How do you build a bottoms-up forecast for a net-new outbound motion in 2027?

Two ways to build the bottoms-up number

There are two legitimate starting points for a bottoms-up forecast on a net-new outbound motion, and most RevOps teams pick the wrong one by default because it's the first one they think of.

The capacity-first model starts with what a rep can physically produce. You define meaningful daily activity — personalized touches across email, phone, and social — multiply it by your team's actual conversion rates, and let the pipeline number fall out the other end. This is the right model when you're standing up a brand-new outbound motion with no history: you don't know what the market will give you yet, so you forecast from the one thing you control, which is effort. A five-rep pod running 40 touches a day each will produce a specific, defensible number of opportunities per month, and that number is true regardless of what quota says it should be.

The rate-first model starts with a revenue or pipeline target and works backward: if you need $2M in new pipeline this quarter and your average deal size is $40K, you need 50 opportunities. Divide that by your meeting-to-opportunity rate to get required meetings, divide again by reply-to-meeting rate to get required replies, and divide again by contact-to-reply rate to get required touches. This tells you how many reps you need, not how many opportunities your current headcount will generate. It's the right model when leadership has already set a number and your job is to reverse-engineer the required inputs — headcount, list size, or messaging quality — to hit it.

The trap is using rate-first math with capacity-first data, or vice versa. If you don't have your own historical conversion rates yet, rate-first forecasting is really just goal-setting dressed up as a forecast — it tells you what would need to be true, not what is likely. Capacity-first forecasting is the honest version for a genuinely new outbound motion because it only claims what your team can currently prove. Once you have 4-8 weeks of real conversion data, you can run both models side by side: capacity-first tells you what your current team will produce, rate-first tells you what headcount or list quality you'd need to hit a bigger number, and the gap between the two is your actual staffing or enablement conversation with the CRO.

How to decide between the two models

The decision isn't philosophical — it's a data-availability question, and it should take five minutes to answer.

If you're pre-launch on a net-new outbound motion, always start capacity-first with conservative benchmark rates (3-5% contact-to-reply, 40% reply-to-meeting, 30-35% meeting-to-opportunity) rather than whatever number a vendor deck or a SaaStr talk promised. Benchmarks exist to keep you from wildly overestimating in week one, not to replace real data — you swap them out the moment your own numbers exist. If leadership has already committed a pipeline number to the board before any outbound motion has run, that's a rate-first exercise, and your job is to tell them honestly whether the required touch volume is achievable with current headcount — a five-rep team at 200 touches/week each caps out around 8,000 touches a month regardless of what the spreadsheet says is needed. RevOps should never let a rate-first target ship without a capacity-first sanity check sitting next to it in the same deck.

Concrete numbers behind each option

These are the ranges to actually use, not aspirational ones. A well-targeted list with tight ICP fit and personalized messaging produces a 5-8% contact-to-reply rate; a broad, unsegmented list drops to 1-3%, sometimes lower on cold email alone once deliverability issues are factored in. Reply-to-meeting conversion sits at 40-60% when reps qualify replies within a few hours and offer a specific next step instead of a generic "worth a chat?" — that rate collapses toward 20-25% when follow-up lags more than a day. Meeting-to-opportunity rate typically lands between 30-50% for net-new outbound, with more complex products and larger deal sizes trending toward the low end because more meetings surface as "not now" rather than a disqualification.

Capacity per rep matters as much as the rates. Most B2B outbound teams sustain 40-60 personalized touches per day when roughly 80% of the rep's time is protected for outbound activity — below that ratio, touches drop fast because meetings, admin, and internal Slack eat the block. At 40 touches/day and a 5-day week, that's 200 touches/week per rep. Running the chain at 5% contact-to-reply, 50% reply-to-meeting, and 40% meeting-to-opportunity: 200 touches produce 10 replies, 10 replies produce 5 meetings, 5 meetings produce 2 opportunities per rep per week. A five-rep pod produces roughly 10 opportunities weekly, or about 40 monthly — that's the capacity-first forecast, built entirely from observable inputs rather than a top-down goal.

Ramp curves change this math for the first three months of any new hire on the motion. A new outbound rep typically needs 6-8 weeks to reach full activity capacity, so model month one at roughly 50% productivity, month two at 75%, and month three at 100%. A forecast that assumes a new hire hits full capacity on day one will overstate quarter-one pipeline by 30-40% and create a commit-category problem for the CRO when the shortfall shows up in week ten instead of being visible from day one.

Implementation details and sequencing

Sequencing matters more than the math itself, because a bottoms-up forecast built on bad measurement discipline is worse than no forecast at all — it creates false confidence.

Start by naming an owner for the forecast and defining the three rates precisely enough that two people measuring the same week get the same number — a "reply" should mean any inbound response indicating interest, not an out-of-office bounce, and a "meeting" should mean a calendared call that actually holds, not a booked-then-no-showed slot. Run the pilot on a single pod for two full weeks before building anything in a spreadsheet; two weeks is short enough to move fast but long enough to smooth out day-to-day noise in a single rep's activity.

