Scene
The owner knows the shop needs another dispatcher. Calls are backing up, invoices are waiting for review, and techs keep texting the same office person for answers. Then the software bill gets involved: another login means another monthly charge.
That is a software pricing problem pretending to be a hiring problem.
On every TuffOps plan, your field tech seats are the only ones you pay for. Office and dispatch seats are free, up to a generous cap on every tier. This post is a quick tour of why we did it, what it actually saves, and what we think it says about how field service software should be priced.
The office should not be punished for helping the field
| Question | Short answer for HVAC contractors |
|---|---|
| What is different? | TuffOps bills by field tech seat and includes office / dispatch seats up to the plan cap. |
| Why does it matter? | Per-user pricing can discourage hiring office help, encourage shared logins, and make dispatch or billing capacity feel like a penalty. |
| What should the shop compare? | Separate revenue-producing field seats from admin seats, then compare the total monthly cost and operational tradeoffs. |
| What is the sample impact? | An 8-person shop with 6 techs and 2 office users saves $158/month in the example below versus a flat $79/user competitor. |
What dispatch gets
A named login without sharing the owner's password or routing every schedule change through one person.
What billing gets
Invoice review, payment follow-up, and customer history access without adding a field-tech seat.
What the owner stops weighing
Whether a needed office hire is worth another software line item.
What stays accountable
Each office user still has their own access, so schedule, invoice, and customer changes do not hide behind shared logins.
The hidden tax of "per user" pricing
Most modern SaaS — including most field service software — charges per seat, period. Whether the seat belongs to a $40/hr field tech generating revenue with every job or a $20/hr part-time office assistant entering invoices, the rate is the same.
The spreadsheet logic is simple: every login has access, so every login gets the same price. But that logic bleeds straight into the shop's hiring decisions:
- Owners delay hiring office help because the software cost feels like a tax on overhead.
- Owners give multiple employees one shared login (a security disaster) to dodge per-seat fees.
- Owners route everything through one bottleneck person — the one who has the login — and operations get fragile.
- Owners shop the cheapest flat-rate tool and lose access to the features they actually need.
None of those are good outcomes. All of them happen because the pricing model was designed around login count, not around how a service business actually grows.
Named office seats and role permissions are healthier than shared logins created to avoid per-seat fees. When each dispatcher, bookkeeper, and manager has their own access, the shop can see who changed a schedule, sent an invoice, or updated a customer record.
Our pricing, plainly
TuffOps charges per field tech. Office and dispatch seats are free up to a cap that scales with your plan:
| User Type | Starter | Pro | Enterprise |
|---|---|---|---|
| Field Tech | $59/mo | $79/mo | $99/mo |
| Office / Dispatch | Free (up to 2) | Free (up to 3) | Free (up to 5) |
| Comply add-on (refrigerant compliance) | +$15/tech/mo | Included | Included + Owner Portal |
That structure isn't a clever discount — it reflects how we think about who creates value in a field service shop and where the software is doing the heavy lifting.
What this actually saves
Let's run the numbers for the same 8-person shop we use elsewhere on this site: 6 field techs, 2 office staff (a dispatcher and a bookkeeper).
On a typical per-user competitor at $79/seat
| Line | Cost |
|---|---|
| 6 field techs × $79 | $474 |
| 2 office staff × $79 | $158 |
| Total | $632/mo |
On TuffOps Pro
| Line | Cost |
|---|---|
| 6 field techs × $79 | $474 |
| 2 office staff (free, up to 3 included) | $0 |
| Total | $474/mo |
Difference: $158/mo, or $1,896/year. For an 8-person shop. The gap widens fast as you grow:
- 12-person shop (8 techs + 4 office on Enterprise): saves $396/mo, or $4,752/year
- 20-person shop (15 techs + 5 office on Enterprise): saves $495/mo, or $5,940/year
That's enough money to fund another part-time office hire, which is sort of the point — we'd rather you hire the dispatcher than pay us for the seat.
Curious what your shop would actually pay? Book a 30-minute pricing walkthrough and we'll model your team size against TuffOps and whatever you're using or evaluating.
The principle behind it
We think pricing should be aligned with where the value of the software actually shows up. In a field service business, that's the field. The software earns its keep by:
- Helping techs run more jobs per day with less friction
- Capturing the data that lets you invoice faster and win disputes
- Protecting you on compliance and warranty work
- Closing the loop between dispatch and the truck
Office staff use the software to coordinate that work — but charging them the same rate as a tech rewards the wrong behavior. It punishes you for adding the office capacity that makes your field operation run smoothly. It encourages shared logins. It drags your hiring decisions sideways.
So we picked a different model. Pay for the seats that touch revenue directly. Get the office seats included.
The honest small print
A few things worth being upfront about:
- "Free" has a cap. 2 free office seats on Starter, 3 on Pro, 5 on Enterprise. If you have 8 office staff, you'll need to talk to us — but at that point you're a big enough operation that custom terms make sense for both sides.
- "Office / dispatch" is a real role distinction. Office seats are people who work primarily from a desk: dispatchers, schedulers, bookkeepers, customer service. If you've got someone who's half in the office and half on a truck, they're a tech seat.
- This isn't a discount we'll yank later. It's a structural part of how we price TuffOps. Every customer gets it.
If you're already on a competitor
The honest move is to do the math on your actual team. Add up everyone with a login, separate techs from office, and apply your current per-seat rate to the office side. That's the number you're paying that you don't have to.
If it's $50/mo, ignore it — the switching cost isn't worth it. If it's $200+/mo, that's $2,400/year you could redirect into another hire, into Comply for Part 84 compliance, or just back into your margin.
How to compare pricing without getting fooled
- Separate roles first. Count field techs, dispatchers, office administrators, managers, and owners separately before comparing plans.
- Price the whole workflow. Include scheduling, mobile work orders, photos, signatures, payments, reporting, compliance, and customer history instead of comparing login cost alone.
- Watch for shared-login pressure. If the pricing model makes shared logins tempting, the software is creating avoidable accountability and security risk.
- Check growth scenarios. Model what happens when you add one dispatcher, one bookkeeper, or a second branch office.
- Ask what "free" means. Confirm the cap, role definition, permissions, and what happens if someone works half in the office and half in the field.
- Compare annual cost. Monthly differences look small until they are multiplied across users and a full contract year.
The examples in this post use sample pricing and sample team sizes, not a guarantee of savings for every contractor. Compare against your actual users, plan requirements, billing terms, and add-ons.
Frequently asked questions
Are TuffOps office seats really free?
Yes, office and dispatch seats are included up to the cap on each plan. TuffOps charges for field tech seats because those seats represent the billable field capacity the software is built to support.
Who counts as an office or dispatch user?
Office users are people who primarily schedule, dispatch, bill, manage customer communication, review work, or handle administration from the office. A user who regularly performs field work should be treated as a field tech seat.
Why not charge every login the same price?
Flat per-login pricing is simple, but it can discourage contractors from adding dispatch and admin help. TuffOps pricing is designed around field capacity while still giving the office named access to coordinate the work.
Get a real number for your shop
Tell us your team makeup and we'll show you the exact monthly cost on TuffOps — including which tier fits your operation and what comes included.
Book a pricing walkthrough