Hiring feels like progress; capacity math shows whether it is
When pipeline looks busy and quota attainment slips, the default instinct in many B2B SaaS teams is to open another account executive seat. Sometimes that is correct. Often it papers over a funnel problem: thin qualified pipeline, uneven territory design, a broken handoff from marketing or SDRs, or a product that still needs three demos to prove value. A lightweight sales capacity model will not replace a full RevOps stack, but it will stop you from hiring hope.
This playbook fits founders and sales leaders at roughly ten to one hundred person companies with a handful of AEs. You need a spreadsheet, honest ramp assumptions, and the discipline to treat capacity as inventory of selling hours—not as a vibe. The goal is a clear answer to one question: if we add one productive AE in N months, what incremental bookings should we expect after cost, and what upstream inputs must already exist?
Start with definitions everyone shares. An AE’s “capacity” is the bookings they can reasonably close in a period given ramp stage, segment, average deal size, and win rates you actually observe—not the aspirational quota on the offer letter. Quota is a management target. Capacity is a forecast input. Confusing them is how you staff for a plan the funnel cannot feed.
Model ramp, not just steady-state quota
New AEs rarely produce full quota in month one. Build a simple ramp curve: for example 0% in month one while onboarding, 25% in month two, 50% in month three, 75% in month four, then 100%. Adjust for your sales cycle length. If your median cycle is ninety days, a hire who starts today mostly closes pipeline that is already being created now—or that they will generate only after they learn the pitch. Ignoring lag creates a fantasy hockey stick.
Compute productive AE-months over the next two quarters. One fully ramped AE equals 1.0. A mid-ramp hire might average 0.4 across the next quarter. Multiplying headcount by annual quota without this curve overstates near-term revenue and understates the cash burn of salary, benefits, tools, and enablement.
- Segment the model: SMB velocity AEs and enterprise AEs should not share one average deal size.
- Use trailing win rates by segment, not the best month’s anecdote.
- Include manager load: a player-coach with three directs has less personal capacity than a pure IC.
- Count attrition risk: if you lose one AE while hiring one, net capacity may be flat.
Pipeline coverage and SDR ratios are the real gates
Capacity without pipeline is idle cost. A common rule of thumb is three to four times coverage of the period’s quota in qualified pipeline, but your number should come from historical conversion: if you need four dollars of pipeline to close one dollar of bookings, hire toward that ratio. Before approving an AE req, show the pipeline that will exist when they are productive—not the pipeline you hope marketing will magically create next month.
Map SDR or BDR support. If each AE needs roughly one sourced opportunity per week to stay full, and each SDR produces a known weekly volume after ramp, you can see whether you are short on hunters upstream. Hiring AEs into a desert of meetings just redistributes scarcity and invites discounting. Sometimes the next dollar of capacity belongs in SDR, solutions consulting, or product-led activation—not another closer.
Also stress-test territory and account assignment. Two AEs fighting over the same named accounts is not double capacity. Neither is assigning a new hire a book of accounts that the best AE already works. Capacity models fail quietly when the org chart and the CRM ownership disagree.
A one-page decision checklist before the offer
Write five numbers on one page: expected ramped bookings from the new seat in the next two quarters, fully loaded cost of that seat for the same window, required incremental qualified pipeline, current coverage ratio after existing AEs take their share, and the enabling hire or spend (SDR, SE, data) required to keep coverage healthy. If the incremental bookings do not clear a threshold you set for payback—or if coverage collapses below your historical close threshold—pause the AE hire.
- Process first: if top AEs crush quota while new hires fail, fix enablement and ICP before adding seats.
- Product first: if demos convert but expansions stall, capacity may belong in CS or PLG, not AE count.
- Hire when: coverage is healthy, ramp plan is funded, and the model shows payback you believe.
- Revisit quarterly: refresh win rates, cycle time, and SDR output; do not fossilize last year’s assumptions.
Keep the model light enough that leaders use it
A capacity model that takes a week to update will not be used in hiring debates. Aim for a sheet you can refresh in under an hour after CRM exports: AE list with ramp stage, segment quotas, trailing win rate, open pipeline by owner, and SDR throughput. Review it in the same meeting where you approve headcount. Make disagreement about inputs visible—cycle time, win rate, ramp—so the argument is about evidence instead of optimism.
Sales hiring is a compounding decision. Each AE multiplies enablement load, forecasting noise, and pipeline demand. Used well, a lightweight capacity model protects growth by matching closers to feedstock. Used poorly, headcount becomes a substitute for strategy. Build the boring spreadsheet first, then open the req only when the math and the funnel agree.