Per Seat Pricing for a Team That Grows in Bursts

Per seat pricing charges you for people, not for work finished. That is fine when your headcount barely moves. It gets expensive when your team doubles for a three month build and then shrinks back again.

Here is the short answer. Per seat pricing is fair when most of your people open the tool most days and your headcount is steady. It works against a team that grows in bursts, because you pay the same monthly price for a contractor who logs in twice a week as you do for an engineer who lives in the workspace. The fix is almost always contractual: monthly billing, a clear way to remove seats, and modules you can switch off for people who do not need them.

Work the maths before you argue about it

Write down two numbers. The first is your baseline: the team size in a quiet month. The second is your peak: the headcount during your busiest project of the year.

The gap between those numbers is the part of the bill worth arguing over. Now ask three things about the people in that gap.

• How many days a month will each of them open the tool?
• How many weeks does the burst last?
• Does the seat get released when they leave, or only when your term ends?

A contractor who is with you for ten weeks and opens the workspace once a week is the most expensive seat you will ever buy. A permanent engineer who works in it daily is the cheapest. Same price, very different value.

When per seat is fair

Per seat is honest pricing when usage tracks headcount closely. If every new person means one more set of tasks, one more calendar, one more leave record and one more approval queue, then the vendor's cost really does rise with your team and the price follows something real. For a small team the prior question is whether a dedicated HR tool earns its place at all.

It is also predictable, which matters more than people admit. A finance lead can forecast a per seat bill from a hiring plan. Usage based pricing needs a guess about behaviour, and guesses about behaviour tend to be wrong in the expensive direction.

Where it punishes seasonal hiring

Three clauses do most of the damage, and they vary by vendor, so read your own agreement rather than assuming.

• Annual commitment with no true down. You add ten seats in March for a summer project and pay for them until the following March.
• Seat floors. The contract sets a minimum count. Your baseline can shrink, the bill cannot.
• All or nothing modules. A warehouse supervisor who only needs a shift roster is charged as though they use everything.

None of these are unreasonable on their own. Together they turn a burst into a year long cost.

What to ask for

Bring specifics to the conversation. Vague requests for a discount get vague answers.

• Monthly billing with the ability to reduce seat count at the next cycle.
• A stated release window, so a seat removed on the 3rd is not billed for the rest of the quarter.
• Modules priced separately, so a short term hire is charged for what they touch.
• A written answer on what happens to a person's records when their seat goes. Removing a seat should not remove the history of the work.
• If the vendor offers a lighter tier for occasional users, ask what it includes. Do not assume one exists.

Ask the last question in writing. It is the one people skip and then regret at renewal.

How this looks in SicherOne

SicherOne is sold per seat, and the modules are separable. That matters for burst hiring in a plain way: someone brought in for a single project can be given the project side without being paid for on the HR side. Project management, HR and AI agents sit on one set of records, so a board still knows who is on leave without every contractor being handed a full HR seat.

That does not make per seat the right shape for every team. It just means the question becomes narrower and easier to answer: which of these people need which parts, and for how many weeks. That is the same question behind adding a module rather than another tool.

The decision, in one line

If your headcount is steady, per seat pricing is fine and you should spend your energy elsewhere. If you hire in bursts, the price per seat matters less than the terms around adding and removing them. Negotiate the terms, and if you are running a project tool and an HR tool side by side, count both bills before you start.