Qualified Demand Loss Analyzer
Find where qualified demand is lost and separate process failures from CRM data-quality problems.
Customise & copy
Add the context you have. The prompt updates as you work.
Provide the ordered stages, definitions, entry and exit rules, and any stage-bypass or re-entry rules.
Provide counts entering and progressing from each stage, including the analysis period and cohort rules.
Provide conversion, aging, time-in-stage, or loss data by source, segment, region, owner, period, or another relevant dimension.
Describe known data issues, process rules, handoff expectations, exclusions, duplicates, missing fields, and definition changes.
Live prompt
4 fieldsAnalyze the lifecycle-stage conversion data below to identify where qualified demand is being lost, distinguish likely process failures from data-quality problems, and prioritize the most actionable findings. Lifecycle-stage definitions and sequence: {{stage_definitions}} Stage-level volume data for the analysis period: {{stage_volume_data}} Segmented conversion, aging, or time-in-stage data: {{segment_data}} Known CRM issues, process rules, handoff expectations, exclusions, and caveats: {{data_quality_and_caveats}} Instructions: - Analyze the full supplied lifecycle path and calculate or report conversion and loss at every available transition. Show denominators and state the time period and stage definitions used. - Account for re-entry, recycling, withdrawals, skipped stages, aging, incompatible cohorts, and mixed lead/opportunity populations when the supplied data indicates they matter. - Separate observed facts, calculated metrics, hypotheses, and assumptions. Do not invent values, benchmarks, causes, sample-size thresholds, financial impact, or unsupported causal claims. - Distinguish process failure, data-quality problem, and mixed or unclear findings using only supplied evidence such as timing, ownership, handoff completion, stage-history consistency, duplicate records, missing fields, stale records, or conflicting definitions. - Report segment differences only where the supplied data supports a valid comparison, and flag insufficient volume or missing data. - Rank findings by business impact and confidence. Return exactly these sections in this order: 1. Executive finding: a concise statement identifying the largest qualified-demand loss points and the most important qualification or data caveat. 2. Lifecycle conversion table: use exactly these columns: Stage transition | Starting volume | Next-stage volume | Conversion rate | Loss rate or volume | Key segment differences | Likely issue type | Evidence | Confidence | Priority. Use N/A where a field cannot be calculated. 3. Finding classification: classify each material finding as Process failure, Data-quality problem, or Mixed or unclear, with a short rationale and supporting evidence. 4. Prioritized interventions: list the three to five most actionable interventions in priority order. For each, state the observed loss point, recommended process or data change, expected decision benefit, and confidence. Do not claim an expected uplift unless the inputs support it. 5. Missing data and validation checks: list the checks required before making high-confidence decisions. 6. Assumptions and limitations: state cohort, period, denominator, stage-definition, data-quality, and causality limitations that affect interpretation. Use concise business language. Keep conclusions traceable to the supplied data or transparent calculations.
Proof before you use it
A real example
Tested on gpt-5.6-luna on 2026-09-09
{
"segment_data": "By source, MQL-to-SQL conversion: partner 78% from 320 MQLs, organic 66% from 610, paid search 49% from 780, paid social 35% from 390. SQL-to-Opportunity conversion: enterprise 45% from 420 SQLs, mid-market 31% from 520, SMB 19% from 320. Median time from SQL to Opportunity: 6 days for partner, 18 days for paid search, and 27 days for paid social. Proposal-to-win is 44% for enterprise and 29% for mid-market; SMB sample is too small to compare.",
"stage_definitions": "B2B SaaS lifecycle: Lead = captured contact; MQL = lead meeting ICP and engagement criteria; SQL = accepted by sales development after qualification; Opportunity = sales-accepted deal with a confirmed use case and next step; Proposal = commercial proposal issued; Closed Won = signed contract. Sequence is Lead > MQL > SQL > Opportunity > Proposal > Closed Won. Leads can be recycled to nurture and later re-enter MQL. Opportunities should not bypass Proposal.",
"stage_volume_data": "Analysis period: Q1 2025, based on records entering each stage during the quarter. Lead 8,400; MQL 2,100; SQL 1,260; Opportunity 420; Proposal 250; Closed Won 95. Of 2,100 MQLs, 1,260 became SQLs; of 1,260 SQLs, 420 became Opportunities; of 420 Opportunities, 250 reached Proposal; of 250 Proposals, 95 Closed Won. 180 MQLs were marked recycled and 140 opportunities had no recorded next step.",
"data_quality_and_caveats": "Sales requires an accepted handoff within two business days, but the CRM does not consistently record handoff acceptance. Duplicate lead records are estimated at 8% in paid campaigns. Opportunity stage history is complete after February 1 but incomplete in January. Some owners use SQL for both accepted and unworked leads. Exclude test accounts and internal opportunities; 12 records have conflicting close dates."
}A small ritual that works
How to use it
- 01Provide the ordered lifecycle stages, definitions, entry and exit rules, and any bypass or re-entry rules.
- 02Provide stage-level volumes, the analysis period, and cohort rules.
- 03Add segmented conversion, aging, or time-in-stage data where available.
- 04Describe CRM issues, process rules, handoff expectations, exclusions, and other caveats.
Why it works
This prompt gives the analysis a clear operating framework: it defines the lifecycle sequence, identifies the required data sources, and specifies how to distinguish observed facts, calculations, hypotheses, assumptions, process issues, and data-quality concerns. Its instructions to show denominators, time periods, stage definitions, and transition-level losses make the analysis traceable rather than impressionistic. The required sections also create a practical flow from executive summary to detailed conversion analysis, classification, interventions, validation needs, and limitations. Requiring confidence and priority for each finding helps separate measurable loss points from explanations that remain uncertain. The prompt also explicitly addresses re-entry, recycling, skipped stages, aging, incompatible cohorts, and mixed populations, which signals that a simple sequential funnel should not be treated as automatically reliable.
Where it fails
The structure cannot resolve ambiguity that is absent from the supplied data. It asks for causal distinctions and prioritization while limiting conclusions to evidence such as stage history, ownership, handoffs, aging, and record quality; if those fields are incomplete, the analysis must remain qualified. Sequential stage volumes may also represent different cohorts, stage-entry events, or records affected by recycling and re-entry, so the requested conversion rates can be descriptive without representing a single cohort journey. Segment comparisons are similarly dependent on compatible definitions, periods, denominators, and sufficient volume. The prompt identifies these limitations, but it cannot correct them without more granular record-level data and consistent operational definitions.
Customisation tips
Provide an explicit analysis period, cohort rule, unique-record definition, and treatment of re-entry or recycling in the stage definitions. In the volume data, include stage-entry and stage-exit counts, dates, and record identifiers where possible rather than only aggregate totals. Organize segmented data with consistent denominators and clearly label the comparison dimension, such as source, region, owner, or account tier. Use the caveats field to document exclusions, duplicate rules, stage-history coverage, handoff requirements, aging definitions, and any changes made during the period. If the intended audience has a specific decision to make, add that context through the supplied business data so prioritization reflects the decision at hand without requiring unsupported financial or causal claims.
Watch-outs
- Do not treat sequential stage volumes as one unduplicated cohort unless the supplied data establishes that relationship.
- Conversion rates can be distorted by re-entry, recycling, skipped stages, withdrawals, inconsistent stage definitions, or mixed lead and opportunity populations.
- A large loss rate identifies where volume changed, but it does not by itself establish why the change occurred.
- Segment differences require compatible periods, cohorts, denominators, definitions, and enough volume for a meaningful comparison.
Works in
Was this useful?
Submit your variation
If your version helps, it may be published with your name and a link back to you.
Want to make AI useful across your team? Explore Atul's training.