We have had the same conversation, with different versions of the same business, a great many times. An owner, often after a glass of something, explains that things are basically fine — but there are these bits, these repeating frustrations, that eat their week. We nod. We have heard these before. We have a reasonable idea, within a few minutes, which of six familiar shapes the bits belong to.
This piece is a plain description of those six shapes. Each is ordinary. Each is solvable. Most of them are solvable for less money than the owner usually expects, partly because the fix often involves subtracting complexity rather than adding it.
I. The leads that slip through the net
The symptom: enquiries arriving through four or five channels (the website form, email, the odd Instagram DM, a WhatsApp group, sometimes a phone voicemail) and occasionally disappearing. You are not sure how many. The team catches most of them, usually. There is a rough sense that some number of good enquiries never gets a reply.
The cost is larger than it feels. Enquiries that come in on a Friday afternoon and get a reply on Tuesday morning are already damaged enquiries. A lead that sits for three days has usually gone elsewhere or cooled so much that the conversation starts from scratch. If twenty per cent of enquiries experience this, and each enquiry was worth an expected £1,500 in revenue, the cost is not hard to work out.
The fix is not about technology. It is about deciding that every channel a customer can reach you through will go into the same inbox, that every enquiry will be acknowledged within an hour, and that every enquiry has a named owner within the working day. Then — and only then — automating those rules so they happen without a human having to remember. We wrote this up in more detail under Lead intake & routing.
II. The onboarding that scrambles
The symptom: you sign a new client, and there is a silence of several days while your team works out who starts what. Someone eventually asks the client for their brand assets; someone else asks for them again two days later; nobody is quite sure which documents were in the contract versus which still need to be collected. The first invoice goes out before the first deliverable has been scoped.
The cost is insidious because it mostly shows up in places you don’t attribute. Client NPS on the first-month question. Churn at the six-month mark among clients who say, in their exit interview, that the start “felt chaotic”. New-starter confusion in your own team, because everyone onboards clients slightly differently.
The fix is a repeatable onboarding per client type. Most businesses have two or three — a retainer client is not onboarded like a project client; a large client is not onboarded like a small one. Each has a fixed sequence of events over the first thirty days, a structured way of gathering documents, and a kick-off call that goes on the calendar at the same time as the contract goes out. The service page has the shape.
III. The invoices that go out late
The symptom: invoicing is a fortnightly event. Someone on the team sets aside a morning to go through the past two weeks and raise invoices for work completed. The work in question is sometimes two days old, sometimes two weeks old. Clients occasionally query dates. Cashflow is tolerable but not tight.
The cost is a combination of cashflow friction (a late invoice is a free loan to the customer) and internal morale (invoicing is nobody’s favourite part of the job). A business invoicing two weeks after work is delivered is carrying roughly fourteen days of revenue as a loan to its clients at any given time.
The fix is to trigger invoicing from the work itself. When a milestone is reached or a retainer period closes, the invoice drafts itself in the accounting system, ready for one click to send. Reconciliation runs itself against the bank feed. Chasers go out on a schedule the owner has agreed, in a tone the owner has written, without anyone having to type them each time. Billing & collections covers the pattern.
A business invoicing two weeks in arrears is making a free loan of two weeks of revenue to its clients, every day.
IV. The reporting that never quite happens
The symptom: the numbers exist, scattered across five or six tools. Pulling them into a readable summary takes most of a Friday, and most Fridays the moment arrives for someone else. The monthly board pack is assembled the weekend before the meeting. Different departments quote different versions of the same KPI in different conversations.
The cost is decisions made on feel rather than on evidence. The owner suspects the pipeline is fine, suspects the utilisation is high enough, suspects the DSO is not getting worse — and in that suspicion space, mistakes get made that a small amount of reliable data would have caught.
The fix is not a dashboard project. It starts with agreeing the six to ten numbers that actually matter (almost always fewer than the team initially proposes), writing a one-paragraph definition for each, and then piping those numbers into one place on a reliable schedule. The owner gets a two-minute weekly read in their inbox. No login required. The monthly pack assembles itself. See Reporting & dashboards for the longer form.
V. The knowledge that lives in three people’s heads
The symptom: there are a handful of people in the business who know how things actually work. When one of them goes on leave, the rest of the team quietly re-learns a few things each week. New hires take six weeks to reach productive contribution; the owner feels that this should be two.
The cost is fragility. A business in which institutional knowledge lives in three heads is a business with three dependencies it would rather not have. It is also a business that trains each new hire expensively and slowly, and one in which clients occasionally get slightly different answers to the same question.
The fix is to capture the knowledge deliberately — usually through structured interview sessions with the people who already hold it — and place it in a searchable layer that the team will actually use. The most common failure mode of knowledge bases is that they decay because nobody owns them; the fix to that is to assign owners, stamp pages with a last-reviewed date, and put the review on the calendar. Knowledge operations describes the approach.
VI. The follow-ups that eat the week
The symptom: someone on the team spends several hours a week writing personal-sounding follow-up emails. Many of them say similar things. Some of them go out late; some don’t go out at all. The person writing them is usually the most expensive person on the team.
The cost is twofold: the direct cost of the hours, and the indirect cost of the follow-ups that don’t happen, which are often the ones that would have tipped a deal over or recovered a late payment.
The fix is templates that don’t read like templates — follow-up sequences written once in the voice of the person sending them, triggered by the events that should trigger them (call happened, proposal sent, invoice paid, thirty days since last contact), and send-approved in batch rather than written in isolation. Almost every business we meet that does this well uses a mixture of CRM-native sequences and a lighter custom flow for the nuanced cases. This is not a service in its own right; it is usually a small slice of a larger onboarding or lead-intake engagement.
A small taxonomy and a bigger point
These six pains are not independent. A business that suffers from one of them usually suffers from three or four. Leads fall through; onboarding is scrambled; invoices go out late; reporting is unreliable; knowledge is private; follow-ups get skipped — and each of these is, in different ways, the same underlying failure: nobody has had the time or the standing to design the operation.
Hiring a firm to solve this is one answer. It is the answer we sell and we think it is often a good one. But it is not the only answer — some of this work can be done by a capable operations manager internally, given the time and the authority. If you happen to have one, keep them close. If you do not, come and talk to us.