Skip to content
ResourcesOwnership

Rented vs owned: what per-seat practice software really costs a growing firm

25 May 20267 min read
RENTED£/mo£/mo£/moPer seat. Every year. Their roadmap.OWNEDBuilt once. You hold the keys.

Every practice management tool on the market, Karbon, Senta, BrightManager, Xero Practice Manager, is rented. You pay per seat, every year, the price rises as you grow, and the roadmap belongs to the vendor. A platform you own costs more on day one and less over time. Here is the honest comparison, including when renting is the smarter call.

What renting actually means

The subscription model is built around one number: seats. Every person you add raises the bill, even if they use a fraction of the product. The headline price is an anchor, not a ceiling: annual rises, tier changes and add-on modules are the vendor’s lever, not yours. And the roadmap is set by what suits the average customer, so the feature your firm actually needs sits behind the features that sell to everyone else.

The cost curve nobody shows you

Per-seat pricing looks cheap because the first year is cheap. The honest picture is cumulative. A subscription compounds with headcount and annual increases. An owned build is front-loaded, a real number on day one, then mostly maintenance. Plot both and they cross.

Yr 1Yr 2Yr 3Yr 4Yr 5CUMULATIVE COSTBreak-evenOwned (build once)Rented (per seat)
Illustrative. Per-seat cost compounds with growth; an owned build is front-loaded, then flat.

Where the lines cross depends on your seat count and time horizon, not on a sales deck. The more people you put on the tool, and the longer you keep it, the worse renting looks. For a tool you expect to use for years across a growing team, owning is usually the cheaper option, not the expensive one.

The four things you give up when you rent

Rented
Owned
The roadmap
The vendor's priorities
Yours, in your order
Your data
Exported on their terms
In your own database
Cost as you grow
Rises with every seat
Flat after the build
Leaving
Migration and lock-in
Nothing to leave

Price is only half of it. The other half is control. When the tool is rented, the vendor decides what gets built, what it costs next year, and how hard it is to leave. Your data lives in their system on their terms. None of that shows up in the monthly invoice, but all of it shows up the first time you want something they do not want to build.

When renting is the right call

Owning is not a moral position, it is a maths and control decision, and it does not always win. If the tool is peripheral, if your process is genuinely standard, if seat counts are low, or if you are early and still changing how you work, a subscription is the sensible choice. Rent the commodity. Own the thing that is core to how your firm runs.

What “you own the code” actually means

It is a specific promise, not a slogan. You receive the full source code and documentation. It runs on your own infrastructure. There is no per-seat licence, so adding staff costs nothing extra. You can hire anyone to change it, because it is yours, and there is no vendor to leave because there is no lock-in. The cost moves from a forever subscription to an asset on your side of the table.

That is the model we build on, and it is the same reason our practice platform is a custom build a firm owns, not another seat to rent. If you are weighing the decision itself, read build vs buy, or the cost crunch behind all of it in the MTD workload piece.

FAQ

Quick answers

Is custom software cheaper than per-seat SaaS?
Over a short horizon with few users, no, per-seat SaaS is cheaper to start. A custom build overtakes it once you have enough seats or enough years, because your cost stops rising with headcount while the subscription keeps climbing.
What does 'you own the code' mean?
You receive the full source code and documentation, it runs on your own infrastructure, and there is no per-seat licence. You can hire anyone to change it and you are not locked to one vendor.
Is owning custom software risky to maintain?
It needs a maintenance budget, but you control the timing and scope. With rented software you are exposed to a different risk: forced price rises, removed features, and migrations you did not choose.
When should a firm not build custom software?
When the tool is peripheral, your process is genuinely standard, seat counts are low, or you are early and still changing how you work. In those cases a subscription is the sensible call.

Who checks what your developers ship?

An independent security and build review of what your agency delivered. £2,500, about two weeks, with a re-test of their fixes included.