How a lead becomes revenue: an owner's map
A lead becomes revenue through six steps: inquiry, first reply, call, proposal, signed and kickoff. Between each pair is a handoff where the lead waits for someone. Write down who owns each handoff, time the wait with a timestamp column, and fix the longest wait first, because it is the biggest share of the time a lead spends waiting.
You know roughly how many leads came in last month, and roughly how much work you signed. What happened to the leads in between is usually a guess. This exercise swaps the guess for a map you can draw in an afternoon, with a spreadsheet, your sent folder and your calendar.
Six steps and the handoffs between them
Most agencies, consultancies and implementation shops run some version of the same path. A lead sends an inquiry, someone sends the first reply, you have a call, a proposal goes out, the client signs, and the work kicks off. Before anything gets built, map this path and mark where work waits.
- Inquiry
- The handoff you measure firstFirst reply
- Call
- Proposal
- Signed
- Kickoff
A handoff is any moment the lead moves from one person or tool to another, or sits overnight waiting for someone. Each step is usually fine on its own. Leads stall in the gaps, at a handoff that nobody owns.
Who owns each handoff, and how to time it
For each handoff, write down the one person who moves it forward. A shared mailbox or a team channel is a place where leads sit, so it can't be the owner. Then time the wait, in one of two ways.
- A stopwatch, for the first reply. Send an inquiry through your own website form from a personal address, start a stopwatch, and stop it when a reply lands. Try it once at a quiet hour and once at a busy one.
- A timestamp column, for everything else. In a spreadsheet, give each lead one row and each step one column, and fill in the date and time each step happened. The sheet can subtract one column from the next, which gives you the wait at every handoff.
| Handoff | Owner | How to time it | What a stall looks like |
|---|---|---|---|
| Inquiry to first reply | Whoever reads the inbox the form lands in, often nobody by name | The time on the lead's email or form against your first sent reply, or the stopwatch test above | Leads answered the next morning, or answered from someone's personal mailbox where nobody else can see the thread |
| First reply to call | The person who sends the booking link | The date of the first reply against the date the call happened, from your calendar | Days of back and forth about times, or a booking link sent once and never mentioned again |
| Call to proposal | Usually the owner, because scope and price sit with you | The call date against the date the proposal was sent, from the sent folder or the proposal tool | The proposal waits for a free afternoon, so it goes out a week after the call |
| Proposal to signed | The owner, or whoever sent the proposal | The date sent against the date signed, from the signing tool or the email that says yes | The proposal goes out with no follow-up date, then the conversation goes quiet and nobody asks why |
| Signed to kickoff | The person who runs delivery | The signed date against the date of the kickoff call | The client signs, then waits on a welcome email, access requests and an invoice before anyone starts |
Where leads drop off the map
The timings tell you where leads wait. The blanks in the sheet tell you where they stop. A lead dies in one of four places, and each one shows up on the map in its own way.
- Never recorded. The lead came by phone, a direct message or a referral to someone's personal mailbox, so it never reached the sheet at all. Ask everyone who takes leads where theirs came from last month, and compare that with the rows you have.
- Never answered. The row has an inquiry time and a blank where the first reply should be. This is the first handoff failing.
- Never followed up. The row stops after a reply, a call or a proposal, with nothing booked next and nobody holding a date. The lead went quiet, and so did the business.
- Never closed out. The proposal is still open months later, with no decision either way. It can't be won, lost or reworked, so it sits in the pipeline and makes the total look bigger than it is.
Fix the slowest handoff first
Once the sheet is filled in, look at the typical wait at each handoff and mark the longest one. That is your bottleneck: the place where work queues for the person or step with the least spare time. Speeding up a step before it only makes the queue there longer.
Use the middle value for each handoff, and leave the average alone. One lead that took a month will drag an average up and hide the pattern you are looking for.
The fix depends on which handoff it is. A slow first reply needs a named owner and a draft ready to send. A slow proposal needs the call notes captured in one place, so the first draft starts from a template. A proposal that goes quiet needs a follow-up date set the moment it goes out. A slow kickoff needs the welcome email, access requests and invoice to start from the signature.
Who keeps the map
The map belongs to the owner, or to the one person who answers for revenue. Update the sheet weekly while you are fixing a handoff, then monthly. If a handoff still has no name next to it after this exercise, that is the first gap to close, before any tool or automation.
If you would rather start from your own answers than a spreadsheet, the lead leak finder asks three yes or no questions about each place a lead can die and names the worst one.
Questions
When does the clock start on a new lead?
When the message arrives, whether or not anyone has seen it. Use the time stamped on the email or the form submission. Stop the clock at the first reply a person would read as an answer, so an automatic acknowledgement doesn't count.
Do I need a CRM to map this?
A spreadsheet is enough for the first pass, with one row per lead and one column per step, and it is easier to fill in from your sent folder and calendar. A CRM helps once you know which handoff matters, because then you know which dates it has to record.
How many leads do I need before the map means anything?
Enough that a pattern shows. A month of leads is a reasonable start for most agencies. If that is only a handful, go back further until the waits stop jumping around from one lead to the next.
What if the slowest handoff is mine?
That is common when the owner holds scope and price. The fix is to take the parts that don't need your judgment off your desk: capture the call notes in one place and have a first draft of the proposal ready, so your part is setting scope and price.
Should I count leads that were never a match for my services?
Count them, then mark them. A lead you turn down still needs a reply and a close. Without a note of the reason, a lead you declined looks the same in the sheet as one nobody answered.
How is this different from a sales funnel?
A funnel counts how many leads reach each stage. This map adds who owns each move and how long it waits, which is where the fix comes from. You can still draw a funnel from the same sheet by counting the filled cells in each column.
Related
- The four places a lead diesLeads drain out of a pipeline in four places: never recorded, never answered, never followed up and never closed out. How to count each one this week.
- The lead-response bottleneck: how fast to answer a new leadHow fast to answer a new lead, why a slow reply hands the decision to someone else, and a system that drafts from your rules for a person to approve.
- The proposal bottleneck: why proposal turnaround is slowProposals wait for one person's free afternoon. Capture the inputs as the call ends, draft in your template, and keep scope and price with the owner.
- Where do your leads leak?Twelve yes or no checks across the four places a lead dies: never recorded, answered, followed up or closed out. See your worst leak and what closes it.
- A drafted reply to each lead, approved from my phone before it sendsAI drafts replies to lead emails that pass a junk screen, from my business facts. Risky asks get flagged, and nothing sends until I approve it on my phone.
- From signed deal to running projectClient onboarding automation I built. One form with the signed proposal sets up the Drive folder, ClickUp tasks, Slack channel and welcome email.
- Bottlenecks in a service businessWhere work stalls between a new lead and a renewal, found by the symptom you notice, with the system that fixes each one.