Map a lead-to-conversation funnel
A practical worksheet for source, response, fit, ownership and next step.
In this article
The situation
Draw the path a real inquiry took last week. The goal is to expose a missing decision or owner, not to make a perfect diagram of every possible journey.
Choose a sample that exposes the process
A funnel diagram often starts with ideal stages and hides what happened to actual people. Use a consecutive sample from one entry source, including inquiries that did not progress. Keep customer identities out of the working copy when possible. For each case, record the arrival event, the first useful answer, the fit decision, the owner who accepted it and the next action. Mark a missing timestamp as unknown rather than filling it from memory.
Segment the sample by staffed and unstaffed hours if response coverage differs. A set of only successful opportunities will make the process look more reliable than it is. The aim is to find the earliest repeatable break, not to infer a market-wide conversion rate from ten records.
Turn the map into a decision
Lay the cases in a simple table and read from left to right. If seven inquiries were captured but four never received an owner, fix the assignment rule before changing the page that attracts inquiries. If ownership is strong but the first answer repeatedly misses the question, repair the response template and context available to staff. Record the reason for each break so the team can distinguish a system failure from a one-off exception.
For the next two weeks, choose one operational change and state what would count as improvement. Keep the sample definition and measurement window stable. A smaller, clearer flow with documented outcomes is more useful than a visually complex diagram that nobody uses in weekly review.
What the worksheet should contain
A usable worksheet has one row per inquiry and columns for source, arrival time, question type, first useful answer, fit status, owner, due date, accepted next step and reason a case stopped. It should also show an explicit unknown state. Do not store full message transcripts merely to calculate stage completion; a short coded reason is usually enough for the process review.
Revisit the map when a channel, staffing model or qualification rule changes. Do not attribute every later sale to the first source; the map's immediate purpose is to make responsibility and next actions visible.
Work through it
- Select ten recent inquiries from one source. Record arrival, first useful answer, fit decision, handoff and agreed next step. Mark unknowns explicitly.
- Put the events in order for each inquiry and identify the first missing or delayed stage. Do not jump to the most visible later failure.
- Choose one rule to test for two weeks, such as a backup owner or a clearer first answer. Keep the same sample definition when reviewing change.
What to measure
- Cases with all stage timestamps
- First missing stage per case
- Cases with an accepted next step
Boundaries
- Small samples expose workflow problems but are not market benchmarks.
- Never upload actual customer names or messages to this site's audit.
Questions for your own workflow
- Which source will you sample?
- Where is the earliest uncertainty?
- What single change will you test?