The ramp-economics parable.
These are field notes from Pete Kazanjy's Founder-Led Sales course — a distillation of the parable he uses to explain why ramp speed, not headcount, is the real lever in scaling a sales team. The thesis: onboarding and ramp speed is not a line item on the plan, buried somewhere under recruiting and enablement. It is the hidden exponent on the entire scaling curve. Every other decision a founder makes about hiring pace, quota design, and management structure sits downstream of how fast a new rep gets from zero to fully productive — and a team that ramps reps twice as slowly does not lose half its output. Compounded over a few years, it loses most of it.
TL;DR
- A single rep's monthly sales contribution margin climbs through the ramp from roughly $15K toward roughly $45K, settling around $50K/mo once fully ramped, in Kazanjy's worked numbers.
- Four ramped reps produce roughly $60K/mo climbing to roughly $180K/mo — the unit economics of one rep, cloned.
- Add a new cohort of reps every ~4 months. Nine cohorts onboarded successfully over 36 months compounds to roughly $1.6M/mo in contribution margin.
- In the worked example — $15K ACV, 20% win rate, 3-month ramp, 10 new opportunities per rep per week, 90% renewal — nine classes of 3 AEs every 3 months (1:2 SDR:AE ratio) produces 27 ramped AEs and 12 SDRs at month 24, doing $4.5M in monthly bookings, or $54M in forward ARR.
- The punchline: double the ramp time from 4 to 8 months, and two cohorts now take 16 months instead of 8. Over a comparable horizon the slow-ramp org lands near $810K/mo in contribution margin (~$9.7M annualized) against ~$1.62M/mo (~$19M annualized) for the fast-ramp org — roughly half the outcome for a 2x slower ramp.
- This is why onboarding is the single highest-leverage investment in scaling a sales org: it is the multiplier sitting in front of every other lever.
The premise
Founders planning a sales team's growth default to headcount math: hire N reps, each rep eventually produces X, so the org produces N times X. The plan is directionally correct and structurally incomplete, because it treats ramp time as a rounding error — a few months of reduced output at the start of a rep's tenure, absorbed somewhere in the model and then forgotten. Kazanjy's framing inverts the emphasis: ramp time is not the rounding error, it is the exponent. It determines how many cohorts of reps you can bring online inside a fixed window, and the number of cohorts you can run is what actually produces the compounding curve the rest of the plan depends on.
The reason ramp time behaves like an exponent rather than a constant is straightforward once stated: a slower ramp does not just delay one cohort's output. It delays the point at which that cohort is fully productive and generating the cash, the pipeline data, and the manager bandwidth needed to bring the next cohort online. Slow ramps don't cost you a quarter. They cost you the cohort after that, and the one after that.
The single-rep ramp curve
Start with one rep, because the unit economics of the whole org are the unit economics of one rep, replicated. In Kazanjy's numbers, a single rep's monthly sales contribution margin does not arrive at full value on day one. It climbs — from roughly $15K/mo early in the ramp toward roughly $45K/mo as the rep approaches full productivity — and settles at an aggregate ramped-rep unit profitability of roughly $50K/mo once the rep is fully up to speed.
That climb is the ramp. It is the period during which the rep is a net cost against the eventual value they will produce, and every week shaved off that climb is a week where the rep is contributing at the $50K/mo run rate instead of somewhere lower on the curve. Clone the unit and the pattern holds at scale: four ramped reps produce roughly $60K/mo climbing to roughly $180K/mo — four times the single-rep curve, because the curve is a property of the rep, not of the org around them.
The single-rep curve is also the reason ramp time is measurable and worth defending as a metric in its own right, independent of quota attainment. A rep who hits quota in month five after a five-month ramp and a rep who hits quota in month five after a three-month ramp followed by two months of over-quota performance look identical on a quota-attainment report. They are not identical on a contribution-margin report, and the difference between them is exactly the gap this chapter is about.
Cloning the unit — the cohort math
Once the single-rep curve is established, the scaling plan is a cohort-cloning exercise: bring on a new group of reps on a fixed cadence, let each cohort climb its own ramp curve, and stack the cohorts. In Kazanjy's model, a healthy cadence adds a new cohort of reps roughly every 4 months. Nine cohorts, successfully onboarded on that cadence, spans 36 months — and the aggregate contribution margin at the end of that window compounds to roughly $1.6M/mo.
The word doing the work in that sentence is successfully. The cohort math assumes every cohort ramps on the modeled timeline. It does not assume anything about hiring being easy, or about the pipeline being sufficient to feed every ramping rep, or about the manager having bandwidth to run nine consecutive onboarding classes without the tenth cohort's onboarding suffering because the ninth cohort is still consuming disproportionate coaching time. Those are the real operational risks sitting underneath the cohort math, and the rest of this cluster — onboarding curriculum design, the revenue-production-unit model, first-line management — is the operational answer to each of them. This chapter is only the parable that motivates why the answer matters.
The worked example
Kazanjy walks the cohort math through a fully specified example, and the specificity is the point — it turns an abstract exponent into a plan a founder can actually build a hiring calendar against. The vitals: $15K ACV, 20% win rate, a 3-month ramp, 10 new opportunities generated per rep per week, and a 90% renewal rate. Against those vitals, the org runs nine classes of 3 AEs, one class every 3 months, at a 1:2 SDR-to-AE ratio.
Run that cadence for 24 months and the org lands at 27 ramped AEs and 12 SDRs, producing $4.5M in monthly bookings — $54M in forward ARR. Every number in that outcome traces back to two inputs: the per-rep unit economics ($15K ACV, 20% win rate, 90% renewal) and the ramp cadence (3-month ramp, new class every 3 months). Change the unit economics and the absolute numbers move. Change the ramp cadence and the whole trajectory moves, because the ramp cadence is what determines how many classes fit inside the 24-month window in the first place.
The cost of a slow ramp
This is the parable's actual punchline, and it is worth sitting with because the intuition most founders carry into this math understates it badly. The instinct is that a slower ramp costs you something proportional — ramp takes twice as long, so you lose roughly half of that cohort's early output, and the org is a little behind schedule. That is not what the math shows.
Stretch the ramp from 4 months to 8 months and the effect is not additive, it is multiplicative on the org's cohort-onboarding cadence. Ramping two cohorts now takes 16 months instead of 8, because the cadence at which you can responsibly bring on the next class is itself gated by how long the current class is still consuming ramp-stage coaching and management attention. Run the clock out to 36 months and the fast-ramp org has fit nine cohorts through the window; the slow-ramp org, with the same 36 months to work with, has only fit roughly 4.5 cohorts of 8-month-ramping reps — half the cohorts, because each one took twice as long to clear the ramp gate.
Extend the comparison to 54 months and the gap does not close, it widens in absolute dollar terms because contribution margin compounds on top of contribution margin. The slow-ramp org lands at roughly $810K/mo in contribution margin — about $9.7M annualized. The fast-ramp org, on the same extended timeline, is at roughly $1.62M/mo — about $19M annualized. A 2x slower ramp does not produce a 2x smaller org. It produces, in this worked comparison, an org running at roughly half the contribution margin of the fast-ramp version, years into the buildout, with the gap compounding rather than narrowing as both orgs keep scaling.
Why this makes onboarding the highest-leverage investment
Put the pieces together and the conclusion is unambiguous: if ramp time is the exponent, then the investment that shortens ramp time is the investment with the highest return in the entire scaling plan — higher than the next AE hire, higher than the next SDR hire, higher than most of the tooling and process work founders instinctively reach for first. A curriculum that gets a new rep from zero to full quota in 3 months instead of 5 or 6 is not a nice-to-have onboarding artifact. It is the lever that determines whether the org compounds to nine cohorts or 4.5 cohorts over the same multi-year window, and the dollar gap between those two outcomes is not a rounding error — it is the difference between a $19M and a $9.7M annualized run rate on Kazanjy's own numbers.
This is the reasoning that motivates the rest of this cluster. If ramp speed is the multiplier on everything downstream, the onboarding curriculum, the revenue-production-unit design, and the first-line management structure that supports ramping reps are not administrative overhead sitting alongside the sales motion. They are the sales motion's scaling infrastructure, and underinvesting in them shows up years later as a compounding shortfall that looks, from the outside, like a hiring problem or a market problem, when the root cause was a ramp curve that was never engineered to be short.
Common operator failures
- Treating ramp time as a rounding error in the model. The hiring plan assumes every rep is at full productivity from month one, or absorbs ramp loosely as "a few slow months," and the plan never gets updated when actual ramp time runs longer than modeled.
- No onboarding curriculum to shorten the ramp. New reps ramp against whatever the manager has time to informally teach them that week; ramp time is a function of which manager they happened to get, not a designed, repeatable process.
- Cohort cadence set by a hiring calendar instead of ramp capacity. A new class starts on schedule regardless of whether the prior class has actually cleared the ramp gate, so the manager is running two overlapping ramp cycles at half attention each, and both slow down.
- Measuring quota attainment instead of ramp time. A rep who eventually hits quota looks the same on the dashboard whether they ramped in 3 months or 7; the metric that actually drives the compounding curve is invisible in the reporting.
- No slack in manager bandwidth for the ramp-stage cohort. Ramping reps need disproportionate coaching time relative to fully-ramped reps; when manager time is allocated evenly across the team, the ramping cohort is starved exactly when the ramp-time investment would pay off most.
Related chapters
- The onboarding curriculum — the operational answer to shortening the ramp this chapter argues is the exponent.
- The revenue-production unit — the rep-plus-support unit economics behind the cohort math.
- Founder-led sales through $1M ARR — the operating posture before the team-scaling math in this cluster applies.
- The first AE transition — the single-rep ramp this chapter's curve describes, at its first instance.
Source and credit
The framework in this chapter — the single-rep ramp curve, the cohort-cloning math, and the compounding cost of a slow ramp — is Pete Kazanjy's. Kazanjy is the author of Founding Sales and the creator of the Founding Sales(foundingsales.com) course on founder-led and early-stage B2B sales, and the numbers and structure above are drawn directly from the ramp-economics parable in his Founder-Led Sales course. This chapter is Allston Labs' distillation of that material for operators building out a sales team — the credit for the framework and the underlying figures belongs to Kazanjy; the elaboration on mechanism and operator failure modes is ours.
Allston Labs operates the full sending estate as a service.
We provision domains, configure the entire authentication record set, run warmup, and monitor reputation across providers. The stack lives under your entity. The engineer on call lives in your Slack.