Decided
Issue 19 — May 27, 2026
CONTEXT
HoneyBook released research this week showing that 36% of customers stop working with a small business because it was hard to reach or slow to respond. That figure ranked above every other dissatisfaction trigger in the study, including lack of professionalism at 32% and inconsistent quality at 30%. The survey was conducted by The Harris Poll with 503 service-based small business owners and 1,002 of their customers.
The finding is straightforward on the surface. Customers want to hear back. They leave when they do not. But the study goes further than response speed. When customers described what responsiveness means to them, fast replies ranked first at 68%, but following through on inquiries came in at 65%, proactive updates throughout the engagement at 58%, reachability on preferred channels at 53%, and remembering prior conversations at 41%.
That is not a speed problem. That is a workflow problem. Each of those behaviors requires a repeatable, documented process behind it. Speed is the output. The process is what produces it.
HoneyBook released the research as part of its positioning around AI-powered CRM automation. The implied answer is more tooling and faster follow-up. That recommendation is not wrong. But the sequence matters.
"It works when the owner is available.
It breaks when they are not."
STRUCTURAL ANALYSIS
The data reveals a perception gap that HoneyBook names directly: small business owners are often investing in branding and polish while customers are prioritizing operational basics. Quality, consistency, responsiveness, ease of communication. Those are not features of a well-branded business. They are features of a well-run one.
Responsiveness gaps in small businesses usually come from one of several structural failures. The first is no defined process for follow-up. The owner handles inquiries when they remember, not on a schedule. There is no trigger, no checklist, no assigned next action. The second is a process that exists in the owner's head but is not documented. It works when the owner is available. It breaks when they are not. The third is a documented process that is not being followed consistently, either because it is too complicated or because no one is accountable for maintaining it.
In all three cases, adding automation does not solve the problem. In the first case, you are automating the absence of a process. In the second, you are building a system on top of an undocumented workflow that will conflict with the automation when the owner deviates from it. In the third, you are adding a tool to an accountability failure.
But there is a fourth case. A business with a clear, documented, consistently followed communication process that is simply outpacing the owner's capacity to execute it manually. In that case, automation does exactly what it is supposed to do. It extends a working process. That is the right order. Workflow first, then the tool.
ORDER CHECK
Before adding any automation to your communication workflow, work through these questions. Each one requires a documented answer, not a gut feeling.
1. Can you describe your current follow-up process in writing, step by step, from initial inquiry to closed engagement? If you cannot write it down, it is not a process. It is a habit. Habits do not automate well.
2. Is your follow-up process producing the right outputs when you follow it? If customers are leaving because of slow response times, but you have a defined process you are following, the process is the problem. Fix the process before automating it.
3. Are you failing to follow the process because of capacity, or because the process is unclear? Capacity problems can be addressed with automation. Clarity problems cannot. Automating an unclear process produces automated confusion.
4. Who is accountable for communication follow-through in your business? If the answer is no one, or it depends, accountability does not exist. A tool cannot substitute for it.
If you cannot answer all four questions clearly, you are not ready to automate your communication workflow. The tool will not solve the problem. It will make the problem move faster.
The question is not whether to automate.
The question is whether the process you are about to automate is working.
THE DECISION
The HoneyBook research confirms what operational diagnostics show in practice: responsiveness is the most visible symptom of a process gap. Customers experience it as the business being hard to reach. The actual cause is usually a workflow that is undocumented, inconsistent, or not owned.
If your communication workflow is documented, consistently followed, and producing the right outputs at lower volume, then automation is the right next move. The data supports it. The operational foundation supports it. Then automation becomes a logical next step.
If your workflow is not documented or not consistently followed, automation will not close the gap. It will widen it. Customers will receive faster evidence that the process is broken.
The question is not whether to automate. The question is whether the process you are about to automate is working. Answer that first.
Decide well,
Chuck
Decided
Weekly AI guidance for business owners making operational decisions.