A lead leak is an avoidable break in the path to an appropriate next step. Repair the process first, then measure whether fewer leads fall through it.
Trace one enquiry from beginning to end
List every way a prospective customer can reach you: website forms, calls, chat, direct messages, events, referrals, and email. Submit clearly labeled test enquiries through the channels you control. Confirm the record arrives, the source survives, and a person is responsible for responding.
Check what happens after hours, on weekends, when an owner is away, and when an integration fails. A successful form submission is not the same as a successful sales handoff. Keep a simple audit log with entry point, timestamp, record created, owner assigned, and next action.
Look for missing ownership and slow response
Build a view for unassigned leads and overdue responses. Set response targets that reflect enquiry intent and your actual coverage. A pricing request and an early-stage resource download do not necessarily need the same treatment. Track human response separately from automated acknowledgements.
Measure the distribution, not only the average. Median response time describes the middle; a high-percentile measure exposes leads that wait much longer. Use a backup owner and an escalation rule so the target has an operational consequence.
Inspect the middle of the funnel
Review no-shows, unanswered proposals, opportunities with no next-step date, and records that have remained in a stage unusually long for your business. Read the context before chasing someone. A buyer who asked to pause needs a different action from a buyer waiting on your answer.
Give every open opportunity a next action, owner, and date. Mark whether the buyer agreed to it. If no active project exists, close or move the record into a clearly defined nurture state with the appropriate contact preference. Inflated pipeline hides the work that matters.
Automate a narrow repair
Start with a specific rule: when a high-intent enquiry arrives, create a record, assign an owner, create a response task, and flag a missed target. Log failures and make retries visible. Prevent duplicate records and stop sequences when a person replies or opts out.
AI can summarize context or suggest a response. Deterministic rules are often better for required fields, routing, and overdue dates. Pilot on a small group of records and inspect both the successful path and failure cases before wider rollout.
Prove the repair and protect the handoff
Re-run your test enquiry and sample recent real records. Compare missing-owner counts, overdue follow-ups, and stage progression before and after the change. Do not treat every untouched lead as a guaranteed lost sale or multiply the entire backlog by average deal value.
For won clients, transfer outcomes, scope, promises, stakeholders, and the first milestone to delivery. Confirm someone accepts ownership. A lead process is not healthy if it closes business that immediately becomes a confusing client experience.
A prompt to make this practical.
Review this anonymized lead-process map. Identify where records, ownership, consent preferences, or next steps can be lost. For each gap, propose one rule, an accountable role, an exception path, and a verification test. Do not estimate lost revenue without explicit assumptions.
Use anonymized information in an approved tool. Verify the result before sending or updating records.
Customize your prompt →Try this today.
Run the lead-leak audit, repair the earliest confirmed gap, and repeat the same test enquiry to verify the fix.
Lead-leak audit ↗