How to set capacity plans that match Series B headcount budgets in 2027

The outcome you should expect

A finished Series B capacity plan is not a hiring wish list. It is a single reconciled number that four different people — CRO, CFO, VP Sales, and the RevOps lead who owns the model — will all defend in the same board meeting without contradicting each other. When it works, you walk out of the plan-approval session with an agreed net-new ARR commit, an agreed fully-ramped seat count, an agreed hiring calendar with start dates by month, and an agreed cost envelope that maps line-for-line to the headcount budgets the board signed off on at close.

Concretely, here is the shape of the output for a company that raised a Series B and committed to roughly $8M of net-new ARR in year one. At mid-market productivity of about $400K net-new ARR per fully-ramped AE per year — the Bridge Group median territory of an $800K quota carried at roughly 50% attainment — you need about 20 fully-ramped AE-years of selling capacity. But fully-ramped AE-years are not the same thing as hired humans. With a median ramp around four months and annual AE attrition in the high teens to low twenties, you have to run roughly 26–30 hires across the year to keep 20 productive seats in the field at any given moment. Price those at a fully loaded $330–360K each — OTE near $200K at mid-market, times a benefits load, plus $12–18K of per-seat tooling, plus front-line management overhead at one manager per six to eight reps — and the sales-org envelope lands near $9.5M for $8M of new revenue. That is roughly a 1.2x sales-only burn multiple before a dollar of marketing spend, which is already uncomfortably close to the widely used 1.5x ceiling.

The useful outcome, then, is not "we can hire 28 AEs." It is the discovery of exactly where the plan breaks and which lever you intend to pull. Almost every honest Series B capacity model comes back over budget on the first pass. That is the plan working correctly. The failure mode is a model that comes back comfortably under, which nearly always means someone quietly assumed 80% attainment, instant ramp, or zero attrition.

You should also expect the plan to change the conversation about *what kind* of capacity you're buying. Once the per-seat cost is explicit, quota coverage stops being the only variable. Territory density, segment mix, partner-sourced pipeline, self-serve or product-led motion, and AI-assisted prospecting all become substitutes for headcount rather than nice-to-haves. A plan that surfaces those trade-offs is worth far more than one that simply divides a number by another number.

What drives that outcome

Four equations drive everything, and they have to close simultaneously. Model only the first two and the CFO rejects the plan in week three; model only the last two and the VP Sales is hiring against a target nobody believes.

Equation one — the net-new revenue target. Start from the board-approved plan, not your aspiration. If the raise was underwritten on growing from roughly $8M to $20M of ARR over 24 months, and you expect about $1M of churn, your year-one net-new commit is somewhere in the $7–9M band. Renegotiating the destination after the term sheet closes burns credibility fast. Renegotiate the *shape of the curve* instead — back-weighting new ARR into H2 is a legitimate ask when the hiring calendar and ramp math justify it.

Equation two — productive seat count. Divide net-new ARR by realistic per-AE output. Use segment-specific numbers: roughly $300–350K for mid-market in the $25K–$100K ACV band, $400K as a general SaaS median, and $500–700K for enterprise motions above $100K ACV. The number you divide by must be *net-new ARR per rep*, not booked ACV including renewals and expansion routed through the same rep, which is the single most common inflation error in these models.

Equation three — the fully loaded cost envelope. This is where capacity planning collides with the headcount budgets finance actually enforces. Take segment-median OTE, apply a benefits and payroll-tax load of roughly 1.25–1.35x, add the per-seat stack cost, add management span, add recruiting cost per hire, and add onboarding and enablement. Recruiting alone commonly runs $35–50K all-in per AE when you count agency or in-house recruiter cost, interviewer time, and the productivity hole between requisition open and first ramped month.

