What You'll Have When You're Done
You'll walk away with a one-page document that shows exactly where revenue is leaking, which stage is your bottleneck, how much hidden capacity exists in your current team, and the three highest-ROI fixes you can execute in the next 30 days. You'll know whether your pipeline problem is volume, velocity, or architecture — and you'll have the data to prove it to your board, your team, or yourself.
This is not for founders still doing discovery calls themselves. It's not for teams under five reps. And it's not for operators who think "we just need more leads" without knowing what happens to the leads they already have. If you don't have 90 days of pipeline data in a CRM, stop here. Fix that first. This audit assumes you have a process worth auditing — even if it's broken.
Step 1: Map Your Current Pipeline Architecture
Start by drawing your pipeline as it actually exists today. Not the slide deck version. Not what you told your VP of Sales it should be. The one your reps are actually running.
What to do specifically: Open a blank doc. List every stage from lead capture to closed-won. For each stage, write down what action moves a deal forward, who owns that action, and what the exit criteria is. If you have multiple pipeline types (inbound vs. outbound, SMB vs. enterprise), map each separately.
Why it matters: Most operators think they have a 5-stage pipeline. Then they map it and realize they have 11 stages with three handoffs and two stages that exist only because someone built a Salesforce report in 2019. The gap between your documented process and your actual process is where revenue dies.
Success looks like: A visual map where every stage has a clear owner, a defined action, and measurable exit criteria. If you can't explain what moves a deal from Stage 3 to Stage 4 in one sentence, you don't have a stage — you have a label.
Common failure mode: Operators map the process they wish they had instead of the one they have. Avoid this by pulling five random closed deals from last month and tracing their actual path through your CRM. If the path doesn't match your map, your map is wrong.
Export 90 Days of Pipeline Data
Pull a full pipeline report covering the last 90 days. You need: deal ID, create date, stage history with timestamps, close date, deal value, rep name, and lead source. Export to CSV. If your CRM doesn't track stage history with timestamps, you're flying blind — fix that before you continue.
Ninety days gives you enough volume to spot patterns without getting lost in seasonality. Less than 60 days and you're guessing. More than 120 and you're analyzing a process that may no longer exist.
Identify Every Handoff Point
A handoff is anywhere a deal changes owners: SDR to AE, AE to solutions engineer, AE to closer, sales to customer success. Handoffs are where deals die. Mark every handoff on your map. Measure how many deals enter the handoff and how many exit it within 48 hours.
Across 101 teams I've built, handoff conversion averages 62%. That means 38% of your pipeline is evaporating at transitions you probably don't even measure. If your handoff conversion is below 70%, you have a process problem. If it's below 50%, you have a leadership problem.
Step 2: Measure Conversion Rates by Stage
Now that you have your map and your data, calculate how many deals move from each stage to the next. This tells you where your pipeline is breaking.
What to do specifically: For each stage, divide the number of deals that progressed to the next stage by the number that entered. Do this for every stage. Record the percentages. Then calculate your overall pipeline conversion rate: deals created to deals closed.
Why it matters: Most operators obsess over close rate. But if you're losing 60% of your pipeline between discovery and demo, your close rate is irrelevant. You're trying to fix the wrong problem. Conversion by stage tells you where reps are guessing instead of executing.
Success looks like: A spreadsheet or table showing stage-by-stage conversion with a clear outlier — one stage where conversion drops 20+ points compared to the stages before and after it. That's your bottleneck.
Common failure mode: Operators calculate conversion using deals currently in the pipeline instead of closed deals. This inflates your numbers because you're counting deals that will eventually die. Only measure conversion on deals that have reached a terminal state: closed-won or closed-lost.
Calculate Stage-to-Stage Conversion
Use this formula: (Deals that moved to next stage) / (Total deals that entered this stage) = Stage conversion rate. Do this for every stage. Ignore deals still in progress — they skew the data.
Healthy benchmarks vary by sales motion, but here's what I see across mid-market B2B teams: Lead to qualified: 25-40%. Qualified to demo: 60-75%. Demo to proposal: 50-65%. Proposal to close: 30-45%. If any stage is 15+ points below these ranges, that's your leak.
Flag Outlier Stages
Look for stages where conversion drops sharply. A 20+ point drop between adjacent stages signals a process breakdown. Common culprits: discovery calls with no qualification framework, demos with no clear next step, proposals sent without verbal agreement, and handoffs with no SLA.
A 7-figure SaaS founder in Austin ran this audit and found 71% of deals were dying between demo and proposal. Reps were running demos without confirming budget or decision process. We added a 3-question qualification gate before the demo. Conversion jumped to 58% in 45 days. Pipeline velocity increased 22% because reps stopped wasting time on deals that were never going to close.
Your revenue ceiling is determined by your lowest-converting stage. You can't scale a system that's hemorrhaging deals at Stage 3. Run the SalesFit assessment →
Step 3: Audit Time-in-Stage and Velocity
Conversion rate tells you where deals die. Time-in-stage tells you where they stall. Both matter. A stage with 80% conversion but 45-day median time is still a bottleneck.
What to do specifically: For each stage, calculate the median number of days deals spend there. Then calculate the variance: the difference between your fastest rep and your slowest rep for the same stage. High variance means you have a process problem, not a people problem.
Why it matters: Pipeline velocity drives revenue more than volume once you're past the startup phase. If your average deal takes 90 days to close but your top rep closes in 60, you don't need more leads — you need to figure out what the top rep is doing differently and make it repeatable.
Success looks like: A table showing median time-in-stage for each pipeline stage and variance across reps. Variance below 25% means you have a repeatable process. Variance above 40% means reps are freelancing.
Common failure mode: Using average instead of median. Averages get skewed by outliers — the deal that sat in Stage 2 for six months because the champion left. Median gives you the true center of your distribution.
Measure Median Time Per Stage
Pull your stage history data. For each deal, calculate how many days it spent in each stage. Then find the median across all deals. This is your baseline. Compare it to your target cycle time. If median time-in-stage is 2x your target, your process is broken or your target is fantasy.
Industry research shows that deals stalled beyond 1.5x the median time-in-stage have a 73% chance of ending in no-decision. If your median discovery-to-demo is 12 days, any deal still in discovery after 18 days is likely dead. Your reps just don't know it yet.
Calculate Variance Across Reps
For each stage, compare the median time-in-stage for your fastest rep vs. your slowest rep. If Rep A moves deals from demo to proposal in 8 days and Rep B takes 31 days, you have a 288% variance. That's not a talent gap — it's a process gap.
High variance means reps are interpreting the process differently. One rep is following up same-day. Another is waiting for the prospect to reply. One is sending a proposal during the demo. Another is scheduling a separate call. You can't scale variance. You can only scale repeatability.
| Stage | Median Time (Days) | Rep Variance | Conversion Rate | Diagnosis |
|---|---|---|---|---|
| Lead to Qualified | 3 | 18% | 34% | Healthy velocity, low conversion — tighten qualification criteria |
| Qualified to Demo | 9 | 52% | 68% | High variance — reps lack follow-up cadence |
| Demo to Proposal | 14 | 41% | 51% | Stalled deals — no clear next step after demo |
| Proposal to Close | 22 | 67% | 38% | Long cycle + high variance = no deal advancement framework |
Step 4: Map Rep Capacity Against Pipeline Demand
You've mapped the pipeline. You've measured conversion and velocity. Now figure out if you have enough reps to handle the volume you're generating — or if you're drowning your team.
What to do specifically: Calculate how many deals each rep can handle per stage based on time-in-stage and activity requirements. Then compare that to how many deals are actually entering the pipeline. If demand exceeds capacity by more than 15%, deals are getting ignored. If capacity exceeds demand by more than 30%, you're overstaffed or undermarketing.
Why it matters: I've seen teams hire three reps to solve a pipeline problem that was actually a capacity problem. They had enough reps. They just had reps stuck in Stage 3 because no one was managing deal flow. More headcount made it worse — more deals, same bottleneck, lower conversion across the board.
Success looks like: A simple calculation: deals entering pipeline per month divided by deals each rep can handle per month. If the number is above 1.15, you're overloaded. Below 0.70, you're underutilized. Between 0.85 and 1.10 is the sweet spot.
Common failure mode: Assuming every rep has the same capacity. Your top rep can handle 40 deals a month. Your newest rep can handle 18. If you're routing leads evenly, you're crushing one and starving the other. Capacity planning must account for skill distribution.
Step 5: Compare Documented Process to Actual Behavior
This is where most audits get real. You think your reps are following the process. Then you pull the data and realize they're not even close.
What to do specifically: Take your documented sales process — the one in your onboarding deck or your Notion wiki. Compare it to what's actually happening in your CRM. Look at: activities logged per stage, time between activities, which stages get skipped, and which stages have deals sitting with no activity for 7+ days.
Why it matters: The gap between your documented process and actual rep behavior is your real sales playbook. If your process says "send proposal within 24 hours of demo" but your CRM shows 68% of proposals go out 5+ days later, your process is fiction. You're managing a system that doesn't exist.
Success looks like: A side-by-side comparison showing where reps deviate from the documented process and how often. If deviation is above 30% for any step, that step is either unclear, unrealistic, or unsupported by your tools.
Common failure mode: Blaming reps for not following the process instead of asking why the process isn't followable. If half your team is skipping a step, the step is broken — not the team.
Step 6: Identify the Three Highest-Impact Fixes
You now have a full picture of where your revenue architecture is breaking. Don't try to fix everything. Fix the three things that will move the needle most in the next 30 days.
What to do specifically: Rank every issue you found by potential revenue impact and ease of implementation. Potential impact = (deals affected per month) × (conversion lift if fixed) × (average deal size). Ease = can you fix it without hiring, without custom dev, and without retraining the entire team. Pick the top three.
Why it matters: Most operators find 11 problems and try to fix all of them. They burn 90 days, confuse the team, and move nothing. The teams that scale pick three, fix them completely, measure the result, then move to the next three. Depth beats breadth when you're fixing architecture.
Success looks like: Three specific fixes with clear owners, measurable outcomes, and 30-day deadlines. Example: "Reduce demo-to-proposal time from 14 days to 7 by implementing same-day proposal sends. Owner: Sales Ops. Target: 80% compliance by Nov 15. Expected lift: 12% conversion improvement."
Common failure mode: Picking fixes that sound impressive instead of fixes that move revenue. Rebuilding your CRM dashboard is not a fix. Reducing time-in-stage by 40% is a fix. Stay focused on conversion, velocity, and capacity — everything else is distraction.
The Complete Checklist
Here's the full audit in checklist form. Print it. Run it. Do it in one afternoon.
- Export 90 days of pipeline data with stage history and timestamps.
- Map your actual pipeline: every stage, every handoff, every owner.
- Calculate stage-to-stage conversion rates using closed deals only.
- Flag stages where conversion drops 20+ points.
- Measure median time-in-stage for every stage.
- Calculate rep variance for time-in-stage (fastest vs. slowest).
- Identify stages with variance above 40% — you have a process problem.
- Map rep capacity: deals each rep can handle vs. deals entering pipeline.
- Compare documented process to actual CRM activity.
- Highlight deviations above 30% — those steps are broken or unclear.
- Rank all issues by revenue impact and ease of fix.
- Pick the top three fixes with clear owners and 30-day deadlines.
- Document everything in a one-page summary: bottleneck stage, hidden capacity, top three fixes.
- Share it with your team. Make it visual. Make it real.
If you want to see whether your team has the behavioral wiring to execute the fixes you just identified, that's a different audit. SalesFit measures 80+ data points across how reps think, decide, and operate under pressure. Revenue architecture is only half the equation. The other half is whether your people can actually run the system you're building.
