Free tool · Instant results
GTM Pipeline Reality Calculator
See how much pipeline, SQL volume, SDR capacity, and outbound activity you actually need to hit your revenue target. The calculator surfaces which GTM lever to fix before hiring more reps.
Runs locally in your browser for private, secure B2B pipeline planning.
Start with a motion preset
Each preset loads benchmark defaults for ACV, win rate, coverage, and SDR productivity.
Pipeline inputs
Set to 100% if you treat SQL and opportunity as the same stage.
3x is the SaaS default. Enterprise often needs 4x+.
5 to 8 is healthy in mid-market B2B SaaS.
Pipeline results
GTM health diagnosis
Interpretation of your plan and the levers most likely to break it.
To hit $5,000,000 with your current ACV and win rate, your outbound team needs 13.9 SDRs. That is usually inefficient unless your ICP is very broad and SDR ramp is proven.
- Raise ACV from $25,000 toward $40,000 through multi-year, bundling, or upsell motion
- Lift SQL to opportunity conversion from 60% to 75% with sharper qualification
- Improve win rate from 20% to 28% via tighter ICP and discovery
- Add inbound, partner, or paid sourced pipeline to reduce outbound load
Channel mix planning
Allocate SQL volume across outbound, inbound, partner, and events for a realistic GTM plan.
Channel split
Outbound activity volume
Translate outbound SQL targets into emails, replies, meetings, and SDR capacity so you can validate whether the plan is executable.
Activity inputs
1 to 3% is healthy for targeted B2B outbound in 2026.
Ramp and hiring plan
Most B2B SaaS SDRs hit full productivity in 3 months.
Scenario comparison
Edit the improved plan to see how lifting ACV, win rate, or SQL to opportunity reduces SDR requirement.
| Metric | Current plan | Improved plan |
|---|---|---|
| Revenue target | $5,000,000 | |
| ACV | $25,000 | |
| Win rate | 20% | |
| SQL to opportunity | 60% | |
| SQLs needed / month | 138.9 | 49.6 |
| SDRs required | 23.1 | 8.3 |
| Pipeline needed | $15,000,000 | $15,000,000 |
Board planning summary
Copy or download a clean text summary you can paste into a board deck or planning doc.
Pipeline Planning Summary ========================= Revenue target: $5,000,000 ACV: $25,000 Win rate: 20% SQL to opportunity: 60% Coverage ratio: 3x To hit target, the team needs: Qualified pipeline: $15,000,000 Closed-won deals: 200 Opportunities: 1,000 SQLs per year: 1,667 SQLs per month: 138.9 Outbound SQLs / month: 83.3 SDRs required (outbound):13.9 Outbound activity (team-wide, per month): Emails: 26,455 Positive replies: 397 Meetings booked: 198 Meetings held: 139 Hiring plan: Current SDRs: 0 Productive SDRs needed: 13.9 Ramp period: 3 months Recommended new hires: 18 GrowthStack recommended fixes before scaling headcount: • Raise ACV from $25,000 toward $40,000 through multi-year, bundling, or upsell motion • Lift SQL to opportunity conversion from 60% to 75% with sharper qualification • Improve win rate from 20% to 28% via tighter ICP and discovery • Add inbound, partner, or paid sourced pipeline to reduce outbound load Generated at growthstackadvisory.com/tools/pipeline-calculator
When to use this calculator
Use it during annual planning to size the SDR team, before a board meeting to pressure-test the pipeline number, or whenever a leader says "we just need more leads."
The output makes the conversation concrete: this is how many SQLs at this conversion, requiring this many reps, supported by this much outbound activity.
If the SDR count looks impossible, the answer is usually ACV, win rate, or ICP targeting before adding headcount.
Common scenarios
Series A SaaS, $1M target
$1M target at $15k ACV and 20% win rate needs ~334 SQLs/year, or ~28/month.
At 6 SQLs/rep that is ~5 SDRs for your sales development team which is usually too many for a Series A.
Levers: raise ACV through multi-year or bundling, tighten ICP to lift win rate, or shift toward product-led signals.
Mid-market, $5M target
$5M at $25k ACV and 20% win rate ≈ 1,000 SQLs/year, ~84/month, ~14 SDRs.
Most teams this size run 8 to 10 SDRs and make up the gap with marketing-sourced pipeline and partner referrals.
Frequently asked questions
How does the GTM pipeline calculator work?
It starts from your annual new-revenue target, divides by ACV to get deals needed, then works backwards through win rate and SQL to opportunity conversion to derive the SQL volume your team must generate.
Pipeline dollars use your coverage ratio. SDR count is monthly SQLs divided by SQLs per rep per month.
The diagnosis layer interprets the result and tells you which GTM lever to fix first.
What is a good pipeline coverage ratio?
3x is the standard SaaS benchmark used in B2B pipeline planning.
Faster SMB motions can run at 2.5x. Enterprise cycles often need 4x or higher.
How many SQLs should an SDR generate per month?
5 to 8 SQLs per rep per month is healthy in mid-market B2B SaaS in 2026.
Sub-3 means targeting, messaging, or ramp is broken.
Above 10 usually means SQL definition is too loose, so check downstream SQL to opportunity conversion before celebrating.
What win rate should I plug in?
Use your trailing 12-month SQL-to-close rate instead of stage-to-stage rates.
Early-stage teams without baseline data can start with a 15 to 25 percent band for outbound-sourced opportunities.
Why does the calculator include channel mix and activity volume?
Most pipeline plans fail because teams calculate the target but skip the GTM system required to achieve it.
Channel mix shows how much of pipeline must come from outbound versus inbound, partner, and events.
Activity volume connects SQL goals to emails, replies, meetings, and SDR capacity so you can see whether the plan is executable.
Is the calculator really free and instant?
Yes, fully free and instant. All math runs locally in your browser for private GTM planning.
Bookmark the page and re-run scenarios anytime.
Related reading
How to build an outbound SDR engine puts these numbers in the context of a full GTM motion. Scaling SDR teams from 10 to 23 reps covers the hiring and management layer when the calculator says you need more SDRs. Cold email reply rate benchmarks help you size the activity needed per SQL.
Your pipeline math shows the target. We help make it achievable.
If your SDR requirement looks too high, the fix is usually sharper ICP, cleaner qualification, and a tested outbound motion rather than more hiring. Book a 30-minute GTM math review and we will pressure-test the plan together.
Book a strategy call