A ramped rep is not the same thing as a tenured rep or a top rep. It is the status flag that says this seat produces full quota and belongs in the full-productivity column of the capacity model.
A ramped rep is a sales rep, usually an AE or BDR, who has completed their ramp period and is now expected to deliver at full productivity against their full non-ramped quota. In B2B SaaS the ramp period is typically six to nine months. Ramped reps are the core unit of capacity math, since only their full productivity counts toward next year's bookings plan. New hires and reps still inside the ramp curve are tracked separately because their contribution is scaled, not full.
The six things to know about a ramped rep before you plug the number into a capacity model, including why the ramped flag matters more than tenure and what separates a ramped rep from a new hire still on the curve.
A ramped rep is a sales rep who has completed their ramp period and is now carrying and accountable to their full non-ramped quota. The status is a binary flag inside the sales operating model: either the rep is ramped or they are not. Partial credit lives on the ramp curve, which is a separate measurement. Ramped is a graduation marker, not a performance score.
In B2B SaaS a rep usually becomes ramped between month six and month nine depending on segment. Transactional roles can ramp in three months. Mid-market reps commonly ramp at six months. Enterprise and platform sellers often ramp at nine or twelve months. The month a rep becomes ramped is set by the role, not by the individual, which is what makes the number stable across cohorts.
A new hire is still inside the ramp period, carries a stepped ramped quota, and contributes partial bookings toward plan. A ramped rep has finished that period, carries the full number, and contributes a full seat of productivity. The difference is not seniority or confidence. It is the measurement line that separates scaled contribution from full contribution in the capacity model.
A tenured rep is one who has been in the role for a long time, often two or more years. A ramped rep is any rep past the ramp line, which could be month seven on the job. Every tenured rep is ramped. Not every ramped rep is tenured. Capacity math uses ramped, not tenured, because ramp is the switch for full-quota accountability.
A capacity plan converts ramped headcount into bookings. If a team has 12 ramped AEs at a one million dollar quota and a historical 85 percent average attainment, the plan carries 10.2 million dollars in ramped capacity for that segment. New hires contribute scaled capacity on top. Mis-labeling an unramped rep as ramped overstates the plan, which is the single most common reason capacity misses in the back half of the year.
Ramped means the rep is expected to carry the full number. It does not mean they are hitting it. A ramped rep can be at 60 percent of full quota or at 140 percent. Both are ramped. Performance is tracked on top of the ramped flag, not instead of it. A manager who conflates ramped with top performer loses the ability to coach a struggling ramped rep back onto target.
The ramped line is the policy inside the sales model that declares a rep ramped. Different companies draw it differently, and the choice is not neutral. A line drawn too generously overstates capacity. A line drawn too conservatively hides productive reps and makes attainment look worse than it is. The six common line-drawing rules below are what mature sales ops teams actually use, and each one has a trade-off worth understanding before writing the policy down.
The simplest rule. A rep becomes ramped on the first day of the month after their ramp period ends, regardless of attainment. If the role carries a six month ramp, every rep hired in January becomes ramped on July first. Pros: easy to run, easy to forecast. Cons: a rep who missed the entire ramp curve becomes ramped on schedule anyway, which overstates capacity. Pair with a performance gate.
A rep becomes ramped on month N only if they hit at least a defined share of ramped quota during the ramp period, usually 70 or 80 percent. Pros: no capacity illusion from a stalled rep. Cons: more admin, and the gate must be reset each year when ramped quotas change. Enterprise orgs usually prefer this rule because one missed ramp curve is a strong signal the rep will not carry full quota in year two.
A rep is declared ramped the month after they first hit 100 percent of full non-ramped quota. Pros: ties the status to real productivity. Cons: a lumpy enterprise rep can hit full quota in month three on one big deal and become ramped before the curve finishes. Use with a two-consecutive-months rule, or combine with the calendar rule so a rep cannot ramp before the floor month.
A rep is ramped when their trailing six-month bookings annualize to at least full quota. Pros: filters out lumpy enterprise months and surfaces real repeatability. Cons: no rep can ramp before month six, which is fine for enterprise and wrong for transactional roles. The right rule for complex, long-cycle teams where a single-month spike should not count as proof of productivity.
The front-line manager signs off that the rep has completed the ramp program and is ready for full quota, with a short written note on territory, pipeline coverage, and forecast accuracy. Pros: catches context the data misses. Cons: inconsistent across managers, which creates downstream reporting noise. Best used as the final checkpoint on top of a quantitative rule, not instead of one.
A ramped AE who moves to a new segment or product may be given a shorter re-ramp or declared ramped on day one. Policy varies: a mid-market to enterprise jump usually resets the clock with a three to six month re-ramp. A product shift inside the same segment often does not. The rule should be written down, because inconsistent re-ramp policy is a common source of capacity drift.
The capacity plan converts headcount into committed bookings for the year. Ramped reps and unramped reps enter the plan on different lines because their expected contribution is different. A plan that treats a new hire as a ramped rep is overstated by whatever the ramp curve averages, usually 30 to 45 percent of full quota in the first six months. The capacity math below is how most SaaS finance and sales ops teams actually model the number, and why the ramped count sits at the center of it.
The ramped line in the plan is ramped AE count times full quota times the trailing historical attainment rate, usually blended across the last four to eight quarters. If 12 ramped AEs each carry one million at a blended 85 percent attainment, the plan carries 10.2 million from ramped reps in that segment. This is the stable, predictable half of the capacity model.
A new hire's expected contribution is the sum of their ramped quota by month across the ramp period. A six-month ramp at 0, 25, 50, 75, 100, 100 percent of full quota adds up to 3.5 months of full productivity across six months, roughly 58 percent of a ramped rep. The plan lines up new hires by start date so the capacity curve is honest about when their revenue actually lands.
To get a rep ramped by Q4, a six-month ramp means hiring by the end of Q2, which means posting the req in Q1. Hiring lead time rolled backwards from ramp date is what sets the hiring plan. A company that waits until July to hire for Q4 contribution is already short by the ramp curve math, which is why ramped reps are the single most important input to the headcount plan.
When a ramped rep leaves, the backfill is a new hire on a ramped quota, not a ramped rep. The team loses the full seat and gains a scaled seat, which is the attrition offset. A team with 15 percent annual AE attrition and a six month ramp loses about seven percent of full-year ramped capacity to turnover alone. Plans that ignore the offset consistently miss the second half of the year.
When a ramped AE is promoted to a different segment, product, or team-lead role, they leave the ramped column of their old segment. If the new role carries a re-ramp, they also do not enter the ramped column of the new segment until the re-ramp finishes. Capacity math has to subtract the promotion from the source team and add it correctly to the destination, or the plan quietly double-counts.
A capacity plan rarely assigns exactly the target number. Teams assign 110 to 125 percent of plan across ramped reps to absorb attrition, under-attainment, and ramp slippage. The over-assignment ratio is a function of historical attainment, attrition, and ramp success rate, not a round number. Mature sales ops teams recompute it yearly against the actuals, not by habit.
Capacity math works only when the system of record agrees with the hiring plan and the compensation plan on which reps are ramped. If the three disagree, finance uses one number, sales uses another, and the plan drifts within a quarter. A CRM that treats ramped as a tracked status, with policy, dates, and quota automatically carried through to the forecast and the dashboards, is what keeps the three sources in sync. The loop usually looks like this.
Each rep record carries a ramped status, ramped date, ramp policy, and current quota (ramped or full). The flag is set by the policy rule configured for the role, not by a one-off manual edit, which keeps the data auditable. Finance, sales ops, and the manager read the same status from the same record, so the capacity plan and the compensation plan start from the same source of truth.
Strkr steps a new hire's quota each month across the ramp schedule and switches to full quota automatically on the ramped date. Forecasts, pipeline coverage math, and compensation calculations all read the current month's quota from the schedule, not from a manual spreadsheet. The ramped flag flips the moment the step reaches full, which keeps the dashboards consistent with the comp plan.
A single workspace view lists ramped reps by segment, team, and manager, with a running count and projected ramp dates for everyone still on the curve. The capacity model consumes this number directly, so when a new rep crosses the ramped line the capacity plan sees it the same day. No reconciliation meetings between sales ops and finance.
Strkr AI reads activity, pipeline, and forecast history across the ramp period and flags reps who are drifting against the on-curve cohort, so the manager can intervene before the ramped-date deadline. The one-on-one agenda becomes specific in month three or four, which is when a drifting ramp still has time to recover before the attainment gate.
Attainment dashboards split ramped and unramped contribution on every chart, so a manager never sees a blended number that hides a slow ramp or an unproductive ramped seat. The split is also the view the CFO reads, which is how the plan avoids the common quarterly surprise of a strong headline attainment number masking under-contribution from the ramped column.
The ramped headcount, ramped quota, trailing attainment, and new-hire ramp curve export directly to the capacity model finance maintains. One source, one number, one plan. The ramped column of the plan becomes a live reading of the CRM rather than a point-in-time spreadsheet, which is what finally stops the drift between the sales plan and the finance plan.
Strkr tracks ramped status as a first-class attribute on every seat, steps ramped quotas into full quota automatically, and feeds a live ramped headcount into the capacity model. The plan, the comp sheet, and the dashboards read the same number, which is how a sales org finally stops losing a quarter to a reconciled spreadsheet.
A new hire is a rep still inside the ramp period, carrying a stepped ramped quota that scales toward full. A ramped rep has completed the ramp period and is carrying the full non-ramped quota. The difference is the measurement line in the capacity model: new hires contribute scaled capacity on the ramp curve, ramped reps contribute full seats. Every ramped rep was once a new hire. Not every new hire makes it to ramped.
A tenured rep has been in the role for a long time, usually two years or more. A ramped rep is any rep past the ramp line, which could be month seven on the job. Every tenured rep is ramped, but a rep who just crossed the ramped line last month is not yet tenured. Capacity planning uses ramped because ramped is the flag for full-quota accountability. Tenure is a separate dimension used for coaching, retention, and promotion planning.
A rep is considered ramped when they cross the ramped line defined by the company's ramp policy. The common rules are a calendar rule (month N since start), an attainment gate (hit at least 70 to 80 percent of ramped quota during ramp), a full-quota month rule, a trailing-six annualized attainment rule, or a documented manager sign-off. Most mature programs combine a calendar floor with an attainment gate so a rep cannot be ramped on paper without actual productivity.
In B2B SaaS the ramp period is typically six to nine months. Transactional and SMB roles can ramp in three months. Mid-market usually ramps at six. Enterprise land-and-expand ramps at nine. Complex enterprise, platform, or regulated-industry sellers often need twelve. The right ramp length is driven by average sales cycle length and deal complexity, not by what a founder wishes it could be. A ramp set shorter than the sales cycle will routinely fail to produce ramped reps.
Capacity math converts headcount into bookings, and only ramped reps carry full-quota expectations. Ramped headcount times full quota times the historical attainment rate is the stable half of the capacity plan. New hires contribute scaled capacity on top, based on where they are in the ramp curve. Mis-labeling an unramped rep as ramped overstates the plan by the gap between stepped and full quota, which is the single most common cause of back-half capacity misses.
Not usually. Ramped is a graduation marker, not a performance score. A ramped rep who is under-performing is tracked through the normal performance process, not re-flagged as unramped. The exception is role transfer: when a ramped AE moves to a different segment or product that carries its own ramp, they may be put on a re-ramp with a shorter schedule, usually three to six months. The re-ramp policy should be written down because inconsistent handling is a common source of capacity drift.
Every ramped rep is a quota-carrying rep, but not every quota-carrying rep is ramped. A new hire inside the ramp curve carries a ramped quota and is still quota-carrying. A sales engineer or customer success manager with an attach-rate target may carry quota without being an AE at all. The ramped label specifically marks an AE or BDR who has finished their ramp and now carries the full non-ramped quota for their role.
Ramped productivity is the full-quota bookings a ramped rep is expected to deliver in a year, blended by the historical attainment rate for the role. It is the number used to size territories, set hiring plans, and over-assign quotas across the team. A company that quotes ramped productivity as the plain full quota is overstating capacity by the attainment gap. The honest number is full quota times trailing attainment, carried per ramped seat in the model.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
