Per-client vs. per-seat pricing for professional services software: what the difference costs you

Most professional services software is sold per seat. You pay for every person on your team who logs into the platform — each admin, each associate, each junior analyst added to a client file. The logic sounds reasonable until you map it against how professional services firms actually operate, at which point it starts to look like a pricing model designed for someone else's business.

Per-client pricing — where you pay based on the number of client relationships you manage, not the number of people on your team — aligns with the economics of the firm rather than working against them. The difference isn't academic. Over three years of typical firm growth, it's often the difference between software costs that are manageable and software costs that become a budget line item people start questioning.

How per-seat pricing works

Per-seat pricing charges you for each user account. £40 per user per month is a common figure in this tier. A firm with one partner, two associates, a paralegal, and an admin has five users: £200/month. When the practice grows and you hire two more associates, you're at seven users: £280/month. The software bill goes up every time you make a hire, independent of whether that hire increased your revenue.

This creates an incentive that cuts against firm growth. Adding junior staff — the people who do the delivery work that earns the firm's revenue — becomes a line item that needs to be justified not just in terms of capacity but in terms of software cost. It's a small friction, but it's a real one, and it compounds over time.

For firms with significant support staff — admin assistants, practice managers, billing coordinators — the cost of including them in the platform becomes a decision. Do you give them access, pay for their seats, and have clean workflows? Or do you exclude them to save on licence fees and accept the workaround costs? Neither answer is good.

How per-client pricing works

Per-client pricing charges you based on the number of client organisations you manage on the platform. The firm pays more as it takes on more clients, which is when it's also generating more revenue. Adding staff to handle existing client work doesn't move the needle on the software bill.

A firm with 12 active clients pays for 12 active clients. Whether it has two partners and a paralegal delivering that work, or five associates and two admins, the software cost is the same. The pricing model is indifferent to how many people you employ.

This also means the software vendor's interests are aligned with the firm's. They want you to take on more clients because that's how they grow their revenue. You want to take on more clients because that's how you grow yours. Per-seat pricing creates a softer tension: the vendor benefits from you hiring, and you are not sure whether that benefit is passed back to you in product investment or just extracted as margin.

A concrete cost comparison

Consider a professional services firm that grows from 10 clients with 5 staff to 40 clients with 15 staff over three years.

Per-seat software at £40/user/month:

• Year 1: 5 users × £40 = £200/month, £2,400/year
• Year 3: 15 users × £40 = £600/month, £7,200/year
• Three-year total: approximately £14,400

Per-client software at £129/month for up to 30 clients (Growth tier example):

• Year 1: £129/month, £1,548/year (10 clients, well within the tier)
• Year 3: £129/month, £1,548/year (40 clients on Scale tier, £299/month — £3,588/year)
• Three-year total: approximately £7,200

The per-seat firm spends roughly twice as much by year three, and the cost gap widens as hiring accelerates. The inflection point varies by firm, but for any practice that hires meaningfully as it grows, the per-seat model becomes more expensive faster than the per-client model does.

The comparison also understates the per-seat cost because it doesn't account for the periods where the firm is deciding whether to add a user. Junior staff sometimes get shared logins (a security problem), work on spreadsheets outside the system (a data quality problem), or have their access deprovisioned and reprovisioned seasonally (an admin overhead problem). Each of these workarounds has a cost that doesn't show up on the software invoice but is real.

The hidden cost of support staff

The seats that create the most per-seat cost pressure in professional services firms are usually not the fee-earners. Partners and associates are relatively predictable in number. Support staff are not.

An admin assistant who handles billing correspondence needs access to invoice records. A practice manager who monitors capacity needs to see request queues. A business development coordinator who tracks proposal status needs to see client files. Each of these roles benefits from platform access, but in a per-seat model, each access point is another licence fee.

The result is that support staff often end up excluded from the system, which means their workflows live in email and spreadsheets and can't be audited or managed centrally. The cost shows up not on the software invoice but in the time partners spend on operational tasks that should have been delegated.

Per-client pricing is generally indifferent to these users. You can give every member of your team access to the platform, configure their permissions to match their role, and not worry that adding the new office manager is going to increase the monthly bill.

What to look for when evaluating pricing

Three questions to ask any professional services software vendor:

What does it cost when I hire my next three people? If the answer is "your bill goes up by X per person," you've found a seat-based model. If the answer is "nothing, unless you take on more clients," you've found a client-based model. The answer to this question tells you more about the long-term cost trajectory than the headline price.

Are client users included? Many PS platforms charge separately for client portal access — each client contact who can log in to view their invoices or submit requests is an additional user. In a per-client model, client-side users should be unlimited and free, because the client portal is a feature of the client relationship, not a separate product.

What's the upgrade trigger? In a per-client model, you upgrade when you take on more clients than your current tier allows. That's a revenue-positive trigger — you're upgrading because you have more business. In a per-seat model, you upgrade when you hire, which may or may not be revenue-positive depending on whether the hire is growth-related or overhead-related.

Software costs compound over time in ways that aren't obvious from the initial price. The pricing model matters as much as the headline number, and for firms whose revenue scales with client relationships rather than team headcount, per-client pricing is the model that stays aligned with the business as it grows.