Custom software or off-the-shelf: how to decide
Most software decisions are not really build-versus-buy. They are process-fit-versus-speed, and the answer changes depending on how much of your operation runs on the process in question.
Start with how your process differs, not what the software costs
Write down the five steps where your workflow departs from the industry default. If those steps are the reason customers choose you, a product that forces you back to the default will quietly delete your advantage. If they are only internal habits, configuration is almost always cheaper.
The licence price is the least useful number in the comparison. What matters is the workaround cost over three years: manual re-entry, exports stitched together in spreadsheets, and the staff time spent compensating for a tool that does not fit.
The three-year cost test
For an off-the-shelf tool, add licence fees, implementation, integration, training, and the internal hours spent on workarounds. For custom software, add discovery, build, integration, hosting, and a maintenance line of roughly 15 to 20 percent of build cost per year.
If the difference is narrower than you expected, choose the option that improves faster with your feedback. Vendors improve on their roadmap; custom systems improve on yours.
Where a hybrid honestly wins
Many businesses are best served by a product for the commodity layer (accounting, payroll, email) and custom software for the layer that faces customers or carries the process that differentiates them.
The connection between the two is where projects fail most often, so budget for integration explicitly rather than treating it as a detail to solve at the end.
Common questions
- Is custom software always more expensive than a subscription product?
- In year one, almost always. Over three years the gap narrows considerably once licence growth, workaround labour and integration costs are counted, and it can reverse when the product forces a process change that costs revenue.
- Can we start with a product and move to custom later?
- Yes, provided you keep your data exportable and avoid encoding logic in the vendor tool that you cannot reproduce. Ask for a full data export in the sales process, not after.
Next step
If this question is live in your business right now, describe the situation and you will get a written view on the options, including whether you should build at all.
Discuss your projectRelated notes
All insightsHow to write a technical brief that gets accurate quotes
The brief structure that separates a project that can be estimated from one that cannot, with the eight sections worth writing before you talk to any developer.
ReadStrategyRebuild or repair: an honest test for an ageing website
How to tell whether your existing website needs a migration or a targeted fix, using five checks that take an afternoon rather than a month.
ReadStrategyPlanning a technology budget that survives the year
How to split spend between build, maintenance and improvement so that the second year of a platform is funded before it starts.
Read