Custom Software vs SaaS: Comparing Total Costs Over Three Years
To compare custom software with a SaaS subscription fairly, add up everything each option costs over the same three years: not just the monthly fee against the development quote, but setup, data migration, integrations, training, your staff's time, hosting, maintenance, manual workarounds and the cost of leaving. SaaS usually costs less to start and spreads its cost over time; custom software costs more up front and then mainly what it takes to run and change it. Which comes out cheaper depends on your number of users, how standard your process is and how much integration you need. Here is how to work it out with your own numbers.
Why the headline price misleads
A pricing page shows a price per user per month; a development quote shows one large number. Side by side, the subscription nearly always looks cheaper, but neither is the full cost. Compare the total cost of ownership: every cost you will pay over a fixed period, including your people's time. Three years is long enough for a custom system to be built and used, and short enough to estimate user numbers.
What you are actually paying for
The two options are not the same product at different prices. NIST's definition of cloud computing describes SaaS as using the provider's applications on the provider's infrastructure, where the customer does not manage that infrastructure "or even individual application capabilities, with the possible exception of limited user-specific application configuration settings". You rent a finished product: you can configure it, but not change how it works.
Custom software is built around your process and can be changed in any direction, but you, or your developer, carry responsibility for more of it. Microsoft's shared responsibility model shows the split: on your own servers you are responsible for the whole stack, while in SaaS the provider manages the operating system, network controls and physical infrastructure. In every model, though, the customer remains responsible for its data, user accounts and access management.
Cost components of a SaaS subscription
- Subscription fees. Usually per user, monthly or yearly. Multiply by the number of users you expect in each year, not today's headcount.
- Plan tier and add-ons. Depending on the vendor, extra storage, API access, detailed permissions, audit logs or single sign-on may be in a higher tier or sold separately.
- Price changes at renewal. Read what the contract allows; do not assume today's price will hold for three years.
- Setup and data migration. Fields, workflows and permissions have to be configured, and existing records moved in, cleaned and checked.
- Integrations. Connecting the product to your website, accounting or warehouse through built-in connectors, a separate integration service with its own subscription, or development.
- Training and administration. Initial training, plus the hours someone spends every month managing users and settings.
- Workarounds. Where the product does not fit, people fill the gap by hand – exporting, retyping, keeping side lists. Nobody invoices this, but it recurs.
- Leaving. The EU Data Act, which has applied since 12 September 2025, requires providers of platform and software as a service to make open interfaces available and, at a minimum, to export data in a commonly used, machine-readable format. According to the European Commission, switching charges, including data egress charges, are removed entirely from 12 January 2027; until then, providers may still charge the costs incurred. Test an export before you commit anyway.
Cost components of custom software
- Specification. Working out exactly what the software must do before development starts; skipping it usually moves the cost into later changes. Our guide to writing a brief for comparable quotes applies to software too.
- Design, development and testing. The main initial cost. Ask for it broken down by feature, so you can see what each part costs and what could wait.
- Data migration and integrations. The same work as with SaaS, but built for your systems.
- Hosting and running costs. Hosting, backups, monitoring, the domain and any paid services the software relies on, such as email delivery, text messages or maps.
- Maintenance. Fixing bugs, applying a security fix when a vulnerability actually affects your software, and adapting when something you depend on changes, such as an external API or a hosting provider ending support for a version you use. Working software does not need rebuilding every year just to stay on the newest versions; budget for changes with a concrete reason.
- Changes and new features. Optional and under your control, but your business will change in three years.
- Your own time. Someone in your company has to answer questions, set priorities and accept the work.
Make sure the contract states who owns the source code, the database and the hosting accounts; see our article on ownership of the domain, hosting, code and accounts.
An obligation both options share
Under the GDPR, a provider that processes personal data on your behalf is a processor. The European Data Protection Board's guide for small businesses says the contract must require the processor, at your choice, to delete or return all personal data after the end of the service. That applies to a SaaS vendor and to whoever hosts your custom software.
A three-year worksheet
Copy these tables into a spreadsheet and fill them in with quotes and your own estimates. Where unsure, enter a rough estimate: an empty cell counts as zero, and zero is almost never true.
| SaaS: cost item | Year 1 | Year 2 | Year 3 |
|---|---|---|---|
| Subscriptions (users × price per user × months) | … | … | … |
| Higher tier or paid add-ons | … | … | … |
| Setup and data migration | … | … | … |
| Integrations and their subscriptions | … | … | … |
| Training and administration time | … | … | … |
| Manual workarounds (hours × internal hourly cost) | … | … | … |
| Total | … | … | … |
| Custom: cost item | Year 1 | Year 2 | Year 3 |
|---|---|---|---|
| Specification, development and testing | … | … | … |
| Data migration and integrations | … | … | … |
| Hosting, backups and external services | … | … | … |
| Maintenance and fixes | … | … | … |
| Changes and new features | … | … | … |
| Training and staff time | … | … | … |
| Total | … | … | … |
Enter one-off costs (development, migration, setup) and recurring ones (subscriptions, hosting, maintenance) in the year you will actually pay them.
An illustration without real prices: with per-user pricing, a team growing from 10 to 25 people makes the year-three subscription line two and a half times the year-one line, before any price change. Running costs of custom software are not usually tied to internal user numbers in the same way, though hosting may need to grow with load.
Finally, note what you have at the end of year three. With SaaS, three years of service and the option to keep paying. With custom software, a system you own that still costs money to run. Neither is automatically better, but they are not the same thing.
When SaaS is the better choice
- the process is standard – accounting, payroll, email, file storage – and the vendor follows rule changes for you;
- you need the tool working within weeks;
- you have few users and expect slow growth;
- nobody on your side has time to manage a development project;
- you are still discovering how the process should work; a subscription you can cancel lets you learn before you build.
When custom software is worth considering
- the process is part of how you differ from competitors, and bending it to fit a product would cost you something;
- covering it would take several subscriptions, integration services and hours of manual workarounds;
- many users, including customers, partners or field staff, would each need a paid seat;
- your data has a structure no product was designed for.
The last point applies to auto-data.net, a catalogue of specifications for more than 57,000 cars, where the multilingual website, the Android and iOS app and a paid API run from one database. We describe the setup in one API for a website and a mobile app. There is also a middle route: keep SaaS for the standard parts of the business and build only the specific part, connected through APIs.
Questions to ask before comparing
- SaaS vendor: Which plan covers every feature we need, and what will it cost for the users we expect in year three? What does the contract allow at renewal? How do we export all data, including attachments and history? What limits apply to the API? Is there a data processing agreement?
- Developer: What does each feature cost, and which could wait? What hosting and external service costs should we expect each year? Who owns the code and the database? How is maintenance charged? What documentation do we receive?
If you have a SaaS offer on the table and wonder whether custom software would cost less over three years, send us a description of the process and the numbers you have. We develop web-based software – CRM systems, admin panels, APIs and integrations – and will help you fill in the worksheet honestly, including when the subscription is the better deal. Get in touch.