The arithmetic nobody runs
Take a perfectly ordinary mid-tier practice suite. The math below is illustrative — plug in your own vendor’s price sheet — but the shape holds across the category.
Say the tier your firm actually needs (client portal, documents, billing — never the entry tier, which exists to be outgrown) lands around USD 89 per user per month. A modest firm of three fee-earners plus one admin:
- 4 users × USD 89 × 12 months = USD 4,272 per year
- Over five years: USD 21,360
And that assumes a price that never rises (they rise), a headcount that never grows (you hope it grows), and no paid add-ons (e-signature, extra storage, “premium” support — the quiet second meter). Firms that run this exercise on real invoices routinely find the five-year figure sitting north of the cost of owning purpose-built software outright.
The subscription doesn’t feel like that, of course. That is the design. USD 89 is a lunch decision; USD 21,360 is a partner meeting.
What the rent actually buys — the honest version
This is not an argument that subscriptions are a scam. The rent buys real things:
- Hosting and maintenance you never think about
- Continuous updates, including the security patches you’d otherwise forget
- Someone to call, for whatever a ticket queue is worth
- Low commitment — walking away costs a migration, not a write-off
For a firm with no technical partner, changing needs, or genuine multi-office concurrency, that bundle is worth paying for. Rent honestly if you rent.
What the rent never buys
Four things stay off the invoice no matter how long you pay:
- Equity. Sixty months of payments leave the firm owning exactly nothing. Cancel, and the software — and sometimes practical access to your own data’s structure — is gone.
- Immunity from repricing. Vendors reprice, repackage, and sunset tiers. Your only vote is a migration project.
- Data sovereignty. Privileged files live in the vendor’s infrastructure, on the vendor’s jurisdictional terms — the architectural issue we unpacked in our three-way comparison.
- Fit. The workflow gaps you bridge with spreadsheets in year one are still bridged with spreadsheets in year five.
When owning beats renting
The ownership alternative is not “hire developers and pray”. It is commissioning a purpose-built system once — matters, deadlines, conflicts, billing in your currencies, encrypted on your own hardware — and paying for care only when you actually change something.
The five-year comparison then looks like this: a one-time build at roughly the same order of magnitude as five years of rent, after which years six through twenty cost approximately nothing in licence fees, with every workflow shaped to the practice rather than the reverse. That is the model behind the sovereign legal operations console we engineered for a cross-border firm — no per-user meter exists anywhere in it.
Ownership is the wrong answer when headcount is genuinely unstable, when the firm has no appetite for owning its own backups, or when a template workflow honestly fits. It is the right answer when the practice is stable, the workflow is particular, and the partners can read a five-year column as easily as a monthly one.
Run your own number
Pull the last twelve months of software invoices, multiply by five, add the add-ons you forgot were add-ons. That figure is the honest price of the current path. If it is uncomfortable, the alternative is a conversation about scope, not a leap of faith — start it through our Project Planner or at hello@evaporizestudio.com.