Automate
Good enquiries are usually lost in the handover, not in the pitch.
Very few leads are lost because someone gave the wrong answer. They are lost because nobody was clearly holding them, the next step was in a person’s head rather than in the system, and by the time anyone noticed, the enquiry had gone quiet. This is the work of making that state explicit.
- Capability group
- Automate
- What that group is for
- Save time and run your business better
- Who it is for
- Sales and operations teams whose CRM is a system of record nobody updates, and whose pipeline is therefore fiction.
- Where it stops
- Lead and customer state, routing, follow-up and operational workflow inside CRM and adjacent tools. Building a new system to hold that state is a Custom Software & Digital Platforms project.
When the system stops describing the work
A CRM stops being useful the moment it is updated after the fact. Records get tidied before a meeting, stages are moved in a batch on a Friday, and the pipeline becomes a report of what people remembered rather than a description of what is happening. Everyone knows it, so the real state moves back into inboxes and conversations — which is precisely where it cannot be routed, reported or picked up by anybody else.
The question that exposes it is a simple one: who owns this enquiry right now, and what is the next thing that has to happen to it? If answering means asking someone, then an enquiry can go quiet without anyone noticing, and the handovers — marketing to sales, sales to delivery, delivery back to account management — are where that happens most.
The fix is rarely more fields. It is fewer stages that genuinely mean something, each with a clear entry and exit condition, an owner at every point, and automation that moves the record when the condition is met. Automate the movement and the reminders; leave the judgement with the person whose judgement it is.
Common signals
- The pipeline gets updated before a meeting rather than as the work happens.
- Who owns a particular enquiry depends on who you ask.
- Follow-up relies on someone remembering, so some of it simply does not happen.
- The handover from sales to delivery is a conversation with no record behind it.
- Two systems disagree about the same customer, and both are still consulted.
- Monthly reporting is rebuilt by hand and then argued with anyway.
What we can help with
We work with the CRM you already run wherever it can do the job, and say plainly when it cannot rather than bending it into a shape it was not built for.
- CRM structure
- The objects, fields and record types that reflect how you actually sell and deliver — kept deliberately small, because a field nobody fills in is worse than one that does not exist.
- Pipeline and stage design
- Few enough stages that each one means something, with an explicit condition for entering and leaving it. A stage that everything sits in is not a stage, it is a waiting room.
- Lead routing and ownership
- Enquiries assigned by rules you set — service, value, region, availability — so an enquiry has a named owner from the moment it arrives rather than after the first person to notice it.
- Follow-up automation
- Scheduled and conditional follow-up that stops the moment a human replies. Its value is in being reliable rather than clever, and in never contradicting a conversation already in progress.
- Reminders and escalation
- A record that has not moved when it should have raises something visible — to the owner first, then past them. Silent ageing is the failure mode this exists to prevent.
- Handovers between teams
- What has to be true before work passes from one team to the next, captured as a step in the system so the receiving side inherits context instead of asking for it.
- Data synchronisation
- Website, messaging channels, finance and delivery tools kept consistent with the CRM, with one system named as the owner of each field so a disagreement has a resolution rather than an argument.
- Workflow reporting
- Pipeline, ageing, response time, source and stage conversion assembled from the records themselves, on schedule — so the report is a by-product of the work rather than a monthly project.
How a CRM engagement usually runs
The state model is agreed before anything is configured, because automation built on the wrong stages is harder to unpick than no automation at all.
Map what actually happens
The real path an enquiry takes, including the informal steps and the exceptions people handle by memory. Written down in a form both sides agree is accurate.
Design the state model
Stages, entry and exit conditions, ownership at each point, and the small set of fields that genuinely drive a decision. Usually removes more than it adds.
Routing and follow-up
Assignment rules, acknowledgement, follow-up sequences and escalation configured against that model, with the failure cases decided rather than discovered.
Build and run in parallel
Live alongside the existing way of working until the records are demonstrably trustworthy. The old way is retired when the pipeline is right without anyone correcting it, not on the day the configuration is finished.
Reporting and revision
Reporting that comes out of the system, then a review of the stages themselves — a state model that is never revised stops matching the business within a year.
Where it connects
The closest neighbour is AI & Business Automation, and the split is worth being precise about. That page is the wider work of connecting tools and automating processes across them, including where a language model genuinely helps. This page is narrower and underneath it: the record of where a customer or lead actually is, who holds it, and what moves it on. Broader automations read and write that state, which is why it is worth getting right first.
Where the state you need cannot reasonably live in a CRM — because the process is unusual enough that every field is a workaround — the honest answer is a system of its own, which is a Custom Software & Digital Platforms project. We would rather say that than sell a configuration that fights the tool for the next three years.
It also connects back to the front of the funnel, and the CRM is what makes that connection measurable. Source, owner and time to first response are recorded against the enquiry itself, so a campaign can be judged on the leads it produced and what happened to them, rather than on the clicks it bought.
What to expect from us
- No promised improvement in response time, conversion or pipeline value. Those depend on how your team works, not on the configuration.
- A recommendation to remove a stage, a field or a step before automating it.
- A stage model your team can explain out loud without opening a diagram.
- Automation that fails visibly, so a stalled record is noticed rather than lost.
- Administrative access, documentation and the ability to change it yourselves.
Related
Work that usually sits alongside this
Pipeline telling you less than your team already knows?
Describe what happens to an enquiry today, from arrival to closed. You will get a straight view of which parts belong in the system, which belong to a person, and which are worth removing entirely.