SaaS, Custom Build or Self-Hosted Licence? A Five-Year Decision Framework for Business Software

Every growing business eventually faces the same decision about its core software: rent it, build it, or own it. Rent a SaaS subscription and be live this week. Commission a custom build that fits every process exactly. Or license self-hosted software that runs on your own servers, with your own data.

Each option is right for some businesses and expensive for others. The mistake is choosing by habit — "everyone uses SaaS now" or "we're special, we need custom" — instead of by the numbers and risks that matter for your next five years.

This article gives you a framework to decide: what each model really costs over time, a scoring matrix across six factors owners actually feel, the questions to ask any vendor, and a short decision path. I am the architect behind a self-hosted product, so I will be explicit about where SaaS or custom is the better choice.

The three models in plain words

	SaaS subscription	Custom build	Self-hosted licence
What you get	Access to software the vendor runs	Software written for you	A licensed product you install and run
Where data lives	Vendor's cloud	Wherever you host it	Your servers
How you pay	Per user or per tier, monthly	Project fee, then maintenance	Licence per site or module, plus hosting
Who runs it	The vendor	You or your agency	You or a partner, with vendor updates
Speed to start	Days	Months	Days to weeks

The cost that matters: five-year total cost of ownership

Comparing the first invoice of each option is misleading. SaaS looks cheapest in month one; custom looks most expensive. What matters is the total cost of ownership (TCO) over the period you will actually use the system — usually five years or more for core operations.

The assumptions behind the chart

The model above is for a business with 25 people using the system. Every number is an assumption you should replace with your own quotes:

• SaaS: an integrated suite at $45 per user per month, plus $3,000 a year for add-ons and integrations, with an 8% price increase each year.
• Custom build: $60,000 to build the first version, then $12,000 a year in maintenance and changes plus $2,400 a year for hosting.
• Self-hosted licence: $6,000 one-time for setup, data migration and training, then $5,100 a year for the licence, a capable server with backups, and a few hours of administration each month.

Cumulative cost (USD)	Year 1	Year 3	Year 5
SaaS subscription	16,500	53,600	96,800
Custom build	62,400	91,200	120,000
Self-hosted licence	11,100	21,300	31,500

Two patterns hold in almost every version of this model I have built with clients:

• SaaS cost grows with headcount. Per-seat pricing is excellent at 5 users and painful at 50. Every new cashier, picker or accountant is a new line on the invoice.
• Custom cost never stops. The build is only the beginning. Every regulation change, new payment method and browser update is paid for by you.

Self-hosted software sits between them: you pay for a product that is already built and maintained by a vendor, but you do not pay per seat and you control where it runs. The trade-off is operations, which we will come back to.

Six factors that matter more than the price

1. Time to go live

SaaS wins. If you need to start selling next week and your processes are standard, a subscription is hard to beat. Self-hosted products come close when they ship as ready-made containers. Custom builds take months, and the first version is rarely the one you keep.

2. Cost at scale

The more people use the system, the more per-seat pricing hurts. Flat licensing per site or per module scales better. Custom software has no seat fee, but you pay in development time instead.

3. Data ownership and residency

Customer records, salaries, supplier prices and sales history are among your most valuable assets. With SaaS, they live in the vendor's cloud under the vendor's terms. Some industries and regions require data to stay in a specific country or on infrastructure you control. Self-hosted and custom software give you that control by default.

4. Fit to unique processes

Custom software fits perfectly — at a price. SaaS offers configuration but rarely real change. A good self-hosted product covers the generic 80% (orders, stock, ledger, payroll) with proven modules and lets you extend the remaining 20% that makes your business different.

5. Operations burden

This is where SaaS genuinely shines: no servers, no updates, no backups to test. Self-hosting means someone must run servers, apply updates and check backups. Modern tooling — containers, one-click updates with rollback, scheduled snapshots — makes this far lighter than it used to be, but it is never zero. Be honest about whether you have the people or a partner for it.

6. Exit cost and lock-in

Ask how you would leave before you sign. SaaS exports are often limited to CSV files that lose relationships and history. Custom software can trap you with one developer who understands it. Self-hosted software on an open database lets you query, export and migrate your own data whenever you choose.

When each model is the right answer

Choose SaaS when…

• You have fewer than about 10 users and standard processes.
• You need to be live within days and have no technical staff or partner.
• Data residency is not a legal or contractual requirement.

Choose a custom build when…

• The software is your competitive advantage — a unique pricing engine, a novel marketplace, a regulated workflow nobody else supports.
• You can fund a team (in-house or a long-term agency) for as long as the software lives.

Choose a self-hosted licence when…

• You have 15 or more users, or plan to, and per-seat pricing would dominate your costs.
• You need control over data location, backups and security policies.
• Your core processes are mostly standard — commerce, inventory, accounting, HR, payroll — with some extensions.
• You have a technical person or a partner who can run a server, or you are willing to learn.

A hybrid is often best. Many businesses self-host their core ERP and commerce platform, use managed services for email delivery, payments and backups storage, and build custom code only for the one or two processes that truly set them apart.

Twelve questions to ask any vendor

1. What will this cost at our current headcount, and at three times that headcount?
2. Which features are in the base price, and which are paid add-ons?
3. How much can prices rise at renewal, and is that written in the contract?
4. Where exactly is our data stored, and who can access it?
5. How do we export all our data, including history and relationships, and in what format?
6. What happens to our data if we stop paying, or if you go out of business?
7. How are updates delivered, and can we roll back a bad one?
8. What is your backup policy, and when did you last test a restore?
9. How do you handle security: two-factor sign-in, roles, audit logs, encryption?
10. Can we extend the system without breaking future updates?
11. Is there a free trial on our own data, and a money-back period?
12. Can we speak to the people who will support us after the sale?

A five-minute decision path

1. Is the software itself your competitive advantage? If yes, plan a custom build for that part — and only that part.
2. Will more than 15 people use it within two years? If yes, model per-seat costs carefully; self-hosted usually wins on cost.
3. Must data stay on infrastructure you control? If yes, choose self-hosted or custom.
4. Do you have a technical person or partner? If not, and the answers above were "no", start with SaaS and revisit in a year.

How StoreConsole is priced and delivered

StoreConsole is a self-hosted licence: you choose the modules you need, pay per site rather than per user, and run it on your own server or any host you trust. Every plan starts with a 14-day free trial and a 30-day money-back guarantee, updates arrive from inside the admin panel with rollback, and your data sits in your own database. The 95-second video below shows how building a plan, checking out and receiving a licence works. Current prices are always on the pricing page.

Key takeaways

• Compare five-year total cost of ownership, not the first invoice.
• SaaS wins on speed and zero operations; its cost grows with every new user.
• Custom wins on fit; its cost never stops.
• Self-hosted licences win on cost at scale, data ownership and exit freedom, in exchange for running a server.
• Ask how you would leave before you sign, whichever model you choose.

Anichur Rahaman is a software architect and the creator of StoreConsole. He designs commerce and ERP systems for growing businesses, with a focus on event-driven architecture, data integrity and self-hosted operations.