You hire a fifth technician. Payroll goes up, which you expected and budgeted for. Insurance goes up, which you also expected. And then your software bill goes up, which has nothing to do with the fifth technician doing any more work in the software than the fourth one did.
That last one is worth sitting with, because it is the only line on that list that buys you nothing.
What are you actually paying for when you pay per tech?
Not capacity. The software does not work harder because another name was added to it. The database row costs a fraction of a cent. Whatever it costs to serve a fifth technician is not what you are charged for the fifth technician.
What you are paying for is a pricing model, and the model was chosen because it works well for the people selling it. Per-seat pricing ties the vendor's revenue to your headcount, which means their income grows whenever your business grows, whether or not they built anything new that year. From the vendor's side that is elegant. From your side it is a meter on hiring.
I want to be careful here, because there is a real argument on the other side and you should hear it properly. If every seat is a person generating revenue, then the cost scales with the thing paying for it, and that is a defensible trade. A platform charging you more as you get bigger is not a scam. For plenty of operations it is genuinely fine.
Where it stops being fine is specific, and it is probably why you are reading this.
It stops being fine when your crew size moves. Trades work is seasonal. If you carry nine people in July and four in February, a per-head bill means you are either paying for five people who are not working, or you are doing admin every spring and autumn to add and remove seats. I have watched owners do the second one and describe it as fine. It is not fine. It is unpaid work created entirely by somebody else's pricing page.
It stops being fine when you are small. A four-tech shop and a two-hundred-tech operation are quoted from the same kind of per-head rate card, except the large operation has a procurement person, a competitor quote, and the leverage to use both. You have none of those, so you pay closer to list. The pricing model that is hardest on you is the one you have the least power to argue with.
And it stops being fine the moment it changes a decision. This is the real cost and it does not appear on any invoice. When hiring a technician has a software line attached to it, some owners hesitate. Not many, and not for long, but the hesitation is real, and a tool you pay for should never be an argument against growing.
Why I did not just buy one
I own a handyman company in Haslett, Michigan. I am also the engineer, which is an unusual combination and the only reason this post exists.
When I looked at the field service platforms, the products were good. I want to say that plainly because the rest of this could read as a complaint about the software, and it is not. They are real tools built by people who understand this industry, and for a business shaped the way they expect, one of them is the right answer.
Mine was not shaped that way, and the per-head bill on a crew that changes with the season was the part I could not get past. So I wrote my own. Not as a product — as the thing my company runs on, because I needed it to exist on a Tuesday.
It has been running that company for about a year. Through it: $216K invoiced, 253 jobs carried from enquiry to paid, 3,235 bank transactions categorised without anyone opening them, and 51 scheduled jobs running quietly in the background, 18 of which move real money. It has taken somewhere around ~140 hours of admin off my own plate — and that last figure is my estimate rather than a measurement, which I would rather say than present it as one.
Those numbers are my company's, not a customer's. That distinction matters and I will come back to it.
One honest limitation
Here is what the per-seat subscription buys you that I cannot, and if you skip the rest of this post, read this part.
A support desk. There is one engineer here. No overnight rota, no team, no phone number that reaches somebody who can help at eleven on a Saturday when your crew is standing in a customer's kitchen. A platform charging per seat is using some of that money to staff a queue, and that queue has real value. If having one is what lets you sleep, buy the subscription — that is not a failure of nerve, it is a correct reading of your own risk.
Somebody else's maintenance. Security patching, uptime, upgrades, the unglamorous work that never stops. A vendor absorbs it. Software you own, or rent from one person, means that work has an owner and you should know who.
Working on Monday. A subscription is live this week. Anything I am building is not. If the bleeding is happening right now, stop the bleeding and read this again in a year.
What to check on your own invoice this week
I am deliberately not telling you what any named platform charges. Most of them do not publish pricing at all, so any figure I printed here would be something I made up, and you would be right to distrust the whole post for it. Use your own invoice instead. It is more persuasive than anything I could assert.
One. Find the per-seat line and multiply it out. Take the per-technician monthly figure, multiply by your headcount, multiply by twelve. That annual number is the one that matters and it is almost never the one quoted at you.
Two. Price your next three hires. Same rate, three more people, twelve months. That is what growing the crew costs you in software before anybody swings a hammer. If that number makes you pause, the pricing model is doing something it should not be doing.
Three. Count the seats nobody is using. Technicians who left. The seasonal people who are not working in February. The office seat somebody set up once. Shops routinely pay for several of these and nobody notices, because the bill arrives at the same time every month and looks the way it looked last month.
Four. Ask where the real work happens. If the pricing, the crew planning, the reconciliation, or the owner's weekly report happens in a spreadsheet after the software has been consulted, then the software is not running your business. It is a place you type things before doing the work somewhere else. That gap never closes on its own, because no product can add a feature for the specific thing that makes your shop different.
That fourth one is the tell I would trust above the other three.
What I am building, and where it honestly is
I am turning the software my own company runs on into something other shops can use. It is called Ballast, and the pricing model is the whole point: priced per shop, not per technician. Hire your fifth tech without it being a software decision.
Now the unflattering part, because a post that spent nine paragraphs arguing for honest arithmetic should not end with a sales pitch that skips it.
One shop runs on Ballast today, and it is mine. It has no customers. The work of turning software built for one company into software that safely carries several is underway now, and that is most of the distance between here and a second shop. Founding shops come on in early 2027, and that date moves with the build — I would rather tell you that now than miss it later.
The price is not set. Per shop rather than per technician is decided. The actual number gets worked out with the first few shops rather than announced at them.
If your work does not fit the standard mould, you are exactly who I want to talk to, because those are the shops that make the software worth having. You can read the whole thing, including the parts where I am the wrong answer, at the Ballast page.
And if you would rather not talk to anyone yet, that is fair — two things cost you nothing and need no commitment.
Run the free website check. Give it your URL and it tells you what a customer standing in their driveway on a phone actually runs into on your site. No signup, no call, and the result is yours whether or not you ever reply to me.
Or book the free 30-minute Operations Audit. Half an hour on where your week actually goes — the quote nobody wrote down, the invoice nobody sent, the job that lived in one person's memory. I will tell you which part is worth automating and which part you should leave alone, and if the answer is that you need a cheaper plan on the tool you already have rather than anything from me, I will tell you that too. If you want the bigger version, an Ops-Automation Build starts from $6,000 — but the audit is free and it comes first.
