What should happen in the ten minutes after someone replies
Speed is not the whole of it. Six things have to happen after a prospect replies, and in most service firms all six wait on the same busy person. The Conversations program, pulled apart.
On this page
A prospect replies. Two words: "sounds interesting." That message is worth more than anything else that will land in your inbox today, and in most service businesses it will sit there until someone gets back from a job.
Everyone understands that speed matters here. What is less understood is that speed isn't the whole of it. A fast reply that asks a lazy question wastes the same opportunity, just faster. What has to happen in the minutes after a reply is a specific sequence of small pieces of work, and almost none of them are hard. They are simply not assigned to anyone.
This is the Conversations program, one of the eight programs that make up a working revenue setup. It's the one with the shortest window and the highest cost of failure, so it's worth pulling apart on its own.
What the ten minutes are actually for
When somebody replies, four things need to become true before the conversation can move forward.
- You know who they are. Not the name on the email. The company, the role, the size, whether they match what you sell, and what has already passed between you.
- You know what they meant. "Sounds interesting" from a decision maker at a right-fit company is not the same message as the identical words from someone doing research for a competitor.
- They have an answer that moves things. Not an acknowledgement. A response that either books time or asks the one question that decides whether time is worth booking.
- The business has recorded it. The CRM knows this happened, the opportunity exists, and the next step has a date on it, so it cannot fall into the gap we described in the gap it otherwise falls into.
Four things. In most firms, all four wait on one busy human, and they happen in the wrong order: the answer goes out first, off the top of someone's head, and the recording never happens at all.
The sequence, step by step
Here's what a worked reply looks like when the Conversations program actually exists. This is the shape of it, not a script.
The trigger
The reply lands and that event starts the work. Nobody notices it and decides to act. The arrival is the trigger, which means it works at 7am, during a site visit, and on a Friday afternoon.
The context pull
Before anything is written, the relevant history is assembled: who this person is, what company, what was sent to them and when, whether they have been in your CRM before, what they looked at on your site. This is the step that gets skipped most often when a human is doing it manually under time pressure, and it's the step that decides whether the answer sounds like it came from someone paying attention.
The read
The reply gets classified. Positive and ready. Positive but early. A question that needs a real answer. Wrong person, needs routing. Not interested, and whether that's a permanent no or a timing no with a date attached. Those five paths lead to genuinely different work, and treating them all as "a reply" is why so much of this goes wrong.
The draft
A response gets written in your voice, referencing the specifics, proposing a concrete next step rather than asking whether they would like to discuss further. If the right next step is a call, it comes with times, not a request for their availability.
The approval gate
The company defines which conditions need review. Routine messages can continue inside approved rules; pricing questions, unhappy tones, unusual asks, and anything outside those rules pause for a designated reviewer. The customer can change the rule, edit the draft, approve it, or veto it.
The record
The CRM is updated. The opportunity exists with the right stage. The next action has an owner and a date. If they said not yet and named a month, that month is now in the system as a real future task rather than a memory.
Why this one program pays for itself first
Conversations is usually the first place we would take work off an owner, for a plain reason: the demand already exists. Somebody has already raised their hand. You don't need a bigger budget or a new channel to capture it, you need the next six steps to happen reliably.
Tyler, co-owner at Martin Plumbing, is the clearest example we can point to. His close rate went from roughly one in five to three in four. Nothing changed about the pitch, the pricing, or the market. What changed was that inbound interest stopped waiting for someone to be free.
How to check yours
Pick a week. For every reply you received, write down the timestamp it arrived and the timestamp of the first substantive answer. Not an acknowledgement, a real answer. Then look at the gaps.
Two numbers matter. The median, which tells you what normally happens, and the worst one, which tells you what happens when you are busy. The second number is the honest one, because busy is the state you are trying to grow into.
Then ask the harder question: of those replies, how many are recorded in your CRM as opportunities with a dated next step right now? If the answer is fewer than all of them, the conversation program is not just slow, it is leaking.
What we would do about it
Conversations is one of the programs Revenue Engine runs inside a company’s existing inbox and CRM, in its own voice. You define the voice and handoff thresholds. Every reply and next step remains visible there, and Revenue Engine surfaces a slipping response-time median before it becomes a revenue problem.
You can see the wider mechanics on the Revenue Engine page or in how it works.
Measure your own gap for one week first. The median will be reassuring and the worst number will not, and the worst number is the one that decides what busy costs you. Send it over with your site if you want us to price it.
