We build bespoke software for a living. So you'd think our answer to "should I build custom?" would always be yes. It isn't. Sometimes WordPress is the right call. Sometimes a SaaS product does exactly what you need. The question isn't custom vs off-the-shelf. It's whether the problem you're solving has already been solved well enough by someone else.
What You Need to Know
- Off-the-shelf works when the problem is common and well-understood
- Bespoke wins when your process, users, or constraints don't fit existing tools
- The worst outcome is building custom when you didn't need to, or forcing a platform when you did
The Real Question
Most organisations don't come to us saying "build us something custom." They come saying "we tried three platforms and none of them do what we need." That's the signal.
Off-the-shelf software solves common problems. Accounting, email, project management, content management for a marketing site. These are well-understood domains with mature products. If your needs fit inside those products, you should use them. Full stop.
But here's where it breaks down. When your organisation has a process that's genuinely different from the industry default, platform software forces you to change how you work to fit how the tool works. You end up with workarounds. Spreadsheets running alongside the system. Manual steps that should be automated but can't be because the platform doesn't support your flow.
31%
of software projects fail to meet their objectives
Source: Standish Group CHAOS Report, 2014
That stat cuts both ways. Custom projects fail when they're poorly scoped. But platform projects fail too, quietly, when the tool can't actually do what the organisation needs. Nobody counts those failures because the software technically "works." It just doesn't solve the problem.
When Bespoke Is the Right Call
We've done enough projects now to see the pattern. Custom software makes sense when at least two of these are true:
The process is yours. Not an industry standard. Not a common workflow. Something your organisation does differently, and that difference is a genuine advantage you want to keep.
The users are specific. Enterprise tools used eight hours a day by people with specific roles need to fit those roles precisely. Generic interfaces create friction that compounds across hundreds of users and thousands of hours.
Integration is non-negotiable. When the system needs to talk to three other internal systems, pull data from external sources, and present it in ways that don't exist in any product on the market.
The problem hasn't been solved before. This is the one that gets us excited. A client comes to us with a challenge and we look at the market and there's nothing. No product. No template. Just a problem that needs a solution built from the ground up.
The best custom software we've built replaced processes that were running on a combination of email, spreadsheets, and institutional memory. The brief was never "build us an app." It was "this is broken and we can't find anything that fixes it."
Isaac Rolfe
Managing Director
When Off-the-Shelf Wins
We've talked clients out of custom builds. More than once. If a WordPress site with the right theme and plugins does everything you need, spending six figures on a bespoke CMS is a terrible use of money. If Xero handles your accounting, you don't need a custom finance system.
The honest answer is that off-the-shelf wins most of the time for most organisations. Custom software is for the gap where products don't reach. The trick is knowing which side of that line you're on before you start spending.
A 2014 survey by Panorama Consulting found that nearly 60% of ERP implementations exceeded budget, often because the off-the-shelf system required more customisation than expected. That's the trap on both sides. Custom projects have scope risk. Platform projects have fit risk. Neither is safe. You just need to pick the risk you can manage.
How We Think About It
When a client comes to us, we start with the problem, not the solution. What are you trying to do? Who uses it? What have you tried? What didn't work?
If the answer points to a product that already exists, we'll say so. We'd rather build the right thing than build a thing.
But when the answer points to a gap, when the process is unique, the users are specific, and nothing on the market fits, that's where IDESIGN does its best work. We scope it honestly, we build it to the actual requirements, and we deliver something that solves the problem the client actually has. Not the problem a product vendor assumed they'd have.
The distinction matters more than people think. And it's worth getting right before you write a single line of code.