Days. Sign up and configure.
Custom or off‑the‑shelf? An honest guide.
The right answer isn't always "build it". This is the framework we use with clients to decide between renting a ready‑made product and commissioning something bespoke — and why, for a lot of teams, the line runs straight down the middle.
Custom vs off‑the‑shelf.
A decision framework.
When to rent a SaaS product, when to build bespoke, and when to do both. The same questions we work through with clients before a single line of code — written plainly, no sales pitch.
The short answer.
If you only read one paragraph, read this one.
Off‑the‑shelf software is a shared, ready‑made product you rent and adapt to. Custom software is built around one organisation and owned by it. Off‑the‑shelf wins when your process is standard and you need to start now; custom wins when your process is your advantage, or when subscriptions and tool‑sprawl are quietly costing more than a build would. Most mature setups end up as a sensible mix of the two.
When each one wins.
Be honest about where you actually sit. The cost of choosing wrong is months, not minutes.
Off-the-shelf
Stay off‑the‑shelf if…
- Your process is fairly standard and a mainstream product covers most of it.
- You need to be live this week, not this quarter.
- The team is small and unlikely to grow fast.
- The tool isn't where your competitive edge lives.
Custom / bespoke
Go custom when…
- Your real workflow lives in spreadsheets beside the software because the software can't model it.
- Per‑seat licences climb every time you hire.
- You're stitching three or four tools together to do one job.
- You need to own the data, the roadmap, or both.
Side by side.
The trade‑offs that actually matter, on the dimensions clients ask about most.
Dimension
Off-the-shelf
Custom build
Time to start
Weeks to a first focused release, built around you.
Cost shape
Low to start, then a subscription that grows with every seat and add‑on.
Higher up front, then maintenance only — it doesn't scale with headcount.
Fit to your process
You adapt to the product. Workarounds accumulate.
The product adapts to you. The workflow is the spec.
Ownership
You rent access. The vendor owns the code and sets the roadmap.
You own the source and the data. The roadmap is yours.
Integrations
Whatever the vendor supports — and nothing they don't.
Anything with an API, wired in directly to your stack.
Changes
Request, wait, hope it's on their backlog.
Prioritised by you, built by the people who know the system.
It's rarely all or nothing.
The strongest setups we build are hybrids. Keep the commodity tools doing what they're good at — email, accounting, payments, calendars — and build custom only where your genuine advantage lives. The bespoke platform becomes the hub; the off‑the‑shelf tools plug into it through their APIs. You pay for software where it's worth paying for, and own it where ownership matters.
Common questions.
The ones that come up whenever this decision is on the table.
What is the difference between custom and off-the-shelf software?
+
Off‑the‑shelf software is a ready‑made product, usually rented as a subscription, that many organisations share and adapt to. Custom software is built specifically for one organisation, around its own processes, and owned by it. Off‑the‑shelf is faster and cheaper to start; custom fits exactly and costs less to run at scale.
When is off-the-shelf the right choice?
+
When your process is fairly standard, you need to be running this week, the budget is small, and a mainstream product covers most of what you need. For a lot of teams that's genuinely the right answer — and we'll tell you so.
When does custom software pay off?
+
When your workflow is too specific for a template, when per‑seat licensing climbs with every hire, when you're stitching several tools together to do one job, or when you need to own the data and the roadmap. The build costs more up front but stops the subscription compounding.
Is custom software always more expensive?
+
Higher up front, often lower over time. There are no per‑seat licences, so cost doesn't scale with headcount, and you're not paying for modules you never open. The crossover point depends on team size and how long you keep the system — our cost guide walks through what drives it.
Can you mix custom and off-the-shelf?
+
Almost always, and it's often the smartest route. Keep the commodity tools — email, accounting, payments — and build custom only where your real advantage lives, wiring the two together through their APIs.