Per-Seat Pricing for Field Service Software, Explained

You hire a fourth technician, and somewhere in the same week your software bill goes up. Nobody sent a warning. That's just how the plan works: another person on the crew, another line on the invoice. Most owners don't think about it until the third or fourth hire, when the monthly charge has quietly become a real number on the P&L.

Per-seat pricing for field service software is the default across the industry, and for good reason. It's also a structural choice that behaves differently depending on how fast you're growing and how many people actually need to log in.

By the end of this page you'll know how the per-seat model moves with your headcount, how an owned system behaves instead, and which one fits the shop you're running right now.

How per seat pricing for field service software works

A seat is a login. Per-seat pricing means you pay a monthly or yearly fee for each person who has one. Five people with logins, five seats on the bill. Hire a sixth, pay for a sixth.

That's the whole mechanic. Most field service management software is sold this way, usually with a base plan that includes a set number of users and a published rate for every user past that. Some plans bundle a few seats into the entry tier. Some charge for the office staff and the techs at different rates. The shape varies, but the rule underneath doesn't: your software cost is tied to your headcount, not to how much work you're doing or how much money the software saves you.

It's worth separating the seat from the subscription. Even a flat subscription with no per-user charge still ends when you stop paying. Per seat pricing adds a second variable on top of that — the number of people — so the bill moves in two directions. You can pay more because the vendor raised prices, and you can pay more because you hired.

Jobber, Housecall Pro and ServiceTitan all run on some version of this. So do most of the smaller products you'll find in a search.

What field service management software counts as a seat

A seat is whatever the vendor says it is, and that definition is where the real cost hides.

Some products charge for every person who logs in, full stop. Your two office people count. Your part-time dispatcher who works Tuesdays and Thursdays counts. Some charge only for the techs in the field and throw in office logins. Some have a cheaper read-only or "limited" login for someone who needs to look at the schedule but never touches an invoice. Some count seats by who's active that month, so a seasonal helper you turn off in November stops billing. Others bill the seat whether the person logged in or not.

None of this shows up cleanly on a pricing page. You find it in the FAQ, the fine print under the plan grid, or by asking a salesperson a direct question and getting the answer in writing.

Before you compare two products, write down your actual team size the way the vendor would count it. Every tech, every office person, the bookkeeper if she needs access, the owner. Then ask each vendor: which of these people is a paid seat, and what does a seat cost when I add one mid-month?

Two products can look close on the headline number and land far apart once your real crew size is plugged in.

How per user per month billing moves with your headcount

Hire a fifth technician and you've added a truck payment, a phone, insurance, and a line on your software bill. That last one is easy to forget, because it doesn't come with a conversation. The seat gets added, the next invoice is bigger.

That's the whole mechanic. On a per user per month model, your software cost is tied to your crew size. It goes up when you grow and it stays up as long as that person has a login.

The pattern matters more at ten than at five. Going from four techs to five is one more seat. Going from four to ten is six, and by then you've probably also added an office person, maybe a dispatcher, maybe a second person answering phones. Those are seats too. The bill that felt small when you signed up is a different number by the time the crew doubles.

It also works the other direction, which owners forget. Software priced on team size is one of the few business costs that can actually shrink when you let someone go, assuming the vendor lets you remove seats cleanly and prorate.

What it means in practice: every hiring decision has a software cost attached to it. Usually small next to payroll. Not zero. If you're planning to go from a three-person crew to eight in the next two years, pull the seat price and multiply it out before you sign anything. You want to see the number you'll be paying at eight, not the one you're paying today.

An owned build is flat rate pricing for your office software

The other shape is a project. You agree on what the software has to do, you agree on a price for building it, and that price doesn't move because you hired two more technicians in March.

That's how we work at First-Rate Tech Corp. A fixed-price build, a perpetual licence, and the source code handed over with it. No per-user fees, ever. Add a tenth tech, add an office manager, add a seasonal helper in June and take them off in October — the software bill doesn't notice.

Trade owners already understand this. It's the same logic as flat rate pricing on a job: the customer knows the number before the work starts, and it doesn't climb because the job ran long. Same idea, pointed at your office software.

The perpetual licence part matters more than it sounds. It means the thing you paid for stays yours whether or not you keep paying anyone a monthly fee. The source code part matters because it means you're not locked to one vendor to make a change. If we're a bad fit in four years, another developer can pick it up. That's a different relationship than renting.

