Custom software or SaaS: how to decide
Most businesses should not build custom software for most things. Accounting, payroll, email and helpdesk tools are mature, affordable and maintained by vendors who have solved the same problems for thousands of customers. The real question is narrower: which parts of your operation are standard, and which parts are what make you different?
This guide sets out when software as a service (SaaS) is the better choice, when custom software can justify the investment, and how to compare the two honestly.
Start with the requirement, not the product
Before you look at any product, write down what the process must achieve, who uses it, what information it needs and which other systems it has to work with. Only then compare the options.
Teams that start with a product demonstration often bend the requirement to fit the product. That can be the right decision, but it should be a deliberate one, not something that happens because the demo looked good.
When SaaS is usually the better choice
The process is common across your industry
If thousands of other businesses do the same thing in roughly the same way, a mature product has probably already built it well. Accounting, payroll, email marketing and customer support are good examples.
You can adapt your process to the software
Many products embody sensible ways of working. If changing your process to match the product is acceptable, that is almost always cheaper than building something new.
You need it running quickly
A subscription can be live in days or weeks. Even a well-run custom project needs time for discovery, design, development and testing.
The vendor keeps up with rules on your behalf
Where regulations change often, such as tax and payroll, a specialist vendor that updates the product for every customer can carry that burden better than a one-off system.
You want a predictable monthly cost
A subscription is easy to budget for. A custom project needs an upfront investment, even if it costs less over time.
When custom software can justify the investment
Your process is how you compete
If the way you schedule, price, match or deliver is what sets you apart, forcing it into a generic tool can mean giving up the very thing customers value.
People are holding the business together with spreadsheets
Workarounds are a strong signal. In one of our projects, a counselling service was handling a growing volume of bookings with a lot of manual admin. The CRM we built matches clients to therapists by location, schedules sessions, takes secure payments and sends automated email and WhatsApp messages.
You need several systems to behave as one
When information has to move between sales, operations, finance and customers, a thin custom layer that connects your existing tools can remove a great deal of duplicated entry.
The rules are complex or change often
Some businesses run on rules that do not fit a template: customer-specific pricing, multi-stage approvals or calculations that change by product or region. For one client, we built a SaaS platform that runs assembly, inventory, procurement, quality assurance and sales through configurable workflow phases, so the business can change its process without changing the code.
Licence costs grow faster than the business
Per-user and per-location pricing can become expensive as you grow. Over several years, owning a system that fits can cost less than renting one that does not.
Compare the full cost, not the first invoice
A fair comparison looks at three to five years, not the first year.
For SaaS, include:
- Subscriptions for every user and location you expect to have, not just today’s numbers
- Add-ons, premium tiers and integration tools
- The time people spend on workarounds the product does not cover
- Data export limits and the cost of leaving later
- Likely price rises at renewal
For custom software, include:
- Discovery and design
- Development and testing
- Hosting and security
- Support, maintenance and future improvements
Two more questions matter as much as the numbers: who owns the data, and who owns the code? With custom software you should own both. With SaaS, check what you can export and in what format.
Consider a hybrid approach
The best answer is often neither extreme. Keep standard tools for standard work, such as accounting and email, and build only the part that is genuinely unique to you, connected to everything else through APIs.
This is how we approach our own products. HEAL, our healthcare software, integrates with the hospital information systems that hospitals already run, so they can add a module without replacing what works. Transform, our de-duplication product, sits alongside existing systems and gives a single view of each customer, patient or product.
Questions to ask before you commission anything
- Which steps in this process are genuinely unique to us?
- What are people doing today in spreadsheets or by hand, and how much time does it take?
- Which systems must this work with, and do they have APIs?
- Who will own the code, the data and the cloud accounts?
- What happens if our needs change in two years?
- What does it cost us to do nothing?
The short version
Choose SaaS when the process is common, you can adapt to it and speed matters. Choose custom software when the process is how you compete, the rules are complex, or workarounds are already costing you time. And when the answer is somewhere in between, build only the part that makes you different.
Read next: How to choose a custom software development company.
Not sure which side of the line you are on?
A short conversation usually settles it. If an off-the-shelf product will do the job, we will tell you.
