---
title: "Why per-seat software pricing quietly punishes growth"
url: "https://www.octalhq.com.au/insights/articles/why-per-seat-pricing-punishes-growth"
kind: article
description: "Per-seat software pricing charges you more for growing. Here's how per-user and per-transaction fees quietly tax your success — and the fairer alternative."
published: "2026-05-29T00:00:00.000Z"
updated: "2026-09-26T05:58:59Z"
topics: ["Buying software"]
---

# Why per-seat software pricing quietly punishes growth

Per-seat and per-transaction pricing means your software bill climbs every time you hire or sell more. Here's how the model quietly taxes your success — and what the fairer alternative looks like.

The short answer: most software is priced per user or per transaction, which means the bill goes up every time you hire someone or make a sale. It feels reasonable at first, but it quietly taxes exactly the thing you're working toward — growth. There are fairer ways to price software, and it's worth knowing they exist before you commit.

## The short version

- Per-seat pricing charges you for each user; per-transaction pricing takes a cut of each sale or payment.
- Both mean your costs rise in lock-step with your success, whether or not you're getting more value.
- The fees are easy to miss individually but add up fast as you scale.
- Flat or business-metric pricing (per site, per job, or a fixed fee) doesn't punish you for growing.

## How does the model work?

Per-seat pricing sounds fair: you pay for what you use. But it treats every new hire as a new cost, even when that person is just doing the same work, more of it. The software isn't doing anything extra — you're simply paying more because your team got bigger. Per-transaction pricing does the same on the revenue side: a small percentage of every payment, taken quietly, forever. Stack per-seat plus per-transaction plus the add-ons you need to make the tool usable, and a product that looked cheap on the pricing page becomes a growing line on your P&L that no one quite decided to sign up for.

## Why does it bite hardest as you grow?

When you're small, a few seats and a small transaction fee barely register. That's the point — the low entry price is what gets you in. But the model is designed to scale its take with you. Double your team and your software bill roughly doubles, for software that isn't doing anything new. Triple your sales and the transaction cut triples. You end up paying more precisely because you succeeded, which is the opposite of what good tooling should do. The tools you rely on should get cheaper per unit of work as you grow, not more expensive — because the whole point of a system is to let you do more without more overhead.

## What are the hidden fees you can't turn off?

The sharpest edge is the fees you don't control. A third-party payment or buy-now-pay-later tool baked into your software might skim a markup you can't adjust. A "premium" tier you're pushed onto the moment you add a certain number of users. Processing fees layered on top of the subscription. Individually small; together, a meaningful slice of your margin that leaves the business every month. Because these are automatic and never arrive as a bill, they rarely get scrutinised. There's more on this in [transaction fees and payment markups](/insights/articles/transaction-fees-payment-markups) — the margin quietly leaving your business.

## What does fairer pricing look like?

- **Flat pricing** — one price regardless of how many people use it, so growing your team doesn't grow the bill.
- **Business-metric pricing** — tied to something that reflects real value (sites, jobs processed) rather than headcount, so you only pay more when the operation itself genuinely gets bigger.
- **Owned payments** — processing at cost, with no platform markup on top, so the margin stays with you.

None of these punish you for hiring or selling more. That's the test: does the price go up when you succeed, or only when you genuinely ask the software to do more?

## Why does the three-year view change the decision?

The right way to compare software isn't the sticker price today; it's what it costs to live with as you grow. A tool that's cheap at five users can be expensive at fifty. A tool that's cheap at low volume can bleed real margin once sales climb. Before you commit, model the cost at the size you're aiming for — not the size you are now. This is the heart of comparing [software costs over three years, not three months](/insights/articles/compare-software-costs-three-years): the cheap-today option is often the expensive-tomorrow one, and only the longer horizon reveals it. It also feeds directly into [subscription creep](/insights/articles/subscription-creep-software-bills), where per-seat growth is one of the quiet ways bills balloon without anyone deciding to spend more.

## Is there an alternative to renting per head forever?

There is. A system you own, priced to your operation rather than your headcount, breaks the link between growing and paying more. Instead of a bill that climbs every time you hire, you have a fixed, known cost to run and maintain the system — one that stays flat while your team and revenue grow underneath it. Over a few years, for a growing business, that difference compounds into real money. Whether it's the right call depends on your trajectory and how specific your operation is, which is exactly what a proper look at your numbers reveals.

## Related reading

- [The real cost of business software](/insights/articles/real-cost-of-business-software) — the pillar guide to pricing, TCO and ROI.
- [Transaction fees and payment markups](/insights/articles/transaction-fees-payment-markups) — the fees that scale with your revenue.
- [How to compare software costs over three years, not three months](/insights/articles/compare-software-costs-three-years) — modelling cost at the size you're aiming for.

## The honest first step

If your software costs climb every time you grow, it's worth knowing whether a system you own — priced to your operation, not your headcount — would cost less over a few years. That starts with understanding how your business actually runs and where the money is leaking. Software should fit the business, not the other way round.

*Tell us what you run, and we'll show you what's possible.*