Equation four — the efficiency gate. Burn multiple is the number that turns your capacity plan into a financeable plan or a headcount freeze. Series B medians sit in the 1.3–1.5x range with top-quartile companies under 1.0x, and the commonly cited underwriting frame layers on NRR above 110%, Rule of 40 above 50, ARR per employee above $250K, and CAC payback inside 15 months. If your first three equations produce a number above the gate, you have exactly three honest moves: reduce hires, raise quota (only defensible if current attainment is already above 60%), or substitute tooling and non-headcount pipeline sources for seats.

The loop back from the failure branch to the top is the important part of that diagram. Capacity planning is iterative reconciliation, not a one-pass calculation, and the iteration should happen in a model you can rerun in minutes — a planning tool or a genuinely hardened spreadsheet with named assumption cells — rather than a deck that has to be rebuilt by hand every time finance moves a number.

There is a fifth driver that lives outside the four equations: coverage ratios for everyone who is not an AE. SDR-to-AE ratios cluster around 1:2.5 to 1:3. Customer success at Series B typically runs one CSM per $1.5–3M of managed ARR, tightening toward the low end when accounts are complex or implementation-heavy. RevOps itself runs roughly one person per 25 quota-carriers, and skipping it is a false economy — under-instrumented Series B orgs miss forecast by materially larger margins than instrumented ones. Deal desk usually earns its first dedicated head somewhere around $10M ARR if average contract values exceed $50K and discounting decisions are contested. Every one of those roles consumes the same headcount budgets as an AE, and a capacity plan that scopes only quota-carriers will blow the envelope the moment the support functions get hired.

Benchmarks and realistic ranges

The value of external benchmarks at Series B is that they end arguments. Your internal history is thin — maybe six to eight quarters of data, much of it from a founder-led motion that no longer resembles what you're scaling — so the benchmark is often more predictive than your own trailing average.

Quota and OTE. Segment medians for AE on-target earnings run roughly $160K for SMB, $200K for mid-market, $260K for enterprise, and above $300K for strategic or named-account roles. Base-to-variable mix has drifted from a traditional 50/50 toward 55/45 at many Series B companies as finance pushes more compensation into variable. The long-standing rule of thumb that quota should equal about five times OTE still holds reasonably well for mid-market; enterprise tends to run 4–5x because deal cycles are longer and territories are thinner, and high-velocity SMB can support 6–7x. Cross-check whatever number you pick against published compensation benchmarks for your specific ACV band rather than a generic figure — the spread within "mid-market" is wide enough to swing your seat count by several heads.

Attainment. This is the assumption that quietly destroys the most plans. Broad-market survey data has median SaaS AE quota attainment sitting in the low-to-mid 40% range, with segment ranges of roughly 50–60% for mid-market and 40–50% for enterprise. A capacity plan built on 80% attainment overstates productive output by 30–60%, which means it under-hires by roughly a third and then misses plan in Q2 with no recovery path. If you want to model above the benchmark, you need direct historical proof from your own reps at similar quota levels — and even then, apply a haircut for the reps you haven't hired yet.

Ramp. Median time to full productivity for a SaaS AE sits around four months, with a realistic range of three to five depending on ACV, sales cycle length, and product complexity. Enterprise motions with nine-month cycles can't physically ramp in four months no matter how good the onboarding is — the first closed-won simply hasn't had time to happen. During ramp, plan on 30–50% of quota. Structured onboarding programs measurably compress ramp, commonly by 30–40%, and they also lift twelve-month retention substantially. That is one of the few places where spending money reliably buys back capacity.

Attrition. Plan on 18–25% annual AE attrition at a high-growth Series B, and skew high if you're changing comp plans mid-year, re-carving territories, or hiring aggressively into an unproven segment. Voluntary and involuntary both count for capacity purposes — a seat is empty either way. Build a 10–15% hiring buffer on top of your gross-up so that a normal quarter of departures doesn't force an emergency requisition cycle.

