Why repair shop software charges per seat (and what to do)

If you've been shopping for repair shop software, you've noticed that almost every option charges you per technician. Start with one, pay one price. Hire two, the bill jumps. Add a part-time person to cover Saturdays, the bill jumps again.

It feels like a tax on growing your shop. Because it is.

Here's why it works this way — and what to look for if you'd rather it didn't.

Where per-seat pricing came from

Per-seat pricing wasn't invented to punish repair shop owners. It made sense back when software ran on local servers. Each additional user meant more load on your hardware, more licences, more support calls. Vendors priced accordingly.

Software moved to the cloud. Hosting got cheap. Adding another login for a technician costs a software company fractions of a cent in compute.

But the pricing model didn't move with the technology. "Per seat" stuck around because it's an easy way to grow revenue as your customer's business grows. Every time you hire someone, the vendor gets a raise — without doing anything extra for you.

What it actually costs

We did the maths on per-seat billing years after we'd already committed to it. By then, switching felt like more hassle than the money was worth. That's the trap, and it's a good one — for them.

Let's put some numbers on it. Say a platform charges £30 per technician per month and you have three technicians. That's £90 a month, not the £30 you saw advertised. Add a part-time Saturday person: £120. Bring on an apprentice for the summer: £150. (Made-up figures to show the shape of it — plug in whatever your own platform charges.)

The headline price you saw at sign-up assumed you were running the shop alone. The actual price is whatever your headcount turns out to be, multiplied out, every month, forever.

Some platforms also cap the number of seats at each tier. So you're not just paying more per head — you're locked into predefined jumps. Go from two technicians to three and you might find yourself bumped to a plan that costs twice as much, even though one extra person's login was all you actually needed.

The argument vendors make for it

Vendors defend per-seat pricing with a few different justifications. It's worth knowing them so you can judge whether they hold up.

"You pay as you grow." This sounds fair in theory. In practice, you're not growing your use of the software in any meaningful way when you hire a technician. You're creating one more login. The actual load on the platform is negligible.

"It keeps costs low for small shops." That's true, as far as it goes. A solo shop on a per-seat plan pays less than a five-person shop. But the solo shop is also the one with the least cash to spare, the one most likely to be watching every line item. The model optimises for the vendor's revenue, not for what's fair at different stages of a business.

"Support and onboarding scale with users." There's something to this. A platform with ten thousand users does need more support than one with a hundred. But that cost scales with the total number of customers, not with the number of technicians at your particular shop. You hiring a second person doesn't make you twice as expensive to support.

What to actually look for

When you're comparing repair shop software, the pricing page is just as important as the feature list. A few things to check:

Flat monthly pricing. Some newer platforms have moved away from per-seat billing entirely. You pay a single amount per month regardless of how many technicians you have. That makes your software cost predictable from day one.

What the "starting price" actually includes. Many per-seat plans have a minimum (often one seat). Read the pricing page carefully and work out what you'd actually pay at your current headcount, and at the headcount you're aiming for in a year.

What happens when you grow. If the platform uses tiers, find out exactly where the tier boundaries are and what triggers a jump. "Unlimited technicians" is a meaningful claim. "Up to 3 technicians at this price" is a ceiling, not a floor.

Whether you can actually cancel. Some platforms put a lot of friction around cancellation — support tickets instead of a button, notice periods, "data export on request" that takes weeks. A flat-fee platform that makes it easy to cancel is taking a different bet: they'd rather earn your loyalty than trap you.

Data ownership. If you move away from a per-seat platform, can you take your customers, tickets, and history with you? Or is your data effectively held hostage until you pay a one-off export fee? The answer to that question tells you a lot about how the vendor thinks about the relationship.

What we did at Benchworks

When we built Benchworks, we spent a lot of time on the pricing model before we thought about the feature list. The thing we kept coming back to wasn't features. It was predictability.

So Benchworks is one flat monthly fee — $59 a month, every technician included. The first 100 shops get in at $29 a month and stay there for good. No tiers, no per-seat multipliers, no penalty for hiring.

We also built cancellation in early. One click in your settings, and it's done — no phone call, no retention script. We'd rather earn your business every month than lock you in.

The honest takeaway

Per-seat pricing isn't going away. Most of the established players in repair shop software are built on it, and switching pricing models is hard when you have a big customer base. It benefits them to keep it.

That doesn't mean you have to accept it. When you're choosing software — or reconsidering what you're already on — factor in the full cost at your actual headcount, not the headline price for one user. And ask what the bill looks like when you hire that next person.

If the answer makes you wince, that's information worth having before you sign anything.

If you want to try a flat-fee alternative, sign up for Benchworks — no card, first three months free, and nothing to escape from if it's not for you.