Decision guide
Bespoke software or off-the-shelf: which should you choose?
Buy the commodity. Build the part that is genuinely specific, valuable and difficult to support with existing products.
By the Voodoo AI product, design and engineering team
8 min read
01
The decision is rarely build everything or buy everything
Most strong operational systems combine standard services with custom workflow. Payments, transactional email, identity and accounting often belong with established providers. The differentiating journey, decision model or cross-team workflow may justify bespoke development.
The aim is not maximum ownership. It is a sensible boundary between capabilities the market already solves well and the parts of your operation that create advantage or persistent friction.
02
Choose off-the-shelf when the process is conventional
Existing software is usually the right first option when your needs follow a widely supported pattern and the team can adopt the product's operating model without damaging the service.
- The product covers the important journey with configuration rather than extensive workarounds.
- Subscription cost remains proportionate as users, records and integrations grow.
- Required exports, APIs and security controls are available on a suitable plan.
- The organisation can accept the supplier's roadmap and service dependency.
- Implementation and process change cost less than owning software development.
03
Consider bespoke when the mismatch is material
Custom software becomes credible when the cost of the gap is sustained and measurable, not merely because staff dislike an interface.
- A high-value workflow crosses several tools and repeatedly loses context or ownership.
- Your service model or rules are genuinely different from the products available.
- Clients or staff need one joined-up journey that configuration cannot provide.
- Licence, usage or transaction pricing becomes punitive at the expected scale.
- Control over roadmap, data or integration is strategically important.
04
Calculate total cost, including the awkward parts
For an existing product, include licences, implementation, consultancy, premium API access, data migration, process workarounds, parallel tools and exit cost. For bespoke development, include discovery, build, hosting, monitoring, support, security updates, product decisions and future change.
Compare a three-year scenario and state the assumptions. Bespoke software does not remove ongoing cost; off-the-shelf software does not remove implementation risk.
05
Run a short discovery before making the irreversible choice
Map the users, complete workflow, data, exceptions and current cost. Demonstrate the closest existing products against real scenarios. Prototype the few interactions that appear genuinely distinctive. Then decide whether to configure, integrate, build or change the process itself.
A good development partner should be willing to recommend an existing product when it solves the problem more responsibly. Bespoke development earns its place by fitting a valuable requirement—not by winning an argument against software subscriptions.
The GOV.UK discovery guidance recommends understanding the problem before committing to build a service. Read the source at GOV.UK Service Manual
06
A practical hybrid example
A service company might retain Stripe for payments, Microsoft for staff identity, an accounting platform for statutory records and Postmark for transactional email. A bespoke operational layer can connect client onboarding, delivery milestones, approvals and support around those services. The business owns the distinctive workflow without recreating regulated or commodity infrastructure.