Per-seat tooling. A consolidated Series B stack — CRM, sequencing, conversation intelligence, forecasting, and data enrichment — typically runs $12–18K per seat per year. Comp administration adds another $30–50K annually for a 40-something-payee org, which is non-negotiable infrastructure: manual commission calculation at this scale reliably produces mid-single-digit percentage leakage plus a steady stream of trust-destroying disputes. Benchmark your renewals against published SaaS pricing benchmark data; overpaying by 20% on the stack is common and it's the easiest money in the plan to recover.

Cost per hire. Somewhere between $35K and $50K all-in per AE, counting recruiting fees or loaded recruiter cost, interview panel time, and the cost of a seat sitting empty. This line is routinely omitted from capacity models and it's material: 28 hires at $40K is over a million dollars that has to live inside the same headcount budgets as salary.

Two adjacent benchmarks worth pulling in even though they sit just outside the narrow question. First, pipeline coverage — 3x for the current quarter and roughly 2x for the next quarter is the standard working assumption, and it is the constraint that determines whether your capacity plan is even executable. Capacity without pipeline is just payroll. Second, marketing-sourced versus sales-sourced mix, because if your plan assumes 60% marketing-sourced pipeline and the marketing budget was cut in the same board cycle that approved your hires, your effective per-rep productivity assumption is already wrong.

Risks, edge cases, and failure modes

The base/bull/bear trap. Presenting a board with three scenarios and no recommendation reads as "the CRO doesn't know which one is real," and boards resolve that ambiguity by funding the bear case. Bring one defensible plan with the sensitivity analysis in an appendix. Show that you've stress-tested it; don't ask the board to choose for you.

Hiring into a pipeline shortfall. This is the textbook Series B blowup. Capacity plan says hire eight AEs in Q2, Q1 coverage comes in at 1.8x instead of 3x, and the org hires anyway because the plan said so. Now you have more reps splitting the same pipeline, attainment craters, attrition spikes, and you've converted a demand problem into a demand problem *plus* a morale problem *plus* a burn problem. Build an explicit coverage gate into the plan: if trailing coverage drops below a stated threshold, hiring pauses automatically and the next cohort slides a quarter. Getting the board to pre-approve that trigger is far easier than getting them to approve a mid-year pause.

Territory carve-up destroying the productivity assumption. Your $400K-per-AE number was derived from reps working territories of a certain density. Add ten reps to the same total addressable footprint and you have not added ten reps' worth of capacity — you've diluted everyone. Model account availability per rep, not just rep count. If the number of qualified accounts per territory drops below what a rep needs to work a full quarter, additional headcount produces negative marginal return. This is where the capacity plan and the territory plan have to be built as one artifact.

Comp-plan changes mid-year. Nothing spikes attrition faster than re-quota-ing a rep who was on pace. If the reconciliation forces a quota increase, apply it at a natural plan boundary with a transition mechanism, not retroactively mid-quarter. And if you raise quota to make the burn multiple work, understand you've just increased your attrition assumption too — those two variables are coupled, and models that raise one without adjusting the other are lying to themselves.

Ramp assumptions that ignore sales cycle length. A four-month ramp assumption inside a seven-month average sales cycle is arithmetically impossible for net-new logo capacity. Enterprise-motion companies should model ramp as *cycle length plus onboarding*, which often lands at seven to nine months, and should staff accordingly earlier in the year. This single error is why enterprise-motion Series B companies so often hit their hiring plan and miss their revenue plan.

Counting expansion and renewal revenue in AE productivity. If AEs carry a blended number that includes renewals, your net-new capacity is smaller than the model claims. Separate the streams explicitly. The same trap appears in reverse when CS owns expansion — the capacity model needs to know who is credited with what, or you will double-count the same dollar and under-hire.

Non-quota-carrying headcount arriving unbudgeted. Sales engineers, enablement, deal desk, and the RevOps analyst who builds the model all consume the approved headcount budgets. A capacity plan scoped to AEs and SDRs only will discover in month five that finance has been counting those hires against the same envelope all along.

