We get the question constantly. "Why wouldn't we just use Salesforce? Or ServiceNow? Or whatever SaaS platform has a booth at the conference this year?" It's a fair question. The SaaS market is massive, growing, and full of genuinely good products. And yet, the enterprises we work with keep choosing bespoke. Not because they haven't heard of SaaS. Because they've tried it.
What You Need to Know
- SaaS works brilliantly when your process fits the tool. It fails when the tool has to fit your process
- Bespoke wins in three specific situations: unique workflows, deep integration requirements, and competitive differentiation
- The real cost of SaaS isn't the licence fee. It's the organisational change required to fit someone else's workflow
- Most enterprises end up with a hybrid: SaaS for commodity functions, bespoke for core operations
The SaaS Promise
The pitch is compelling. Someone else has already solved your problem. They've spent millions on development. They maintain it, update it, secure it. You just pay a monthly fee and get on with your business.
For a lot of functions, this works. Email. File storage. Basic CRM. Accounting. These are commodity processes where most organisations work the same way. The tool doesn't need to flex because the process is standard.
73%
of organisations use SaaS for at least one business function
Source: BetterCloud State of SaaSOps, 2018
But enterprise clients don't come to us for commodity functions. They come to us when the standard tool doesn't fit, and the gap between what the tool does and what they need it to do is costing them more than a custom build would.
The Three Situations Where Bespoke Wins
1. Your Workflow Is Your Advantage
Some organisations have developed processes over decades that are genuinely unique. A logistics company that's optimised its routing over 30 years. A healthcare provider with clinical workflows shaped by NZ regulatory requirements. A financial services firm with risk assessment processes that differentiate them from competitors.
Forcing these workflows into a SaaS product means stripping out the differentiation. The very thing that makes the organisation competitive gets flattened into someone else's generic process.
When a client tells me their process is unique, I'm sceptical. When they show me the spreadsheets and workarounds they've built around their current system, I'm convinced.
Isaac Rolfe
Managing Director
We had a client last year running a SaaS platform for their core operations. They had 14 spreadsheets running alongside it to handle the parts the platform couldn't. Fourteen. That's not using a SaaS product. That's working around one.
2. You Need Deep Integration
Enterprise doesn't run on one system. It runs on dozens, and the value is in how they connect. When a new system needs to integrate deeply with SAP, legacy databases, proprietary APIs, and custom data formats, SaaS products hit their limits quickly.
Most SaaS platforms offer integrations. But "integration" in SaaS terms usually means a REST API with standard endpoints and a Zapier connector. Enterprise integration means mapping complex data models, handling edge cases in legacy systems, managing real-time synchronisation across platforms that were never designed to talk to each other.
Custom builds let you design the integration architecture from the ground up. You're not limited by what the SaaS vendor decided to expose in their API. You build exactly the data flow you need.
3. The Total Cost Favours Custom
This one surprises people. SaaS looks cheap on paper. But enterprise SaaS pricing scales with users, features, and data. A platform that costs $50 per user per month sounds reasonable until you have 2,000 users and need the enterprise tier. That's $1.2 million a year. Every year. Forever.
A bespoke build has a higher upfront cost but a fundamentally different cost structure. You own it. You control the roadmap. You're not subject to pricing changes, feature deprecation, or vendor acquisition.
$1.2M
annual cost for a 2,000-user enterprise SaaS deployment at $50/user/month
For systems that will be used for five or ten years by hundreds of people, the total cost of ownership calculation often favours bespoke. Not always. But more often than the SaaS marketing would have you believe.
When SaaS Is the Right Call
Bespoke isn't always the answer. If your process is standard, SaaS is almost always better. You get faster time to market, continuous updates, and the benefit of the vendor's investment in security and compliance.
The organisations getting this right are the ones making deliberate choices. SaaS for commodity functions where the process is standard. Bespoke for core operations where the workflow is the competitive advantage. And clear integration between the two.
The Honest Conversation
What we tell every client considering bespoke is this: it's harder. It takes longer. It requires more of your team's involvement. You need to be in the room, making decisions, giving feedback, testing with real users. You can't just buy a licence and walk away.
But when your organisation's core operations depend on software that works exactly the way you need it to, that investment pays for itself. Not in the first month. But over years of having a system that fits your business instead of a business that fits someone else's system.