Everyone building software for a living has an incentive to tell you to build software.
So take this with that in mind: most businesses asking this question should buy something, and the ones who should build usually already know why.
Why is buying usually right?
Because you are not paying for the software, you are paying for everything around it.
A product used by ten thousand businesses has had ten thousand businesses find its bugs. It has documentation, support, a help centre, integrations with things you have not thought about yet, and someone whose full time job is improving it.
Custom software has none of that on day one. It has exactly the features specified, no documentation unless you paid for some, and one person who understands it.
You are also buying the discovery. A mature product encodes years of learning about what this kind of business actually needs, including the things you would not have specified because you have not hit them yet.
When is custom genuinely the right call?
Three cases, and they are narrower than they sound.
When how you work is the advantage. If your process is genuinely different from your competitors and that difference is why customers choose you, standard software will push you towards working like everyone else. That is a real cost, and it is the strongest argument for building.
When you need several systems to behave as one. This is integration rather than invention, and it is the most common legitimate reason. You keep your existing tools and build the connective layer that makes them talk. Far cheaper than replacing anything.
When per user pricing has stopped making sense. Some products cost more as you grow while delivering the same value. There is a point where a one time build plus hosting is cheaper over three years, and it is worth actually calculating rather than assuming.
Note what is not on that list: the product is nearly right but missing one feature. That is almost never worth building around.
What is the cost nobody quotes for?
Maintenance, and it is the reason most custom projects disappoint.
The build is the visible cost. Then there is hosting, security updates, fixing things that break when a browser or a payment provider changes, and modifying it when the business changes. That continues for as long as you use it.
A reasonable expectation is a meaningful annual cost relative to the build, every year, forever. If nobody has mentioned that, the quote is incomplete.
Off the shelf software has this cost too. It is called the subscription, and it is at least predictable and visible.
What about building it cheaply first and improving later?
Reasonable in principle, and it depends entirely on how the first version is built.
A small first version built properly can be extended. A small first version built to hit a price cannot, and you find out eighteen months later when the change you need turns out to require rewriting.
The question to ask whoever is quoting is not what it costs. It is what happens when you want to add something in a year. The answer tells you which kind you are being offered.
How do I evaluate off the shelf options properly?
Three checks that catch most bad choices.
Can you get your data out? Test this before committing, not after. Export everything, look at what comes out. If the answer is a locked format or a support ticket, that is a decision to stay whether or not it keeps working for you.
Does it integrate with what you already run? A tool that cannot talk to your accounting or your CRM recreates the retyping problem you were solving.
Is it still being improved? Check the changelog or release notes. Software that has not changed in two years is either finished or abandoned, and it is usually the second.
What is the hybrid answer?
For most growing businesses this is the right one and it gets overlooked.
Buy the standard pieces. Accounting, email, CRM, storage. These are solved and you have no advantage to gain.
Build only the connective layer and the one thing that is genuinely yours. The customer portal that shows your clients something specific to how you work. The internal tool that replaces the load bearing spreadsheet.
That keeps the custom surface small, which keeps the maintenance small, which is what determines whether this is a good decision in three years.
What would I ask before deciding?
One question: if this software vanished tomorrow, what would actually stop?
If the honest answer is that people would go back to a spreadsheet and cope, buy something cheap or do nothing yet. If the answer is that a core part of how you serve customers would stop working, you are in build territory, and you should build it properly rather than cheaply.
We recommend off the shelf software regularly, including when it means a smaller project for us. Tell us what you are working on.