AI-substitution assumptions that outrun reality. AI-assisted prospecting and research tooling genuinely displaces some SDR volume, and hybrid models — a smaller human SDR team plus automated workflows — are now common at Series B. But the honest planning posture is to model the substitution conservatively, hold the human floor you need for complex outbound and for the SDR-to-AE promotion pipeline, and revisit at the 90-day checkpoint with actual meeting-to-opportunity conversion data. Boards increasingly ask for the AI-productivity assumption explicitly; give them a number you can measure rather than a story.

Geographic and remote-comp variance. If your plan assumes a single national OTE median but you're hiring in high-cost metros, your cost per seat is understated. Conversely, distributed hiring can legitimately buy back 10–15% of the compensation envelope — a real lever, and one of the few that improves the burn multiple without touching the revenue plan.

A practical rollout plan

Treat the first 180 days as the plan's implementation, with hard checkpoints where you're allowed to change course.

Days 1–30: lock the model. CRO, CFO, and the RevOps lead build the four-equation reconciliation in a real planning tool or a hardened spreadsheet with named, documented assumption cells. Every input gets a cited source or an explicitly labeled internal actual. The deliverable is one number, one hiring calendar with monthly start dates, and a written list of the triggers that would change either. Get finance to sign the assumption sheet, not just the total — that's what prevents relitigation in month four.

Days 30–60: open requisitions and finalize comp. Requisitions open against the hiring calendar, not all at once. Compensation is finalized in the comp system before the first offer goes out, so the first rep's plan document isn't drafted retroactively. Leveling and territory assignment are decided now, because both change the productivity assumption the whole plan rests on.

Days 60–90: land cohort one and instrument ramp. The first cohort onboards through a structured program with defined 30-, 60-, and 90-day competency milestones and a ramped quota schedule that matches the ramp curve in the model. Instrument ramp progress from day one — activity, first meeting, first opportunity, first close — because ramp velocity is the earliest reliable signal about whether the productivity assumption survives.

Day 90: first reforecast. Check pipeline coverage against the 3x current-quarter standard, check cohort-one ramp against the modeled curve, and check actual attrition against the buffer. Any one of those breaking is grounds for sliding the next cohort. This is the checkpoint the board actually cares about.

Days 90–180: cohorts two and three, with rebalancing. Continue hiring against the calendar, adjusted by the day-90 findings. Commit to quarterly territory rebalancing as a standing practice rather than an emergency intervention — moving accounts toward reps who are converting, and away from ramping or under-performing seats, meaningfully lifts blended attainment compared with an annual carve.

Day 180: mid-year decision. Either accelerate — pull forward H2 hires because coverage and attainment support it — or cut. Making the cut decision at day 180 rather than day 270 is what preserves the runway the Series B was raised to buy.

One structural note on ownership: the capacity plan should have a single named owner in RevOps who maintains the model, and a standing monthly reconciliation meeting with finance. Plans that live in a deck decay within a quarter. Plans that live in a maintained model with a monthly cadence survive contact with reality, because the reconciliation happens continuously instead of erupting at the next board meeting.

Related questions

How do I decide between hiring another AE and buying more tooling?

Compare marginal fully loaded cost per seat against the incremental net-new ARR the seat can realistically source given available territory. If qualified accounts per rep are already thin, tooling that raises conversion or reduces non-selling time returns more than an additional body.

What changes if we're an enterprise motion rather than mid-market?

Per-rep productivity rises to roughly $500–700K, but ramp stretches to cycle length plus onboarding — often seven to nine months — so you must hire earlier and carry the cost longer. Fewer seats, higher cost each, and far more sensitivity to territory quality.

How much hiring buffer should sit on top of the fully-ramped number?

Gross up for ramp first, then add 10–15% for attrition on top. For a 20-fully-ramped-AE requirement that lands near 26–30 hires across the year, depending on ramp length and how aggressive your attrition assumption is.

