Build or buy? Choosing software for a small business

The instinct is usually to build, because off-the-shelf never fits perfectly. That instinct is wrong more often than it is right, and expensively so.
Buy by default
Existing software is cheaper than you think and custom software is more expensive than you think. The gap is bigger than almost anyone estimates.
A subscription at 50 dollars a month is 600 a year. The equivalent custom build is rarely under five figures, and then it is yours to maintain forever.
Established products have also already survived problems you have not thought of yet: backups, security patches, the edge case that happens twice a year, the browser update that breaks something.
Buy unless you have a specific reason not to.
The reasons that genuinely justify building
The process is your actual advantage. If how you do the thing is why customers choose you, software that shapes it to someone else's assumptions is a real cost.
Nothing on the market fits without ugly workarounds. Not nothing is perfect, but you would be running three tools and copying between them by hand.
The subscription maths has turned. Per-seat pricing at forty people is a different conversation from four.
You need it to connect things that nothing off-the-shelf connects.
Note that none of those is it seems expensive. That one leads to building something more expensive.
The costs people forget on each side
Buying: per-seat pricing as you grow, paying for a tier because of one feature, the cost of getting your data out later, and the integration work that is never as simple as the logos on the page suggest.
Building: the build is the small part. Maintenance, hosting, security updates, the person who fixes it when it breaks at an inconvenient time, and the fact that every feature you add is now permanently yours. Budget for the life of it, not the launch.
The middle option most people miss
Buy the boring parts and build only the thin layer that is actually yours.
Payments, email, scheduling, accounting, storage: buy. Nobody has ever won a customer with a better payment integration.
Then build the small piece that reflects how you specifically work, and let it talk to the rest.
This is how most sensible small-business systems end up, and it costs a fraction of building the whole thing.
A test before you commit
Write down the five things the software must do. Not fifty, five.
Find the closest existing product and check it against the list honestly. If it does four of five, the gap is usually a workaround, not a build.
If it does two of five, and the three missing ones are the reason customers choose you, that is a real case for building.
The question underneath
Most build-versus-buy arguments are really about control: who holds your data, whether you can leave, whether a price rise is survivable.
Those are good questions, and you can answer them without building anything. Ask whether you can export your data, what it costs to leave, and what happens if they double the price. If you are comfortable with those three answers, buy.
Keep reading
Digital ProductsHow to price a digital productWhy cost-based pricing fails for files, how to price against the outcome instead, and what to do when nobody is buying at any price.
Digital ProductsWhat you need in place before selling digital productsThe practical checklist before your first sale: delivery, refunds, tax, licensing and the file itself, and which parts genuinely matter at the start.
SEOSEO or paid ads: which should you do first?The honest trade-off between search and paid traffic for a small business, what each actually costs, and the case where doing either one first is a mistake.
Comments