Nobody notices the moment software becomes the constraint on a business. There is no outage. Revenue keeps growing, just slower than it should, and everyone has a reasonable explanation: the market softened, the team is stretched, hiring is slow. The systems get blamed last because they never actually broke.
I want to give you five symptoms that are specific enough to check this week. Not "your tech is holding you back," which is what every agency says, but observable things with a number attached.
Symptom one: someone's job is being a database
Look for a person whose week includes copying information from one system into another. An operations manager rekeying orders into accounting. A coordinator maintaining the real schedule in a spreadsheet because the actual tool cannot express it. An office manager who is, functionally, the integration layer between two vendors.
The number to get: hours per week, times their loaded hourly cost, times 52. It usually lands between $15,000 and $60,000 a year for one person, and the copying is the smaller half of the cost. The bigger half is that this work is invisible until they take a holiday.
Threshold: if any one person spends more than four hours a week moving data by hand, that is a build with an obvious payback.
Symptom two: growth costs more than it used to
Take the number of people it took to serve 100 customers two years ago. Compare it with today. In a healthy business that ratio improves as you learn. When software is the constraint it goes the other way, because every new customer arrives through the same manual funnel and the only lever available is another pair of hands.
This one is worth calculating even if nothing else in this article applies. If headcount per unit of revenue is flat or rising while your prices held, you are buying growth with labour, and labour compounds in the wrong direction.
Symptom three: the answer to "how many" takes a day
Ask a question about your own business that should be instant. How many jobs slipped last month. What our repeat rate is. Which customers are unprofitable. Then time the answer.
If it takes more than an hour, the data exists but is not connected. If nobody can answer at all, the data does not exist, which is worse and also more fixable. Businesses in this state make decisions on the loudest anecdote, which feels like instinct and behaves like a coin flip.
Symptoms four and five: the quiet no, and the named workaround
The fourth is expensive precisely because it never shows up in a report. A customer asks for something slightly outside how your systems work, and you decline. Not for a good commercial reason, but because the quote would have to be built by hand, or billing cannot represent it, or nobody could track it. Count these for a month. Most owners are surprised, and the ones who track it usually find the declined work is worth more than the fix.
The fifth is the softest signal and the most reliable, because you cannot fake it: when a process has an internal nickname, it has been broken long enough to become culture. The Friday spreadsheet. The shared inbox. The thing where you have to open two tabs. Nicknames are how organisations metabolise dysfunction into normality.
What this actually costs, in one example
A 40-person specialty distributor. Orders arrive by email and phone, get entered into a quoting tool, then rekeyed into accounting, then tracked in a shared spreadsheet for fulfilment. Two people spend roughly a day a week each on the rekeying. Nobody can say which products are actually profitable, so pricing is copied from last year with a percentage on top.
The visible cost is about two days of labour a week. The real cost shows up in three places nobody was measuring: margin, because pricing was guesswork; churn, because status questions took a day to answer; and growth, because every new account added the same manual load. None of that appears on a line item called software.
They did not need a platform. They needed order intake wired to accounting, one dashboard for margin by product, and status visible to the customer. Three pieces of plumbing, in the order that pays back fastest.
How to sequence a fix without betting the business
The instinct is to replace everything. Resist it. Replacements are where mid-sized companies lose a year and their appetite.
- Instrument first. Before automating anything, measure the manual process for two weeks. Without a baseline you cannot prove the fix worked, which is the same trap that sinks most AI pilots. Our piece on measuring AI ROI makes the case at more length.
- Fix the copying, not the tools. The two systems are usually fine. The gap between them is the problem, and integration is a fraction of the cost of replacement.
- Buy where you are ordinary, build where you are not. Payroll is not your edge. The thing your customers pick you for probably is. The reasoning behind that line is in build, buy, or AI.
- Ship in weeks, not quarters. If the first useful thing is more than six weeks out, the scope is wrong. Something smaller is hiding in there.
What this means for your business
- Pick the one symptom above with the clearest number and put a real figure on it this week. That figure is your budget, and it is usually larger than you expect.
- Rank by payback, not by irritation. The loudest annoyance is rarely the most expensive one.
- Treat a person who has become a data pipeline as a hiring problem you already have, not a software nice-to-have.
- If you cannot answer basic questions about your own numbers, fix visibility before automation. Automating a process you cannot measure just makes the same mistakes faster.
If two or more of those five symptoms sound like your week, the useful next step is not a proposal, it is naming the most expensive one. Tell us what the week actually looks like and we will tell you which piece we would build first and which we would leave alone. Occasionally the answer is that your systems are fine and the constraint is somewhere else, which is a cheaper thing to hear early. If it turns out you do want to hand the whole thing off, what to expect when you outsource software covers how that arrangement works in practice.