What 'Fully Ramped' Actually Means, and Why Every Team Defines It Differently
Ask five sales leaders what 'ramped' means and you'll get five different thresholds, none of them written down anywhere.
Ask five sales leaders what "ramped" means and you'll get five different answers, and none of them will be written down anywhere. One says two consecutive months at 100% of quota. Another says three closed deals, doesn't matter which three or what size. A third says, more or less, "I know it when I see it" — which is the most common answer in the industry and the least defensible one to put in a board deck. Ramp time gets quoted in every enablement report, every new-hire cost model, every VP's QBR slide, treated as if it's one stable, comparable number. It isn't. It's five different measurements wearing the same label, and that ambiguity is quietly wrecking every decision built on top of it.
The four definitions hiding under one word
Most organisations are running one of these, usually without having chosen it on purpose.
- Quota attainment. Clean on paper — hit X% of quota for Y consecutive periods. But the threshold is picked by committee and rarely revisited, it ignores pipeline lag entirely (a rep can be doing everything right and still be three months from a closed deal in a 90-day cycle), and it quietly punishes anyone dropped into a thin territory through no fault of their own.
- Deal count. "Ramped after three closed-won" sounds objective until you notice it treats three £2,000 logo deals the same as three £80,000 multi-stakeholder ones. Same number, wildly different skill bar cleared.
- Tenure. "Ramped at four months" because that's what the offer letter has always said, irrespective of what actually happened in those four months. This is the laziest definition on the list and, not coincidentally, the most common — it requires no measurement at all.
- Manager gut feel. The fastest to declare, and the one every experienced leader secretly trusts most. It's also the one that cannot survive the follow-up question "based on what, specifically?" — most managers, pressed, cannot answer it.
None of these four is wrong, exactly. Each is measuring something real. The problem is that most organisations run one without naming it, let it drift between managers, and end up with a "ramped: yes/no" field that means a different thing depending on who typed it in.
Why this makes your ramp-time number unusable
The obvious cost is benchmarking. Comparing a 47-day ramp time in Team A against a 90-day figure in Team B is meaningless if A means "hit three activity-to-conversion targets" and B means "manager stopped worrying." You're not comparing two teams' performance. You're comparing two different instruments and pretending they're the same ruler. Most companies that quote a single ramp-time figure to their board haven't checked whether it means the same thing this year as it did last year, let alone the same thing across two acquired teams now reporting into one dashboard. If you want a sense of how much unstated variation is baked into terms your whole org treats as settled, the Sales KPI Dictionary is a useful gut-check — "ramped" is far from the only term doing more silent work than anyone's agreed to.
The less obvious cost is worse: it breaks coaching. A binary flag tells a manager nothing about what to do differently. If a rep is marked "not ramped" at day 75, that flag gives zero direction on which of a dozen possible gaps is actually holding them back — discovery, objection handling, negotiation, territory planning, or something as mundane as CRM discipline masking real pipeline health. You've spent 75 days generating a data point that cannot inform a single coaching conversation.
What "ramped" should mean instead
Replace the single flag with tiers, and anchor each tier to named competencies with observable evidence — not to a manager's impression of vibe.
| Tier | What it certifies | Evidence required |
|---|---|---|
| Tier 0 — Onboarded | Product and market fluency, clean CRM hygiene | Passes a product knowledge assessment; logs activity correctly without prompting |
| Tier 1 — Independent | Can run a full-cycle conversation without a manager in the room | An observed discovery call scores at "competent" against a rubric; qualification framework applied correctly, not just recited |
| Tier 2 — Ramped | Executes the core competencies consistently, unsupervised, across a full cycle | Three consecutive observed calls score "proficient" or above on discovery and objection handling; deal velocity within 20% of team median |
| Tier 3 — Proficient | Handles the harder version of the job — multi-stakeholder, senior-level pushback | Named competency scores at proficient across negotiation and multi-threading, not just discovery |
The point of the table isn't the specific thresholds — yours will differ by motion and deal size. The point is that each tier certifies something a rubric can actually score, rather than a manager's confidence that "they seem ready now." A New Rep Certification Scorecard is the difference between that evidence being auditable and it living in a manager's memory of a Slack message from six weeks ago.
The second and more important shift: ramped isn't a flag, it's a vector. A rep can be Tier 2 on discovery and Tier 1 on negotiation — that's normal, and it's the useful signal a binary flag destroys the moment you collapse it to yes or no. Once you're tracking tiers per competency instead of one flag per rep, "ramp time" stops being a single number and becomes a set of them: time to Tier 1 discovery, time to Tier 2 negotiation, and so on. That's a genuinely comparable metric across teams, because it's measuring the same named thing every time, not a manager's mood.
Building it without starting from zero
You don't need a research project to stand this up. Name four to six competencies that actually matter for the role before you argue about thresholds. Define what "proficient" looks like in observable terms for each one — a sentence a manager could use to score a real call, not an adjective. Certify with structured evidence, gathered the same way every time. A 30-60-90 Day Sales Plan Template is a reasonable place to hang the tier definitions if you don't want to stand up a separate system on day one — the structure already exists, it's just rarely used to certify anything specific.
The reason most companies haven't written their definition of "ramped" down isn't that it's hard. It's that writing it down means admitting the manager's gut isn't a system. It's a perfectly good instinct. It makes a terrible spreadsheet column.