Buy what fits, build what doesn’t. Five questions that help a small business choose, and the common mistakes in both directions.
Every business eventually asks whether to buy a ready-made tool or have something built. Both answers can be right. The trouble starts when the decision is made on price alone.
Start by buying
For common jobs, off-the-shelf software is usually the right call. Accounting, payroll, email, point of sale and standard booking are well served by products that thousands of businesses use. They are maintained, secure and improving every month.
Five questions to ask
- Is our process actually unusual, or do we just do it differently out of habit? Sometimes the cheapest fix is changing the habit.
- How many workarounds does the current tool need? Spreadsheets on the side, copy-and-paste, sticky notes and “ask Sam” are all signs of a poor fit.
- Does the tool connect to our other systems, or will someone retype data every day?
- What happens if the vendor changes their price or shuts the product down? Can we get our data out?
- Is this process a reason customers choose us? If so, owning it can be worth more.
When custom makes sense
Custom software earns its place when the work has rules that products don’t handle well. Some examples:
- Shared equipment that has to be requested, tracked, cleaned and repaired.
- An order that passes between several businesses, each needing to see where it is.
- A client checklist that changes depending on the type of application or service.
- Reporting that has to combine data from several tools into one weekly view.
The middle path
Often the best answer is both: keep the off-the-shelf tools for what they do well, and build a small custom layer that fills the gap. A dashboard on top of your booking and payment tools. An intake form that feeds your existing client system. An integration that removes the retyping.
Buy the standard parts. Build only the part that makes your business work the way it does.
Mistakes we see
Building too early, before anyone has written down how the process should work. And buying too much, where a large platform is bought for one feature and the team ends up working around the rest.
Whichever way you go, make sure you own your data, can export it, and know who to call when something breaks.
From the DYOL blog. Photo by Sebastian Svenson on Unsplash.
Keep reading
All posts
What the 2026 developer survey says about how software gets built
Most developers now use AI every day, and most only trust it when they can check it. What Stack Overflow’s survey tells business owners hiring developers.

How a little code changes a whole workday
Software doesn’t have to be big to matter. Small, well-placed tools remove the steps people repeat a hundred times a week.

AI is making accessibility easier. It doesn’t do it for you
Captions, alt text and plain-language rewrites are now quick to make. How to use AI for accessibility, and what still needs a person.
A free 20-minute conversation, then an honest assessment. You’ll know what it costs and how long it takes, in writing, at a fixed price.
Or email lloyd.delacruz@outlook.com. We reply within 24 hours.
