How do I know if my requirement is genuinely bespoke?
A requirement is genuinely bespoke when it is the thing you compete on, not merely the thing you find annoying. Three questions usually settle which one you have.
Would a competitor doing the same job need something different? If the answer is no, an off-the-shelf product almost certainly exists for it, and the search is cheaper than the build. Businesses routinely commission custom software for problems that thousands of other businesses have, which is exactly the situation the software market is good at.
Is the awkward part the process, or the software? A lot of bespoke projects are commissioned to encode a way of working that nobody has examined in years. Building custom software around it does not fix it. It makes it permanent and expensive to change.
What happens if you do nothing for six months? If the honest answer is "we carry on, mildly irritated", you have a preference. If it is "we cannot take on the new contract" or "we lose the audit", you have a requirement.
It is also worth knowing that this is not a yes-or-no decision. There are five positions, not two: off-the-shelf, configured, extended, integrated, and fully bespoke. Cost steps up sharply between extended and integrated, because that is where you stop buying a product and start owning a system that has to be hosted, secured, updated and understood by someone. Most businesses that believe they need the last position need the third.
Dropping a row down that list because of one missing feature is the most common expensive mistake in this category.
If you would rather work it through properly, the build vs buy calculator asks six questions and gives a straight answer, including when the answer is neither.
Read the full guide to bespoke software development in the UK →
Read more: Bespoke Software Development in the UK