How much does field service software cost?

Every field service owner I talk to asks this early, usually in the first ten minutes: what does this stuff actually cost? The honest answer is that the monthly price on a pricing page is normally the smallest number in the equation.

So here’s the whole equation. Subscription, setup, and the part nobody quotes.

The short answer, in three tiers

Off-the-shelf field service platforms sort themselves into three bands. Entry-level tools built for small crews run roughly $30–$60 per user per month. Mid-market platforms with dispatch, inventory and reporting that goes past the basics run roughly $80–$200 per user per month, usually with a minimum seat count you pay whether you fill it or not. Enterprise platforms don’t publish pricing at all — you get a custom quote, generally with an implementation fee measured in thousands and a per-seat rate that climbs every time you turn on an add-on.

A custom build is a different shape of number entirely. It’s a one-time cost — I start at $25,000, and most V1 builds land between $25,000 and $65,000 — after which you own the software outright and pay for hosting plus whatever changes you decide to make.

The subscription model scales with your headcount. The ownership model scales with your ambition. That one difference is the whole decision.

Per-seat pricing has a built-in problem

Per-seat sounds fair until you notice which direction it runs. Hire five techs and your bill goes up five seats — for software that already existed and already worked yesterday. Growth costs you twice: once in payroll, once in license.

Then there are the tiers. The feature you actually need — two-way texting, a second location, custom reporting, a clean accounting sync — is almost always one plan above the one you’re on. That isn’t an accident. The demo shows you the top tier; the quote lands you where the useful parts cost extra.

And renewals move one direction. You find out about the increase in the same email that thanks you for your loyalty.

The costs nobody puts in the quote

When you’re comparing platforms, add these to whatever the salesperson tells you:

• Onboarding and implementation. Enterprise platforms routinely charge a one-time fee to configure the system and move your data. It can rival a full year of subscription on its own.
• Data migration and integrations. Getting your customer list, job history and accounting data in — and keeping it in sync — is rarely free and rarely quick.
• Training and the productivity dip. Every hour a tech spends learning a tool is an hour off a job. New software always costs you before it pays you.
• The workaround tax.This is the big one. When the platform doesn’t match how you dispatch or quote, your team invents a side process — a spreadsheet, a group text, a manual export every Friday. You pay that every single week, on top of the subscription.

The workaround tax never appears on an invoice, which is precisely why it gets expensive. Nobody counts the hours, so nobody notices them stacking up.

The five-year math

Put rough numbers on it. Say you run ten techs on a mid-market platform at $150 per seat per month. That’s $1,800 a month once you count the office seats, call it $21,600 a year, and about $108,000 over five years before a single price increase. Add an implementation fee, the integration work, and the seats you’ll add as you grow, and the real five-year figure sits comfortably above $130,000.

A custom build at $35,000 up front, plus a managed plan from $375/month for hosting, monitoring and ongoing changes, totals somewhere near $57,500 across the same five years. At the end you own an asset instead of a stack of receipts. Hire ten more techs and that number barely moves, while the subscription roughly doubles.

That’s the same comparison I run in more detail in the ServiceTitan vs. custom software piece, one price tier up.

When a custom build actually pays off

Custom is not automatically the right answer. It wins in four cases:

• You have enough seats that the license is a real line item — usually past eight or ten.
• Your operation has edge cases the platform can’t hold cleanly, so your team is already working around it.
• You’re paying for two or three tools that don’t talk, and re-keying the same job into each one.
• You plan to grow and you’d rather your software bill didn’t grow in lockstep with your headcount.

If none of that is true — small crew, standard jobs, an off-the-shelf tool that fits — keep the subscription. Jobber is genuinely excellent at that size and I’d rather you spent $99 a month than $35,000 with me. I say that on calls regularly, for free, and it costs me work. It’s still the right answer.

For Utah HVAC, plumbing, electrical and similar trades that have outgrown the template, field service software built around your actual workflow is where the math starts to flip.

How to decide without guessing

Don’t start with the software. Start with your operation. Write down four numbers: how many seats you pay for, how fast you’re adding them, how many separate tools are in the stack, and how many hours a week your office spends moving data between them by hand.

Those four tell you more about your real cost than any pricing page will. Then compare the total — subscription plus setup plus drag — against a one-time build you’d own. For a lot of growing field service companies, the number that looks scary up front is the cheaper number over five years. For plenty of others it isn’t, and that’s a perfectly good outcome too.