Once you have real numbers, build the capacity-first model first, because it's the one you can defend without caveats — it only claims what the team demonstrably produced. Layer the rate-first model on top only if leadership needs a target-driven number, and always present the two together so the gap between "what we can produce" and "what's being asked for" is visible rather than papered over with optimistic rate assumptions.

Refresh the model every four weeks, not once a quarter. Outbound conversion rates drift with list quality, messaging fatigue, and seasonality — a rate that held in March can be 30% worse in July simply because your TAM segment is smaller and you're further down the list into less-qualified accounts. Build the refresh into the same cadence as pipeline review so nobody has to remember to do it separately. If a rep or the whole pod misses forecast two cycles in a row, don't adjust the model to match reality quietly — surface it, because a persistent miss usually means either the capacity assumption was wrong (reps aren't actually getting 80% protected time) or the rate assumption was wrong (list quality degraded), and those require different fixes.

Finally, keep the forecast tied to your CRM, not a side spreadsheet. Touches, replies, meetings, and opportunities should be logged as activities and stage changes on the same records finance and the CRO already review, so the forecast number and the pipeline number are reading the same underlying data rather than two systems that can silently drift apart.

Related questions

How many outbound touches per rep per day is realistic?

Most B2B outbound teams sustain 40-60 personalized touches daily across email, phone, and social when about 80% of a rep's time is protected for outbound work. Below that time allocation, effective touch volume drops sharply regardless of headcount.

What conversion rate should I use if I have no historical outbound data?

Use conservative benchmarks: 3-5% contact-to-reply, 40% reply-to-meeting, 30-35% meeting-to-opportunity. Replace every benchmark with your own measured rate within the first four weeks of running the motion.

How long should a new outbound rep take to ramp to full capacity?

Plan for 6-8 weeks: roughly 50% productivity in month one, 75% in month two, and 100% by month three. Forecasting full output from day one overstates early-quarter pipeline.

Should I forecast bottoms-up or top-down for a brand-new motion?

Bottoms-up, always, for a motion with no track record — top-down assumes a market response you haven't proven yet. Reserve top-down/rate-first math for reverse-engineering headcount against an already-committed target.

How often should I recalibrate a bottoms-up outbound forecast?

Every four weeks. Conversion rates drift with list quality, messaging fatigue, and seasonality quickly enough that a quarterly refresh leaves the forecast stale for most of the quarter.

FAQ

What's the difference between capacity-first and rate-first forecasting? Capacity-first starts with what your reps can physically produce (touches per day) and multiplies forward through conversion rates to a pipeline number. Rate-first starts with a required pipeline or revenue target and divides backward to find the touches and headcount needed. Use capacity-first when you lack history; use rate-first to check a target against reality.

How many reps do I need to hit a specific pipeline target?

Divide the target by average deal size to get required opportunities, divide by your meeting-to-opportunity rate for required meetings, divide by reply-to-meeting rate for required replies, and divide by contact-to-reply rate for required touches. Divide total touches by sustainable touches per rep to get headcount.

Is a 5% reply rate good for cold outbound? Yes, for a well-targeted, personalized list — the realistic range is 3-8%. Broad or unsegmented lists commonly fall to 1-3%. Treat anything above 8% as a signal to verify the sample size before trusting it.

Why does my forecast keep missing even though rates look accurate? The most common cause is an unmodeled ramp curve on new hires or an activity capacity assumption that ignores non-selling time. Rebuild the capacity input using actual protected selling time, not a theoretical 100% allocation.

Can I build a bottoms-up forecast without any CRM history? Yes — run a two-week pilot on one pod, log every touch, reply, and meeting manually if needed, and use that short window to replace generic benchmarks with your team's real numbers before committing to a quarterly forecast.

How does deal size factor into a bottoms-up outbound forecast? Deal size converts opportunity count into a pipeline dollar figure and is essential for rate-first math (target ÷ deal size = required opportunities), but it doesn't change the capacity-first activity chain — that stays touches → replies → meetings → opportunities regardless of deal size.

Sources

• https://hbr.org/topic/sales
• https://www.salesforce.com/resources/articles/sales-forecasting/
• https://www.gartner.com/en/sales/topics/sales-forecasting
• https://www.saastr.com/
• https://www.forrester.com/blogs/category/sales-operations/
• https://business.linkedin.com/sales-solutions/b2b-sales-resources

Related on PULSE

• How do you build a bottoms-up revenue model in 2027?
• What happens to net-new pipeline when AI agents autonomously skip 40% of early-stage qualification?
• What quota credit policies prevent gaming while rewarding split deals, expansions, and net-new accounts?
• How do you build a warm outbound motion in 2027?
• How do you read CAC payback when half your sales motion is PLG and half is enterprise outbound?