The trade-off is real and worth saying out loud. A project has a bigger number at the front and a timeline before you're running on it. A subscription has a small number and you're working tomorrow afternoon. One is a purchase, the other is a rental. Neither one is clever, they're just different shapes, and which shape fits depends on what your crew looks like in three years.

Pricing tiers change, so we compare models

You won't find a dollar figure for any subscription in here, and that's on purpose.

Software pricing moves. Jobber, Housecall Pro and ServiceTitan all adjust what they charge, what's bundled, and how their pricing tiers are drawn. A number that's right the week this is published can be wrong by the time you read it. An article that quotes a stale price doesn't just age badly, it sends you into a sales call with the wrong expectation in your head, which is worse than having no expectation at all.

So what we're comparing is shape. One model ties your software bill to how many people use it. The other is a one-time build you own. That structure holds whether the monthly price goes up, goes down, or gets repackaged next spring.

Go get the current numbers yourself. They're on the vendors' own pricing pages, and a sales rep will walk you through them in twenty minutes. Ask what's included at the level you'd actually buy, ask what happens when you add a user mid-month, and ask whether the features you care about sit behind a higher tier or get sold separately as add-on modules.

Then bring those real numbers back to the math in the next few sections and run them against your own crew.

Why a Jobber subscription is an honest way to buy software

A monthly per-user bill is an honest way to sell software. The vendor keeps a support team, ships updates, runs servers, and gets paid in proportion to how much of the product you're using. Nothing shady about that.

And for plenty of shops, per-seat pricing is the right way to buy field service software. If you're two people and a truck, you can sign up for Jobber or Housecall Pro on a Tuesday and be dispatching jobs by Thursday. No build, no scoping call, no waiting. That speed is worth real money when your scheduling currently lives in a notebook and three text threads.

Seasonal crews get the same benefit from the other direction. Landscapers who run twelve people in July and four in January can drop seats in the slow months. A fixed one-time build doesn't shrink with your headcount.

The model does what it says. Where owners get caught out is treating a per-user subscription as a settled cost when it's actually tied to a number that moves.

So if you need to be running this week, go start a trial. Just know what you're signing, and check back on the math when the crew grows.

Annual vs monthly billing and what happens at renewal

Paying up front for a year almost always costs less per month than paying month to month. That's the trade on annual vs monthly billing: you hand over cash now, you lock in a lower rate, and the vendor gets a customer who isn't going anywhere for twelve months.

The part worth reading closely is what happens in month thirteen.

First-year pricing is often promotional. The discount you signed up for was an introductory rate, and the renewal quote comes in at standard pricing. Nothing shady happened. You just agreed to a number that had an expiry date on it, and the renewal lands in your inbox during a busy week when switching software is the last thing you want to do.

Stack that on top of headcount. If you added two technicians during the year, renewal hits you with both changes at once: the discount is gone and you're paying for more seats than you were when you signed.

Two things to do before you renew anything.

• Find the original agreement and check whether the rate you're paying was introductory, and what the standard rate is.
• Ask the vendor, in writing, what your renewal total will be at your current seat count.

Ask early. Ninety days out, not the week it renews. You have more room to negotiate when you still have time to leave.

Modeling three years of growth against your crew size

A monthly price at today's headcount tells you almost nothing. Software is a multi-year decision, so do the arithmetic the way you'd do it for a truck.

Open a spreadsheet. Four columns: year, crew size, seats, annual software cost. Fill in year one with what you're paying right now, at the headcount you have right now, plus any onboarding or setup fees the vendor charges to get you running. Then fill in years two and three with the crew you honestly expect, not the crew you hope for. Add your renewal rate if your introductory period ends inside that window. Total the three years.

Do the same for a fixed-price owned system: the build cost in year one, then whatever hosting and support you've agreed to in years two and three. One number for each path.

Now you have a comparison worth arguing about. The per-seat total moves with your team size. The owned total mostly doesn't.

The ROI question sits underneath both columns, and it's the same question either way: how many hours of office work does the system take off someone's plate, and what is that person doing instead. A cheaper bill that still leaves your office manager chasing invoices by hand hasn't paid for anything.

Two directions change the shape of that spreadsheet, and both are worth running.

If you add technicians

Hire a fifth tech and you're not just adding a truck, a phone and a payroll line. You're adding a seat. Most per-seat plans bill per user per month, so that hire shows up on your software invoice every month he's on the crew, and it stays there until he leaves.