When should we pause hiring even though the plan says hire?

When trailing pipeline coverage drops below roughly 3x for the current quarter, or when cohort ramp is tracking materially behind the modeled curve. Pre-negotiate that trigger with the board so a pause reads as discipline rather than a miss.

Who should own the capacity model day to day?

A named RevOps owner, with a standing monthly reconciliation with finance. Shared ownership between sales and finance without a single maintainer is how the model goes stale and the two sides arrive at the board meeting with different numbers.

FAQ

What is a realistic AE productivity number to use for 2027 planning?

A defensible range is $300K–$500K of net-new ARR per fully-ramped AE per year, with the low end fitting mid-market teams with short average tenure and the high end assuming mature reps and strong product-market fit. Enterprise motions can support $500–700K. Don't model above $500K for a mid-market team without direct historical proof from your own reps at comparable quota.

How should I account for ramp time in my headcount budget?

Budget three to five months of reduced productivity per new AE, with reps hitting roughly 30–50% of quota during that window. Practically, this means hiring 10–20% more AEs than your fully-ramped math suggests, and timing start dates so that ramp completion lands before the quarter you need the capacity — not during it.

What attrition rate should I plan for?

Plan on 18–25% annually for Series B AE teams, skewing high if you're changing comp plans, re-carving territories, or hiring into an unproven segment. Add a 10–15% hiring buffer on top of the ramp gross-up. Note that raising quota to fix a burn-multiple problem also raises your attrition assumption — the two are coupled.

How do I check whether my capacity plan fits the burn multiple?

Divide net cash burn by net-new ARR over the same period. Series B medians sit around 1.3–1.5x, with top-quartile companies under 1.0x. Model the sales-org envelope separately first — if sales alone consumes 1.2x before marketing, the blended number will breach the gate and the plan needs a lever pulled before it reaches the board.

Should SDR and CS headcount live in the same capacity model?

Yes, with separate ratios. SDR-to-AE clusters around 1:2.5 to 1:3, and CS typically runs one CSM per $1.5–3M of managed ARR, tightening for complex accounts. Both consume the same approved envelope, so excluding them produces a plan that looks fundable and isn't.

What if the board-approved budget doesn't match the math?

Reduce the net-new ARR target proportionally, or find non-headcount pipeline — partners, product-led motion, higher-converting tooling. What you must not do is inflate attainment, shorten ramp, or zero out attrition to force a fit. Those adjustments make the model close on paper and fail in Q2, and the credibility cost is worse than asking for the target to move up front.

Sources

• Bridge Group, SaaS AE Metrics & Compensation research — https://blog.bridgegroupinc.com/
• RepVue, Cloud Sales Index and compensation data — https://www.repvue.com/
• ICONIQ Growth research and reports — https://www.iconiqcapital.com/growth/insights
• Pavilion, B2B SaaS performance benchmarks — https://www.joinpavilion.com/
• High Alpha, SaaS Benchmarks Report — https://www.highalpha.com/saas-benchmarks
• Bessemer Venture Partners, State of the Cloud — https://www.bvp.com/atlas
• OpenView / SaaS benchmarks and pricing research — https://www.saastr.com/
• Xactly, sales compensation research and insights — https://www.xactlycorp.com/resources
• Vendr, SaaS pricing and spend benchmarks — https://www.vendr.com/blog
• SaaS Capital, spending and growth benchmark surveys — https://www.saas-capital.com/research/

Related on PULSE

• [How to design territory carve-up after a 50% headcount expansion in 2027](/knowledge/ra0312)
• [Quota Capacity Planning for Series B SaaS in 2027](/knowledge/ra0230)
• [Attrition Buffer in Sales Capacity Planning in 2027](/knowledge/ra0424)
• [Clawback Policy Architecture for SaaS Comp Plans in 2027](/knowledge/ra0422)
• [How to design rep ramp plans that get AEs to quota in 90 days in 2027](/knowledge/ra0333)