Rent, Buy, or Have It Built? What Software Models Cost in the Long Run
A small subscription looks harmless, a purchase price looks big — calculated over five years, the picture often flips. A sober comparison of the three paths to software of your own.
A practice's appointment management, a cultural centre's membership administration, a law firm's client portal — before anything else comes the same decision: rent, buy, or have it custom-built? All three are legitimate; they just distribute costs and risks differently.
Renting (subscription/SaaS): start small, pay forever
The subscription scores at the start: low upfront costs, operation and updates included, ready immediately. The price is permanence — you pay as long as you use it, and the provider can change the terms. An example: €89 a month adds up to €5,340 over five years. Add lock-in: switching later means negotiating data exports and starting over elsewhere. A note on my own products: your user data can be exported at any time – as JSON, including all uploaded files.
Buying (one-off licence): pay once — with an honest footnote
The one-off licence reverses the logic: a larger amount up front, after which the installation belongs to the organisation and runs with no mandatory costs. Over years this is often the cheapest path — if you read the footnote: purchased software also needs care. Security updates, new browser and PHP versions, changed legal requirements — skipping these becomes a risk within a few years. Honest buying maths: purchase price plus modest annual maintenance, via contract or a provider of your choice. A note on my own products: maintenance is optional and cancellable yearly – the software keeps running unchanged without it. Why that is not fine print: Why Software Needs Care.
Having it built (custom development): maximum fit, maximum project
Custom development delivers exactly the workflows you want — at quickly five-figure project costs plus ongoing support. Sensible when workflows are so specific that nothing ready-made fits. For standard tasks such as appointment booking or membership management, you mostly pay for something that already exists.
What to base the decision on
- Length of use. The longer the software is meant to run, the more the maths favours buying.
- Independence. Buying plus your own installation gives the most control over data and costs — see Your Server, Your Data.
- Pace of change and budget structure. Constantly changing requirements favour a subscription's flexibility; one-off purchases are often easier to fund than permanent costs — for instance for grant-funded associations.
In short
"Pay once, use forever" works — as a total calculation of purchase price plus well-maintained operation. The subscription buys convenience at a permanent price, custom development buys fit at a project price. Calculate over three to five years, not the first month, and the decision is usually safe.
Frequently asked questions
Is buying always cheaper than renting?
No — for short use or very small subscriptions, renting can come out ahead; after a few years the maths usually tips towards buying.
What happens if I don't book maintenance after buying?
It initially keeps running unchanged. Over the years, security and compatibility risks grow — no care at all is not a long-term option.
Do I really own software I have bought?
Usually a perpetual right of use for your organisation, not ownership of the source code with resale rights. The licence agreement is decisive.
Last updated: August 2026
Ask a question — I always reply personally.
Sounds like your topic?
Let’s find out – with no obligation – where your biggest lever is.






