Most businesses that come to us believe they have a technology problem. The website is old. The CRM is “not working.” Someone has suggested an app. The instinct is to buy or build the next tool.
In most cases, that instinct is wrong — not because the tools are fine, but because the tool is not the problem. The problem is that nobody has answered a more basic question: where, specifically, is the business losing money?
Three symptoms that look like technology problems
“Our website doesn’t generate leads.” Usually the website is not the constraint. Traffic arrives, some of it converts, and then the enquiry sits in an inbox for two days. The prospect has moved on. The site did its job; the follow-up system did not exist. Rebuilding the website will not change the outcome.
“Our CRM isn’t working.” A CRM that is not working is almost always a CRM that is not connected. Leads arrive from the website, the phone and social media; only one channel reaches the CRM; the pipeline is incomplete; the team stops trusting it and goes back to spreadsheets. The software is fine. The system around it was never designed.
“We need an app.” Sometimes true. More often, the business needs customers to book, pay or check status without calling — and a well-built web portal does that for a fraction of the cost, with no app-store friction. The word “app” is a symptom of a desire for self-service, not a specification.
What a systems problem looks like
A systems problem has a recognisable shape:
- The same information is typed into more than one place.
- A process depends on a specific person remembering to do something.
- Nobody can state, from data, how many enquiries became customers last month.
- Tools were bought one at a time, for one team at a time, and do not share data.
- Growth increases workload faster than it increases margin.
None of these are solved by a better tool. They are solved by designing the flow — traffic, capture, qualification, conversion, delivery, retention — as one connected system, and only then deciding which technology each stage requires.
The economic test
Before any build, we ask the same question: if this works exactly as intended, which number changes, and by how much?
If the answer is “lead-to-appointment rate, from roughly one in eight to one in four,” you have a business case and a specification. If the answer is “we’ll have a modern website,” you have a cost.
This test is uncomfortable because it sometimes concludes that the right investment is small — a follow-up sequence and a booking link, not a platform. That is a feature, not a limitation. Technology that does not change the economics is an expense, however impressive it looks.
What to do instead
- Map the flow. From first contact to repeat purchase, on one page. Mark where information changes hands.
- Put numbers on the stages. Even rough ones. Enquiries per month, response time, conversion at each step, cost to serve, repeat rate.
- Find the leak. The stage where the numbers drop hardest is where the leverage is.
- Design the system for that stage. Then, and only then, choose the technology.
Businesses that do this usually discover they need less technology than they feared, connected more carefully than they expected. That is the difference between a technology problem and a systems problem — and it is the difference between spending and investing.
