Per-Seat vs. Flat-Fee Software Pricing, Compared

Most business software is sold one of two ways: per seat (you pay more as you add users) or flat fee (you pay the same regardless of user count). The pricing model matters as much as the sticker price, because the two behave completely differently over time — and mid-market companies, which grow headcount steadily, feel that difference the most.

How per-seat pricing actually behaves

Per-seat pricing looks reasonable at small scale — a handful of users at $X/month is a manageable number. The issue is that the bill scales linearly with headcount forever. As an illustration: 40 users on a mid-market SaaS plan at roughly $70/seat/month runs about $33,600 a year — and that number grows every time you hire, whether or not those new hires use the software heavily. (This is an illustration, not a quote — your actual rate and seat count will differ.)

How flat-fee pricing behaves

A flat monthly fee, by contrast, is set by scope — what the software does and how it’s built — not by how many people log into it. Add 10 users or 400, the fee doesn’t move. That makes the model naturally suited to tools used by a large, often lower-frequency user base: field staff, operations teams, partners, customers.

	Per-seat	Flat fee
Cost driver	Number of users	Scope of the build
Cost as headcount grows	Rises linearly, indefinitely	Flat
Best fit	Small, stable teams of power users	Large or growing user bases, especially light users
Budgeting	Variable — moves with headcount changes	Predictable — fixed monthly number

Why mid-market companies feel this more than small teams

A 15-person startup on per-seat software barely notices the model. A 500-person company adding dozens of new hires a year, plus contractors, plus partner and customer access, watches the same pricing model compound into a genuinely large number — one that has nothing to do with how much value each additional light user is getting from the tool.

When per-seat pricing is still the right call

Per-seat makes sense when the user base is small, stable, and everyone genuinely uses the product’s full depth — a focused team of power users in a specialized tool, for example. The model becomes a problem specifically when it’s applied to large or fast-growing groups of light users who don’t need (or use) most of what they’re being billed for.

When flat-fee wins

Once a workflow needs to reach a large or growing number of people — most of whom touch it for a narrow set of tasks — a custom-built flat-fee tool usually wins on total cost, often within the first year or two, and the gap widens every year after. We break down the full build-vs-buy math, including when SaaS is still the better call, in custom software vs. SaaS.

To see where the crossover point sits for your own team and tool stack, run your numbers through the savings calculator. And if the seat sprawl you’re modeling spans more than one tool, see why mid-market SaaS bills keep climbing for the bigger picture.

Frequently asked questions

Is flat-fee software always custom-built?

Not always, but it usually is in practice — most off-the-shelf SaaS products price per seat because that’s how the vendor monetizes a shared product across many customers. A flat fee is more common with software built specifically for your organization.

Isn’t a flat fee just a bigger upfront cost?

Not necessarily — it depends on the vendor’s model. With ARDN’s approach, for example, new customers pay nothing for the one-time build and only pay the flat monthly fee once it’s live, which avoids the large upfront cost some custom-software vendors charge.

How do we know if we’re a good fit for flat-fee pricing?

If your user count is large, growing, or includes a lot of light/occasional users, flat-fee pricing tends to win on cost. If your user base is small and stable and everyone uses the tool heavily, per-seat pricing may already be efficient for your situation.