Revenue operations leaders, Sales leaders, Finance partners, RevOps analysts, Operations managers
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 consultant. Your task is to identify where revenue is leaking across the sales and customer journey and produce a practical recovery plan.
### Required Input
- Business Model: [Example: B2B SaaS with annual subscriptions and expansion revenue]
- Revenue Journey Scope: [Example: lead to close, close to renewal, expansion process, or full lifecycle]
- Revenue Targets: [Example: $3M quarterly new ARR target]
- Performance Data: [Provide conversion rates, win rates, discounting, churn, expansion, slippage, no-shows, or handoff data]
- Sales Process Summary: [Briefly describe lead flow, qualification, opportunity stages, proposal, close, onboarding, renewal]
- Known Problem Areas: [Example: high discounting, slow legal review, missed renewals, poor lead follow-up]
- Customer Segments: [Example: SMB, mid-market, enterprise]
- Constraints: [Example: limited headcount, CRM gaps, no dedicated CS operations]
### Input Validation
Review all inputs before analysis. If the user has not defined the journey scope or provided any performance indicators, ask for clarification before continuing. If data is partial, state assumptions and separate proven leakage from suspected leakage.
### Instructions
Treat revenue leakage as preventable revenue loss caused by process gaps, data issues, poor qualification, pricing behaviour, handoff failures, conversion friction, retention risk, or expansion underperformance. Do not only look at closed-lost deals.
Trace the revenue journey from source to realised revenue. For each step, identify where value can disappear: lead response delays, poor routing, low meeting conversion, stage stagnation, weak discovery, proposal delays, excessive discounts, procurement friction, failed handoffs, under-adoption, renewal risk, or missed expansion signals.
Quantify leakage where possible. If exact numbers are unavailable, use directional estimates and explain what data would confirm the scale. Separate leakage by revenue type: new business, expansion, renewal, and margin protection.
Make recommendations operational. Include changes to ownership, process controls, CRM fields, approval rules, inspection cadence, enablement, and handoff quality. Prioritise fixes that recover revenue without requiring major new systems.
### Output
- Executive Summary: top leakage points and estimated commercial urgency
- Revenue Journey Map: stages where revenue is created, delayed, reduced, or lost
- Leakage Findings: each issue with evidence, likely cause, revenue impact, and confidence level
- Leakage Categories: acquisition, qualification, pipeline, pricing, closing, onboarding, renewal, expansion
- Quantification Table: known or estimated loss, required data, and recovery potential
- Root Cause Analysis: process, people, data, customer, and governance factors
- Recovery Opportunities: specific actions to stop or reduce leakage
- Control Measures: dashboards, CRM rules, approvals, SLAs, or review cadences to prevent recurrence
- Prioritised Recovery Roadmap: immediate, 30-day, and 90-day actions
- Success Metrics: how to measure recovered revenue and leakage reduction
Include a conservative, moderate, and ambitious revenue recovery estimate based on the available data.
This audit evaluates the full lifecycle revenue infrastructure of the Cross-Border Customs API Hub product line. The goal is to isolate systemic process leaks, margin erosion, and churn points that threaten our quarterly targets.
The operational lifecycle reveals four distinct points where revenue is delayed, reduced, or lost:
| Journey Phase | Primary Failure Mechanism | Operational Impact |
|---|---|---|
| Acquisition & Routing | Sloppy inbound lead assignments and slow response times. | Reduces top-of-funnel pipeline yield. |
| Pipeline & Technical | Deals stall in mid-funnel stages because reps do not qualify technical requirements early. | Extends the average sales cycle out to 75 days. |
| Pricing & Closing | Reps use manual discounts to push through month-end deals. | Erodes contract values and lowers gross margins. |
| Onboarding & Expansion | Poor data transfer during post-sale handoffs. | Delays implementation and reduces first-year net revenue retention. |
| Identified Leakage Point | Estimated Annual ARR Loss | Required CRM Field Validation | Recovery Potential |
|---|---|---|---|
| Late-Stage Concessions | $240,000 | Enforce manager approval for discounts over 10%. | Recover 50% ($120k ARR) within 60 days. |
| Onboarding Bottlenecks | $280,000 | Make the Target ERP Infrastructure field mandatory before closing. | Accelerate implementation times by 30%. |
| Inbound SLA Breaches | $120,000 | Track the time delta between lead creation and first outbound activity. | Recover $60k ARR in saved opportunities. |
Get access to all workflows, across every sector, with structured systems built for better results.