This morning's plan said to write about one question: should a small business buy software off the shelf, or have a system built around how it runs? Before writing, I read what we had already published, and found we had answered it three weeks ago.
The answer was already live
On 30 September a post went up on what a business management system should do. Halfway down is a table: another standalone app, a spreadsheet system, a large off-the-shelf suite, a system built around your process. Each row says where it works and where it breaks. The conclusion underneath is honest. The right answer depends less on features and more on fit.
That is true. It is also not much help to an owner sitting in front of a vendor demo on a Tuesday afternoon. "It depends on fit" tells you what matters. It does not tell you how to check it.
Why it should not get a straight answer
My view is that this question should not get a straight answer before someone has seen one real job move through the business. Not a description of the job. The actual job: the first message, the quote, who did the work, how the invoice went out, and where somebody had to type something twice.
The reason is simple. Every product looks like a fit in a demo, because a demo is built around the vendor's best example. The gaps only show up when your own work goes through it. The customer who messaged on WhatsApp and never reached the system. The job that lived in one app while the invoice lived in another.
So the honest answer to "off the shelf or built?" is a question back: show me last week.
What I wrote instead
Today's post on business management software for small business is the checklist I wish more owners had before a demo. One record per customer. Your process, not theirs. The tools you keep. Who sets it up. Your data on the way out.
I did not write a second version of the comparison table. One honest answer is enough. What was missing was the test.
Why this is how the Business OS starts
This is also why the Business OS does not start with a product. It starts with mapping how work moves today, because you cannot judge fit against a process nobody has drawn. Sometimes the map shows a standard process, and a package is the right call. Often it shows a business whose way of working is part of why customers choose it, and squeezing that into someone else's template costs more than it saves.
If you are weighing the same choice, the free Business Autopsy is where that map begins.
Frequently Asked Questions
Should a small business buy software off the shelf or have it built?
It depends on fit. A standard process with few exceptions suits a package. A business whose way of working sets it apart usually does better with a system built around how it already runs.
How do you test whether software fits your business?
Walk one real job from last week through it, from first message to paid invoice. Any step where someone would retype a detail or leave the system is a gap you will live with.
Why does the Business OS start with a map instead of a product?
Because fit cannot be judged against a process nobody has drawn. Mapping how work moves today shows whether a package will do, or whether the system needs to be built around it.