Custom software vs off the shelf: what SaaS really costs, and when building pays off

Prices checked 19 October 2026.

For most teams, off-the-shelf software is the right buy, and we say that as a company whose main service is building custom software. Custom pays off in two cases: when the software is the process that makes you different, or when the seats, tier upgrades and workarounds around a tool cost more than owning something that fits. Outside those cases, keep the subscription.

That is the short version of custom software vs off the shelf (in Europe you'll hear it as bespoke software vs off the shelf; same question). The rest of this post puts real list prices on the SaaS side, and our own published prices on the custom side, so you can run the numbers for your team. If you already know your tool is a commodity, skip to the five-question test near the end.

Custom software vs off the shelf: the short answer

What off-the-shelf software really costs

The sticker price is per user, per month. The bill is that number multiplied by people, by months, and by the tier you end up needing.

Seats add up

Salesforce publishes its Sales Cloud list prices: Starter Suite at $25, Pro Suite at $100 and Core at $195 per user per month, with Pro Suite billed annually (Salesforce pricing, checked 19 October 2026). The same page lists Pro Suite at £80, €100 and AU$140, and Core at £156, €195 and AU$273.

Here is plain arithmetic on those list prices, for a 20-person team, before discounts or other add-ons:

Discounts, other add-ons and contract terms will move the real number. The shape holds, though: the cost grows with every hire, every year, for as long as you use the tool.

Add-ons and tier jumps for one feature

Say the one thing you need is to connect the CRM to your own systems. Salesforce's pricing page lists the Web Services API on Pro Suite as "Additional $25 USD/user/month", and its FAQ says Core includes APIs (Salesforce pricing). The add-on is the cheaper route, but it's still charged per seat. That's the second row in the table: on 20 seats, API access adds $6,000 a year, and the figure grows with every hire.

Run the same check on any pricing page you're comparing. Find the tier or add-on that covers the integration or admin feature you need, then multiply it by every seat, because plans like these are priced per user.

Price rises you don't control

On 1 August 2025, Salesforce raised list prices for Enterprise and Unlimited Editions of Sales Cloud, Service Cloud, Field Service and some Industries Clouds "by an average of 6%" (Salesforce newsroom, 17 June 2025).

Microsoft did the same from 1 July 2026: Microsoft 365 Business Basic went from $6.00 to $7.00 per user per month, and Business Standard from $12.50 to $14.00. Existing customers keep their current price until renewal (Microsoft Licensing, 16 February 2026).

Both vendors tied the rises to new features, and that may well be fair. It's still your budget, set on their calendar.

Workarounds and integrations

The cost nobody invoices is the spreadsheet that copies data between two tools every Friday, or the custom field someone bolted onto the CRM three years ago. The UK government's technology guidance puts it bluntly: "Even small modifications to OTS software can remove most of the benefits of using it." It lists what changes, customisations and workarounds do, including that they "increase costs", "make maintenance harder" and can "restrict you from upgrading or removing them in future" (GOV.UK, Define your purchasing strategy).

So count the hours. If two people spend part of every week moving data by hand, that time is part of what the software costs.

Disadvantages of off-the-shelf software, and its real advantages

You depend on the vendor's roadmap. If they drop a feature you rely on, your options are to adapt or to leave.

The advantages are just as real, and for most businesses they win:

• You can start this week. The product exists, and so do the help docs.
• Someone else patches it, hosts it and keeps it running.
• Other customers have usually hit the common bugs before you do.
• Common jobs (email, accounting, payroll, a standard sales pipeline) are solved problems. Rebuilding them buys you nothing.

When custom software pays off

GOV.UK's guidance gives a clean test. It says you might choose to build if your user need is unique or rare, if few suppliers can meet your requirements, if you "cannot scale, adapt or integrate available commercial products to meet your core needs", or if you need to own the technology to keep the flexibility to modify it (GOV.UK).

In business terms, custom pays off when:

1. The process is how you win work. A quoting engine, a scheduling rule set, a client portal that does what your competitors' don't.
2. You're paying top-tier seats for a whole team because a few people need one feature.
3. The workarounds have become a job. Someone's week is spent keeping two systems in sync.
4. You need the data and the code to stay yours, because the system is central to the business.

That is the work we do on our custom software development service: a written scope before the first sprint, with what's out of scope named, a running build you can click every fortnight, and a repository you keep. If the brief is still fuzzy, we run a short architecture pass first.

When off-the-shelf wins (most of the time)

Off-the-shelf wins whenever the job is the same in every business. The UK government's technology blog uses email as the example: "you're better off buying an email service than building it yourself", while an organisation whose core job is checking passports might build the passport-checking tool (Technology in government, 3 February 2021).

Bespoke software has its own disadvantages, and you should hear them from a company that sells it. You own the bugs. You pay for hosting, updates and the next change. If the people who built it leave and nobody wrote anything down, you're stuck. Building a CRM because Salesforce costs $100 a seat is usually a bad trade.

The middle path: keep the tool, add automation or a small build

Often the cheapest fix is to keep the SaaS that does the common job well and close the gap around it.

• If the gap is moving data between tools, sending follow-ups or logging enquiries, that's an automation job. Our automation service builds and runs those, and a person approves what goes out. We also offer Automation Lite, which our pricing page describes as: "We set up a free automation for you, and you manage it on our platform at no cost." It's a small automation set up for your business on a booked call, and it stays free.
• If the gap is a feature the SaaS will never have, a small custom service beside it (a portal, a calculator, an internal tool reading the SaaS through its API) can cost less than moving the whole team up a tier. Check whether your plan includes API access or sells it as a per-seat add-on first.

We wrote more on where automation pays off for a small business.

Build vs buy software: what custom costs after launch

After launch, custom software costs maintenance, hosting and changes every month, so a fair build vs buy software comparison counts those next to the build. Here are our prices, from our pricing page (USD starting prices; the quote follows the written scope):

Maintenance is the line people forget. Software you own needs patches, backups and someone to answer tickets, and that is a monthly cost like a subscription, only it doesn't grow per seat. DevOps is what gets a change from a commit onto a server without a ritual: pipelines, infrastructure as code, and cloud accounts you keep. Security testing belongs in the plan too, and our penetration testing page covers that side.

Go back to the $24,000 a year for 20 Pro Suite seats. Maintenance at our starting price comes to $4,200 a year for one app ($350 × 12). That comparison is incomplete on purpose: it leaves out the build itself, which for a web application is quoted after scope, and the hours your own team spends on the project.

It does show why the answer turns on headcount. Ten seats and twenty seats give very different SaaS totals, while our maintenance is priced per site or app, not per user.

Exit and data: what happens when you leave

With SaaS, leaving depends on the vendor's export tools and your contract. With custom software, you already hold the code. GOV.UK's Service Manual says the most important thing when choosing technology is to make choices that let you "change your mind at a later stage" (GOV.UK Service Manual).

In the EU, the Data Act now backs that up for cloud services. Providers of software and platform services must offer open interfaces and export your data "in a commonly used and machine-readable format", and from 12 January 2027 they can't charge you switching or data egress fees (European Commission, Data Act explained; legal text: Regulation (EU) 2023/2854). Outside the EU, your contract decides, so read the export clause before you sign.

You still need a tested backup and someone who can run it. We wrote about what happens when a vendor goes silent in The vendor that stopped answering.

A five-question test before you build

Go through these with whoever signs the software bills.

1. Is this job the same in every business (email, payroll, accounting)? Then buy.
2. Have you priced the right tier for every seat, for three years, including the price rises above?
3. How many hours a week go into workarounds, and whose hours are they?
4. Would a small automation or integration close the gap without replacing the tool?
5. If you build, who maintains it next year, and is that in the budget?

If the answers point to a build, send us the brief on our software development page. If you want a second opinion on the decision first, our IT and technology consulting covers architecture and stack reviews.

FAQ

Is custom software cheaper than off-the-shelf in the long run?

Sometimes, not always. SaaS costs grow with every seat and every price rise; custom software costs more upfront and then needs maintenance. Price your actual tier for every user over several years, add the hours spent on workarounds, and compare that with a build quote plus monthly maintenance. For common jobs, off-the-shelf usually stays cheaper.

When should a small business build custom software?

When the software is the process that sets you apart, when you can't adapt or integrate a product to meet a core need, or when workarounds have become someone's job. GOV.UK's build criteria are a good checklist. If none of those apply, buy.

What is the difference between bespoke and off-the-shelf software?

Off-the-shelf software is a ready-made product sold to many customers, usually as a monthly subscription per user. Bespoke (custom) software is built for one business to a written scope, and the business keeps the code. "Bespoke" is the more common word in Europe; "custom" in North America.

Can I keep my SaaS tools and add custom features?

Yes, and it's often the best option. A small automation or a custom tool that reads and writes through the SaaS API can close a gap without moving everyone to a higher tier. Check how your plan handles API access: on Salesforce Sales Cloud, Pro Suite lists the Web Services API as an add-on at $25 per user per month, and Core includes APIs.

What happens to my data if I leave a SaaS product?

It depends on the contract and where you are. In the EU, the Data Act requires software and platform providers to export your data in a commonly used, machine-readable format, and from 12 January 2027 they can't charge switching fees. Elsewhere, check the export clause and test an export before you need it.

Ready to compare your own numbers?

Send the brief through our custom software development page, or book a free 30-minute assessment. We'll tell you if off-the-shelf is the better buy. Starting prices for every service are on our pricing page.

How this guide was made: Ramin Moradi researched and wrote it with AI assistance. Every price and quote was checked against its linked source on 19 October 2026. Vendor prices change, so check each source for the current figure.

Sources

1. Salesforce, Sales Cloud pricing. https://www.salesforce.com/sales/pricing/ (read 19 Oct 2026)
2. Salesforce, "Updated Product Packaging and Pricing Offer New AI Capabilities and More Ways to Scale AI Throughout Every Organization", 17 Jun 2025. https://www.salesforce.com/news/stories/pricing-update-2025/
3. Microsoft Licensing, "Microsoft 365 Pricing and Packaging Updates", 16 Feb 2026. https://www.microsoft.com/en-us/licensing/news/2026-m365-packaging-pricing-updates
4. GOV.UK, "Define your purchasing strategy". https://www.gov.uk/guidance/define-your-purchasing-strategy
5. GOV.UK Technology in government, "To build or to buy – that's the technology question", 3 Feb 2021. https://technology.blog.gov.uk/2021/02/03/to-build-or-to-buy-thats-the-technology-question/
6. GOV.UK Service Manual, "Choosing technology: an introduction". https://www.gov.uk/service-manual/technology/choosing-technology-an-introduction
7. European Commission, "Data Act explained". https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained
8. Regulation (EU) 2023/2854 (Data Act), EUR-Lex. https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng