The cost of software

Per-seat pricing punishes you for hiring

Charging per user made sense when a seat meant a full-time desk worker. Applied to a salon floor it produces decisions nobody would defend out loud.

By the TotalPro360 team · Published 2026-08-07 · The cost of software

Key points

• The shared-login problem
• Part-time staff break the model entirely
• The incentive runs the wrong way
• What to look at instead
• Worked example: the seat that does not get bought
• What per-seat pricing actually measures
• What to ask a vendor before signing

The shared-login problem

Ask around any industry priced per seat and you will find businesses sharing one login across a team. It is against the terms, everybody knows it, and it happens anyway because the alternative is paying four times over for people who each use the system for ten minutes a day.

The cost of that workaround is not the license fee. It is that every action in the system is attributed to the same person, so there is no audit trail, no per-staff reporting, and no way to know who changed a booking.

Part-time staff break the model entirely

A Saturday-only stylist, a seasonal detailer, a trainee two afternoons a week — each needs access and each generates a fraction of a full-time person's revenue. Charged a full seat, they can easily cost more in licensing than they contribute in their first months.

So they do not get an account. They work through somebody else's, or on paper, and the business loses visibility over exactly the staff whose work it most needs to supervise.

The incentive runs the wrong way

Good software should make it easier to grow. Per-seat pricing makes every addition to the team a small negotiation with your software vendor, which is a strange party to have a say in your hiring.

It also means the vendor's revenue grows when your headcount does, regardless of whether your revenue did. In a year where you hired and margins tightened, your software bill goes up.

What to look at instead

When comparing options, price the business you expect to be running in two years, not the one you are running today. Include the seasonal staff. Include the second location if you are thinking about one.

If that number changes the decision, the seat model is doing something to your plans that is worth being deliberate about.

Worked example: the seat that does not get bought

A salon with six stylists is on a plan at $49 per user. Adding a seventh stylist adds $588 a year to the software bill before she has done anything.

That is not enough to stop the hire. What it is enough to do is stop the seat: the new stylist shares a login, or works off the front desk's screen, or keeps her own clients in her phone. Every one of those is a rational response to the price, and every one of them destroys the thing the software was bought for.

Now add the part-timer who works Saturdays, the apprentice, and the receptionist who covers two days a week. At $49 each that is another $1,764 a year for people who between them use the system a few hours a week — so they do not get accounts either.

The salon is now running a system that half its floor cannot log into, and the reports it produces describe a smaller business than the one that exists.

What per-seat pricing actually measures

Per-user pricing came from software sold to office workers, where a seat meant a full-time desk and a full day of use. Applied to a shop floor it measures the wrong thing entirely: a Saturday-only stylist is not a third of a user, she is a person who needs to see her own column.

The result is a pricing model that charges most for exactly the businesses that are growing, and that makes its worst offer at the moment a business hires. Nobody would defend that out loud, and every vendor that uses it knows it, which is why the price per seat usually drops the moment you threaten to leave.

The alternative is not complicated. Charge for the transactions the business runs, which scales with revenue rather than with headcount, or charge a flat price regardless of team size. Either way, the answer to "should this person have a login?" stops being a budget decision and goes back to being an obvious yes.

What to ask a vendor before signing

Ask three questions: what happens to the price when I add a seasonal member of staff, which tier contains online booking and payments, and can I export my clients and appointments if I leave. The answers are more revealing than the pricing page.

A vendor comfortable with all three is one whose incentives are roughly aligned with yours. Hesitation on the third is the one worth paying attention to.