Every software proposal looks affordable when the licence is the only number on the page. The cost that decides whether the investment works is the total cost of ownership: everything you spend to choose, implement, integrate, run, change and eventually leave the system.
This comparison sets out a defensible TCO model and applies it to five common ownership models. It avoids fixed prices because licence and implementation costs vary with scope, but the structure lets you plug in the quotes you have received.
The TCO formula
Five-year TCO = acquisition + implementation + integration + data + training + run + change + exit
Acquisition includes licences, subscriptions, hardware and setup. Implementation covers configuration, migration and project management. Integration is the API and file work that connects the system to the rest of the business. Data covers cleaning, deduplication and ownership. Training is staff time, not only course fees. Run is the annual subscription, support, hosting and internal administration. Change is the cost of the customisations and upgrades you will need. Exit is the cost of extracting data and moving to another supplier.
Five ownership models
1. Commercial SaaS subscription
You rent the product per user, per module or per transaction. Upfront cost is low and the vendor manages infrastructure and upgrades. The trade-offs are recurring cost that grows with headcount, limited customisation, add-on pricing and dependence on the vendor's roadmap. Integration and data migration often cost more than the first-year subscription.
2. Perpetual licence with on-premise hosting
You buy a licence and run the software yourself, sometimes with an annual maintenance fee. The upfront cost is higher and you carry infrastructure, patching, backup and database administration. Customisation is usually easier, and data stays under your control. The hidden cost is the specialist who keeps it running, including cover for holidays and resignations.
3. Low-code or workflow platform
A platform provides building blocks for forms, approvals, dashboards and integrations. It can deliver a working process quickly and lets a small team maintain it. The risks are platform lock-in, per-user or per-automation pricing that climbs quietly, and governance gaps when many departments build their own apps. It works best with a centre of excellence and a clear list of approved use cases.
4. Custom-built software
You pay for design and engineering rather than a licence. The fit can be excellent when the process is genuinely different, and you own the code and data. The trade-offs are higher initial cost, the need for a maintenance budget, and dependence on the supplier or an internal team for future changes. A custom build without documentation and tests is a future legacy problem, not an asset.
5. Managed open-source
You use an open-source product and buy hosting, support or implementation from a specialist. Licence cost is avoided, but support, upgrades, security patching and integration are real costs. The model suits businesses that want control and are prepared to pay for operational discipline.
Comparing the models
- Lowest upfront cost: SaaS, followed by low-code. Both shift spend into recurring fees.
- Lowest cost at stable, small scale: often SaaS, because you avoid infrastructure and specialist staff.
- Lowest cost at high, stable scale: sometimes perpetual or custom, but only when the internal team is genuinely capable.
- Best fit for a unique process: custom or low-code, with custom giving more control and low-code giving faster delivery.
- Highest exit cost: deeply customised SaaS and low-code platforms with proprietary data models. Ask for export formats before you sign.
- Highest hidden operational cost: on-premise software maintained by one person who is never replaced.
Cost lines most business cases miss
- Data cleaning. Importing a decade of inconsistent customer records is a project of its own.
- Integration. Each connection needs an owner, error handling and monitoring, not just an initial build.
- Training and change management. A system that staff do not use has a negative return, whatever the licence cost.
- Reporting. Operational reports, statutory reports and ad hoc analysis often need work outside the core licence.
- Security and access reviews. User provisioning, role design, audit logs and periodic reviews take time.
- Renewal uplift. Model a renewal increase rather than assuming today's price lasts five years.
- Exit and decommissioning. Data extraction, contract notice and parallel running are costs, not footnotes.
Build a five-year model you can defend
Create one row per cost line and one column per year. Put the quote in the year it is incurred, not spread evenly. Add low, expected and high scenarios for implementation and change. Then calculate cost per user, cost per transaction and cost per process supported. A system that costs more per transaction than the margin it protects is a candidate for replacement, however modern it looks.
For a Bangladesh business, add currency risk on USD licences and the cost of international card payments or bank transfers. A licence that looks stable in dollars can rise sharply in taka terms, and the renewal budget should reflect that.
Include the cost of the internal owner. Someone must manage the vendor, approve changes, review access and own the data. If that person does not exist, the TCO is understated.
Decision guidance
- Choose SaaS when the process is standard, the team is small and speed matters more than customisation.
- Choose perpetual or managed open-source when data control and deep customisation matter, and you can fund operations.
- Choose low-code for well-bounded internal workflows with a named platform owner and a governance model.
- Choose custom when the process is a source of competitive advantage, no product fits, and you can commit to maintenance.
Questions for the supplier
- Which costs are included in the quote, and which are billed later?
- How does pricing change at 10, 50 or 200 users?
- What is the renewal uplift clause, and how much notice is required?
- Who owns the data, and in what format can we export it?
- Which integrations are native, and which need paid add-ons or custom work?
- What happens to our configuration and history if we leave?
Metrics
- Five-year TCO per user and per transaction.
- Percentage of the quoted scope delivered without change requests.
- Adoption rate among the intended users.
- Integration incidents per month and time to resolve.
- Annual run cost as a share of the original acquisition cost.
If you need help comparing a product against a custom build, start with Custom Software & Integrations; the pricing page explains how we scope discovery, build and handover. For the budgeting side, read how SME IT budgeting changes year by year.
Sources
- FinOps Foundation, FinOps Framework, accessed 17 November 2026.
- Flexera, State of the Cloud report, accessed 17 November 2026.
- AWS Well-Architected Framework, Cost Optimization Pillar, accessed 17 November 2026.
- UK Government, Technology Code of Practice, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.