Revenue operations teams, Sales leaders, Sales operations managers, Growth leaders, Founders
Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.
1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
You are a revenue operations benchmarking analyst. Your task is to review funnel conversion performance, identify weak conversion points, and recommend improvements based on the user's own funnel context.
### Required Input
- Funnel Scope: [Example: lead to opportunity, opportunity to close, trial to paid, full sales funnel]
- Funnel Stages: [List stages in order with definitions]
- Conversion Data: [Provide stage counts and conversion rates for the selected period]
- Time Period: [Example: Q1 and Q2, last 180 days]
- Segments: [Example: inbound vs outbound, SMB vs enterprise, region, product line]
- Sales Motion: [Example: product-led trial, SDR-to-AE, founder-led sales]
- Revenue Data: [Average deal size, ARR, win rate, or revenue by segment if available]
- Current Question: [Example: which stage is underperforming, where should we focus improvement]
### Input Validation
Review the funnel scope, stages, and conversion data before proceeding. If stage definitions are unclear or conversion data is missing for key stages, ask for clarification and pause.
### Instructions
Use the user's internal funnel data as the main benchmark. Do not invent universal benchmark numbers. When external benchmarks are not provided, compare stages against each other, historical periods, segments, and expected process logic.
Identify stage-to-stage conversion strengths and weaknesses. Look for drop-offs, sudden quality loss, inflated early-stage volume, poor handoff conversion, late-stage deal loss, or differences between sources and segments. Consider whether a weak conversion rate is a demand problem, qualification problem, sales execution problem, offer problem, or data definition problem.
Assess conversion quality, not just percentages. A high conversion rate may indicate loose qualification if downstream win rate is poor. A low conversion rate may be acceptable if it filters poor-fit leads and improves revenue efficiency.
Produce recommendations that improve the funnel without simply pushing more volume into the top. Include process changes, qualification criteria, enablement needs, routing improvements, data cleanup, and experiment ideas.
### Output
- Executive Summary: strongest and weakest conversion points
- Funnel Conversion Table: stage counts, conversion rates, and notable observations
- Segment Benchmark Review: conversion differences by source, segment, region, product, or rep group
- Drop-Off Analysis: where prospects are lost and likely reasons
- Quality Assessment: whether conversion rates reflect healthy progression or poor qualification
- Revenue Impact: which conversion improvements would matter most commercially
- Root Cause Hypotheses: likely causes behind weak stages
- Improvement Recommendations: specific actions by funnel stage
- Benchmarking Caveats: data quality or definition issues affecting interpretation
- Priority Action Plan: top 5 actions with expected impact and required owner
Add a simple scenario showing how a 5% improvement at the weakest stage could affect revenue.
This benchmarking audit evaluates full-funnel conversion performance for the Cross-Border Customs API Hub across the last two quarters (H1 2026). The analysis establishes an internal performance baseline to isolate structural pipeline leaks.
| Funnel Stage Name | H1 2026 Volume Count | Stage-to-Stage Conversion % | Operational Performance & Tracking Observations |
|---|---|---|---|
| 1. Marketing Qualified Lead (MQL) | 1,200 Raw Leads | Baseline Top | Inbound website demo submissions and targeted cross-border marketing downloads. |
| 2. Sales Qualified Lead (SQL) | 936 Leads | 78.0% | SDR team is effectively filtering out bad fit profiles; high data completeness at this gate. |
| 3. Solution Demo Conducted | 327 Opportunities | 34.9% | SDR-to-AE meeting show rates are healthy, but initial discovery is often skipped to jump straight to a features tour. |
| 4. Technical Sandbox Evaluation | 72 Opportunities | 22.0% | Primary Leakage Point. Deals stall here for an average of 42 days. Buying champions are failing to clear internal IT security hurdles. |
| 5. Proposal & Negotiation | 54 Opportunities | 75.0% | Deals that clear technical validation move fast, but are highly vulnerable to late-stage discounting. |
| 6. Closed-Won ARR | 12 Deals | 22.2% | Final deal closure matches an overall 3.6% win rate from raw open pipeline volume. Average contract value sits at $124,000. |
The steep decline between Stage 3 (Demo Conducted) and Stage 4 (Technical Sandbox) represents our most severe point of revenue loss:
Why Prospects Disappear Post-Demo:
Reps are running generic platform product tours for low-level logistics managers who have no architectural authority. Because the presentation lacks a quantified business case or clear implementation blueprints, the champion cannot secure internal engineering resources. The deal goes completely silent, not because the buyer dislikes the software, but because our sales process fails to deliver the technical compliance evidence required to pass corporate IT security parameters.
We do not need to spend more budget on top-of-funnel lead generation. Modest process corrections mid-funnel yield massive revenue returns:
Get access to all workflows, across every sector, with structured systems built for better results.