Run it forward. Two more techs next spring, one more the spring after, and your software bill has grown three times without you ever changing what the software does. Same features, same scheduling, same invoices. More seats.

That's the pattern to expect. Ask any vendor what happens the month you add a user, and whether the price per seat changes as the count goes up.

If you lose technicians

The bill stays where it is until you change something. A tech quits in March and that seat keeps billing until somebody in the office logs in and removes the user. On a monthly plan that's a few weeks of waste. On an annual plan you may be paying for that seat until the term ends, because you committed to a user count up front.

Seasonal crews feel this most. You staff up for summer, staff down in fall, and the software bill lags behind both moves.

Ask the vendor what happens when you remove a user mid-term, and get the answer in writing.

The crew size where the math starts to change

There's a point for every shop where the monthly seat bill stops feeling like a rounding error and starts feeling like a line item you'd defend to your accountant. For a two-truck operation it's rarely worth the thought. Somewhere past that, the arithmetic shifts, and it shifts quietly — nobody sends you a letter the month it happens.

Team size is part of the trigger. So is what each seat actually does for you. Ten technicians who all live in the app all day are getting real value per seat. Ten seats where half are subcontractors who log in twice a month, or an office person who only needs to see the schedule, is a different story.

So work it from both ends. Take your current crew size and your honest hiring plan for the next two years, multiply the seat price out, and compare that total against what a fixed-price build would cost once. Then look at how many of those seats are doing light work.

That's a conversation worth having with someone who's seen the numbers for shops your size, not a decision to make from a pricing page.

Automation matters more than which pricing model you pick

Automation for the trades means one thing: stop paying people to do work software should do. That's the point of any of this. A shop that answers every missed call, follows up on every quote, and gets paid without three phone calls is ahead of a shop that doesn't, no matter what the invoice from the software company says.

So judge a system by what it does while nobody's watching. Does a text go out the second a call gets missed? Does a quote that's been sitting four days get a nudge on its own? Do invoice reminders fire without your office manager building a list every Friday? Does a review request go out after the job is marked done? Is there a morning report in your phone before you're in the truck?

Those five should run the same whether you're on a per-seat plan or an owned build. Scheduling and dispatch are the floor. The automations are where the hours come back.

The difference shows up on the bill. Under a per-seat model, every person you add to the system adds cost, including the ones who only need to see today's board. Under an owned system the automations run for whoever you put in them, and hiring a technician in March doesn't change what you pay for software.

Pick the model that fits your cash and your crew. Then make sure the automations actually run, because that's the part that pays for either one.

How to decide which model fits your shop this week

Sit down with three numbers you already know: your crew size today, the number of people you expect to be paying in two years, and how much a surprise line item hurts in February.

If the crew is small and you need to be scheduling jobs by Friday, sign up for field service software with per-seat pricing. Jobber and Housecall Pro will have you running fast, and the monthly cost at a small team size is something most shops can absorb without a meeting. Build the habit first. You can always move later.

If you're hiring, the question changes. Every tech you add comes with a software line attached, so your bill tracks your headcount instead of your revenue. Some owners are fine with that. Others want the software cost to sit still while the crew grows, which is what a fixed-price build with a perpetual licence gives you.

Budget predictability is its own reason. If you quote work months out and want a number you can set and forget, owning the system removes a variable.

Three things to check this week:

• What you're paying per person right now, written down
• How many people you'll put in the system by this time next year
• Which office tasks you're still doing by hand — missed calls, quote follow-up, invoice chasing

That last one decides more than the pricing model does.

Questions owners ask about per-seat pricing

What counts as a seat? Usually any login. That includes the technician in the truck, the office manager answering the phone, and often you. Some vendors separate a full user from a limited or view-only user, and some don't. Read the plan page, then ask the sales rep directly whether your bookkeeper or your part-time dispatcher needs a paid login. The answer changes the monthly number more than most owners expect.

Does the price go up after the first year? It can. Vendors adjust list prices, and the discount that got you in the door may not carry over at renewal. Ask what happens at the end of the term before you sign. That's also where annual vs monthly billing matters: paying annually usually costs less per person, but it locks you in for the year, and monthly keeps you flexible if the crew is about to shrink.

What happens when I hire mid-season? On most plans the new login gets added right away and the charge is prorated, so the bill moves up in the same billing cycle. Losing someone rarely works in reverse that fast. Check whether you can remove a seat mid-term or only at renewal.

If you want to walk through what per seat pricing would cost your shop against an owned build, book a New Project Consultation.