Field Service Software Per-User Pricing: The Math

An HVAC contractor in Denver with six technicians pays a monthly fee times six. Six becomes seven when they hire someone new. Seven stays seven even during the slow season in March when two trucks sit idle and three techs are splitting a single service call between them. That's how per-user pricing works, and it's the standard cost model for nearly every field service platform built in the last fifteen years.

It's also a cost structure that doesn't map to how trades actually work. Hiring is supposed to increase revenue capacity, not software expense. Seasonal layoffs are supposed to lower operating costs, not keep them flat. And overhead shouldn't move independently of the work flowing through the door.

The per-user math

Start with what you're running. A residential plumbing company with three full-time technicians and two seasonal helpers uses per-user pricing. Their software vendor charges a fee per technician per month — let's call it their plan price, whatever you read on the vendor's invoice. For three full-time and two seasonal slots, they're paying about 60 months of fees a year (12 months × 5 seats, minus the seasonal gaps). For comparison: a contractor running three steady employees year-round pays 36 months of fees. The difference compounds if the seasonal crew grows to four people.

The math doesn't reward efficiency. If the same three-person crew works more hours or books more jobs, the software cost doesn't move. If they add a dispatcher who doesn't carry a route, the cost goes up — a dispatcher is still a user, and most platforms charge for every login seat whether they're optimizing work or just scheduling it.

When per-user pricing breaks the budget

A general contracting shop in Montana might have eight project managers, each running multiple jobs across winter and summer. In November, two of them take six-week unpaid leaves for hunting season. The software bill doesn't go down—they stay on the plan. In March, a third takes medical leave, and maybe a fourth goes part-time. The bill stays the same. By April, all eight are back. The per-user model treats every month as full capacity, even though the actual usage pattern varies wildly with season, project stage, and personnel availability.

Scaled up, this becomes significant. A commercial electrical contractor with 12 field techs and 3 admin staff pays the per-seat fee times 15, month after month. If they grow to 15 techs and 4 admin, the fee goes up by 33%. If they drop to 12 techs and 3 admin during a slow winter, they either keep paying for the unused seats or go through a manual audit and repricing—a process no vendor makes painless because they have no incentive to.

The alternative model is what we call a flat retainer — you pay one monthly price regardless of how many people log in. Unlimited users, unlimited technicians, one price. That fundamentally changes the math for headcount volatility and seasonal hiring.

Why per-user pricing won the market

Per-user pricing scales the vendor's revenue with the customer's growth, which is why it's everywhere. A five-person crew pays five seats worth; a thirty-person operation pays thirty. The vendor's margin grows automatically as the customer succeeds. That's attractive to venture-backed SaaS companies because it means predictable, linear growth. It's also attractive to Wall Street because it creates a customer lifetime value calculation.

What's less visible is that it doesn't map to how you actually staff, hire, and lay off. A roofing contractor in Texas might have eight full-time crew leads and twelve seasonal laborers who help during spring and summer peaks. Under per-user pricing, they're paying for twenty seats year-round even though the full crew is together for maybe sixteen weeks. Under a flat retainer, they pay one price and add as many laborers as they need without rethinking the software budget.

What to actually measure

Before comparing field service tools, do this: take your last full year of headcount. Count your full-time and seasonal staff by month. Multiply your seasonal months by the monthly fee per seat you're looking at. Now multiply your full-time headcount by 12. Add those together and divide by 12 — that's your actual annual average cost per month under per-user pricing.

Then look at a flat retainer model. A custom system that runs on our Custom Portal tier ($350/mo) gives you unlimited logins, unlimited technicians, unlimited dispatchers, and one month-to-month bill. For a five-person crew with seasonal help, that's often cheaper than per-user pricing after they hit six or seven active seats. For a twenty-person operation with high seasonal volatility, it's usually cheaper by significant margin.

The catch: flat retainers require integrations that per-user platforms handle through their own app. You need to own the tech stack, which means understanding what it does, what it costs to run, and how it handles uptime during your peak season — the conversation around managed hosting and SLAs matters more when you're not paying a vendor to handle it.

What doesn't change with model

Either way, you still need job dispatch, route optimization, photo capture, signature collection on site, and invoice generation. The software requirements don't change. What changes is the cost structure and your operational flexibility. Per-user pricing locks in a specific headcount model; flat retainers decouple hiring decisions from software spend.

The real decision isn't per-user vs. flat — it's whether you want your software vendor controlling the cost model or whether you want to own a system that grows with your business, not with your payroll. For trades with seasonal hiring or high crew volatility, ownership usually wins.