Bespoke software
Bespoke software is software designed and built for one organisation, to fit a process that organisation already has. It is the opposite of an off-the-shelf product, which many organisations licence and adapt their own processes to fit, and it is owned by the business that commissioned it.
Also known as: Custom software, Custom-built software, Tailor-made software
Last reviewed
Why bespoke software matters
Off-the-shelf products encode one way of working — usually the most common one. That is exactly what you want for payroll or accounting, where being unusual has no value. It is a problem when the process in question is part of why customers choose you, because adopting the product means adopting everyone else's workflow.
Bespoke software exists for that second case. It fits the process rather than the other way round, which means nobody has to work around it, and the way you do the thing stays yours rather than becoming whatever your vendor supports.
How a bespoke project works
A bespoke build starts with scoping rather than code: establishing what the software must do, who uses it and what it connects to. On our projects that is a fixed-scope planning engagement — Quickstart App Planning typically completes within 3 to 6 weeks and produces the scope and the estimate.
Delivery then happens in increments. In our projects that means fixed two-week Velocity Sprints, with most projects aiming to launch a usable first version within 2 to 8 weeks, typically across 2 to 4 sprints, committed one at a time. The first release is deliberately narrow; it earns the next one.
Bespoke vs off-the-shelf
The honest comparison is not about features. Off-the-shelf is faster and cheaper to start, spreads development cost across every other customer, and hands maintenance to the vendor — but you adapt to it, you pay per user indefinitely, and your competitors can buy the same thing.
Bespoke costs more up front and you own the upkeep, but it fits exactly, integrates with anything you run, and cannot be repriced or discontinued under you. The full comparison is in our guide.
When you need it
Build when the process is an advantage rather than overhead, when no product covers roughly 80% of the outcome, when staff maintain spreadsheets alongside a product to hold what it cannot, or when the software is itself the thing you sell.
The spreadsheet signal is the most reliable of the four. A file people keep updating next to a system they already pay for is a precise specification of what that system cannot do. Under our published floor a bespoke project under £7.5k is unlikely, so the process needs to be worth at least that before building is the right answer.
Bespoke software: common questions
Yes. Bespoke is the more common phrasing in the UK and custom is more common in the US, but they describe the same thing: software built for one organisation rather than licensed as a product. Tailor-made and made-to-measure are occasionally used for the same idea.
That depends on your contract, so agree it before work starts. Ownership of the source code, the data and the hosting arrangement should all be explicit. Where a build reuses open-source components or a supplier's existing framework, the terms covering those parts should be written down too.
It needs an owner. Hosting, monitoring, dependency updates and security patching continue after the project ends, and someone has to decide what gets built next. A bespoke system with nobody accountable for it degrades into the legacy problem it was built to replace.
Want to talk about your project?
Tell us what you’re trying to achieve and we’ll map the fastest credible path.