The handover is where systems go to die

Most business problems do not happen inside a tool.

They happen between people.

The lead moves from marketing to sales. The sale moves from sales to delivery. The project moves from the founder to the team. The site survey becomes a quote. The quote becomes a job. The job becomes a report. The report becomes an invoice. The customer question becomes an internal task.

Somewhere in that movement, context gets lost.

That is where systems go to die.

Everyone thinks the problem is the software. Sometimes it is. Usually, it is the handover.

The first person knows the detail. The second person gets the summary. The third person gets a task title. By the time the work reaches the person doing it, the useful context has been stripped away. What was obvious in the conversation is now hidden in a note, a memory, an email thread, or not captured at all.

Then people compensate.

They ask the same questions again. They check with the founder. They create their own spreadsheet. They send another message. They wait for clarification. They make assumptions. They redo work. They apologise to the customer. They lose time in small pieces until the business accepts the drag as normal.

This is why I am suspicious of big transformation talk.

Most businesses do not need a transformation first. They need to fix the handovers.

What exactly needs to move from one person, stage or system to the next? What format should it be in? Who owns it? What does good look like? What happens if something is missing? What can be automated? What must be checked by a human?

Simple questions. Huge consequences.

A bad handover creates risk because the next person is forced to work from partial information. In sales, that means weak follow-up. In delivery, it means avoidable mistakes. In customer service, it means repetition and frustration. In finance, it means delays. In operations, it means the founder becomes the glue.

That glue is expensive.

It also does not scale.

Founder-led businesses often survive on informal context. The founder knows the customer, the promise, the exception, the history, the risk and the workaround. That can feel efficient when the business is small. It becomes a ceiling when everything needs the founder’s memory to move.

The system should not depend on one person knowing what everyone else meant.

That is not resilience.

It is a queue.

AI can help handovers a lot, but only if the business is honest about them. It can summarise calls, turn notes into tasks, check forms for missing details, draft client updates, route requests, extract key points and prepare the next person. That is useful work.

But AI cannot fix a handover nobody has defined.

If the input is poor, the output will be poor with better grammar.

The first job is to map the movement of work. Not the imaginary process from a slide. The real one. The one with the WhatsApp message, the half-filled CRM field, the folder nobody uses, the email someone forwards because they are not sure where else to put it.

That is where the truth is.

Then decide what must be captured at each point.

For a sales-to-delivery handover, it might be the customer’s goal, the promised outcome, key dates, decision makers, risks, exclusions and success criteria. For a site visit, it might be location details, photos, constraints, recommendations and missing evidence. For marketing-to-sales, it might be enquiry source, pain point, urgency, offer interest and next action.

The right fields depend on the work.

The principle does not.

No handover should rely on someone remembering the important bit.

Once the handover is clear, tools become useful. The CRM can prompt. The form can structure. The AI assistant can draft. The automation can route. The dashboard can show exceptions. The team can trust the process.

That is when systems start working.

Not when every tool is connected, but when context moves cleanly.

A good handover feels boring. That is the point. The next person knows what happened, what matters, what to do and where to find the proof. The customer does not feel the joins. The founder is not dragged back into every decision.

Boring is underrated.

The handover is where systems go to die because nobody owns the gap between steps.

Own the gap.

That is where the value is.

The small test is to pick one customer journey and follow a single piece of information through it. Where does it start? Who changes it? Where is it copied? Where is it retyped? Where does it disappear? Where does someone have to ask again? That map will tell you more than most strategy sessions.

Fix that, and the business usually feels calmer very quickly.