Lesson 1 of 5 · 14 min · ends with a checkpoint

What ramp actually is

On this page
What you'll learn1. What ramp actually is2. Days 1–30: learn

Premium module, sold separately — and deliberately so. Module 08 ends the moment you accept the offer. This one starts the Monday after.

The first ninety days in a sales seat are the highest-anxiety period of the whole career, and the one nobody teaches. The interview process is drilled to death; the ramp is left to fend for itself, on the assumption that a good hire will work it out. Plenty don't — not because they can't sell, but because nobody told them what the first quarter is actually for, what their manager is really measuring, or how long the maths takes to turn activity into revenue.

One rule above all: in your first ninety days you are not judged on revenue — you are judged on whether revenue has become predictable. Almost every ramp mistake is a version of forgetting that.

What you'll learn

  • What a ramp period actually is — ramped quota, draws, guarantees — and honest data on how long new reps take to produce, so you can calibrate against reality instead of dread.
  • A concrete 30-day learning plan: product, ICP, competition, process, CRM and call listening, with a week-by-week checklist and a "teach it back" test that proves you've learned it.
  • How to build a first pipeline from nothing — territory analysis, the first 50 accounts, the first sequences — and the arithmetic of how long activity takes to become pipeline.
  • Days 31–60: your first solo discovery calls, the first demo you lead, how to ask for help without looking weak, and the one-deal-end-to-end milestone.
  • Days 61–90: first proposal, first negotiation, first close or first honest forecast, and how to run a pipeline review your manager believes.
  • How to manage your manager — one-to-ones worth having, asking for coaching, escalating blocked deals, and what "coachable" looks like in practice rather than in adjectives.
  • Territory tiering and calendar architecture: the discipline that separates reps who ramp from reps who drown, and the trap of activity theatre.
  • The honest signals that it's going badly, what to do about each, how UK capability procedures and PIPs actually work, and how to tell a wrong role from a wrong you.
  • A 30/60/90 scoreboard by role, so you can self-assess instead of guess.

1. What ramp actually is

The definition nobody gives you

Ramp is the period between your start date and the date your employer expects full production. It's a commercial decision, not a courtesy: the company has modelled how long you'll cost more than you return and priced it into the hiring plan.

Three things move during ramp, at different speeds. Knowledge — product, market, buyer, process — moves fastest, in weeks. Activity — calls, sequences, meetings — follows within weeks of that. Output — pipeline, then revenue — is slowest, lagged by the full length of your sales cycle.

Almost all new-rep despair comes from watching the third curve while working on the first two. It cannot move yet; it is arithmetically impossible for it to move yet, and the next few pages prove it.

Ramped quota, and how comp works while you ramp

You will usually carry a ramped quota: a phased target stepping up to full quota over the ramp — commonly 0/33/66/100% across your first four quarters, monthly steps for short-cycle and SDR seats, or (most honestly, in long-cycle markets) a quota that starts one full sales cycle after your start date.

Against that quota, the variable half of your pay is protected by one of two mechanisms — and the difference between them is the most important number in your contract that isn't the base:

  • A guarantee. Your variable is paid at 100% of plan, or a stated fraction, for n months regardless of what you book. You keep it.
  • A draw. An advance against future commission. The critical question is whether it is recoverable — clawed back out of later commission — or non-recoverable, which behaves like a guarantee.

Worked example on realistic UK entry-level numbers: base £38,000, OTE £60,000 — so variable is £22,000 a year, roughly £1,833 a month. A six-month non-recoverable guarantee pays you £11,000 and you owe nothing. A six-month recoverable draw pays the same £11,000 and you now owe it: if your first real commission month earns £2,500, you may see none of it. Reps have discovered this in month eight, in a bad quarter, and been unable to make rent.

Neither is dishonest and both are normal, but know which you have, over what period, at what rate, and — for a draw — whether recovery is capped per month. If you didn't ask at offer stage (Module 08, Section 8), ask in week one, along with any ramp accelerator on early deals and any clawback on churn.

Voice from the field

In The Sales Development Playbook, Trish Bertuzzi makes the ramp arithmetic uncomfortably plain: a rep's productive time is simply tenure minus ramp. On the figures she cites — three to four months to ramp an SDR against average tenure of twelve to eighteen — a large slice of a sales development career is spent not yet being good at it. The point isn't despair: every week you shorten your own ramp is a week added to the only part of the job that pays.

How long it actually takes — the honest numbers

Be sceptical of ramp statistics: most figures on sales blogs trace back to a handful of surveys, get rounded, lose their sample size and reappear as fact. Two sources publish method and sample. The Bridge Group's AE research (2026, tenth biennial edition, 158 B2B companies) puts average AE ramp at 6.2 months — the highest in that study's history — with 48% of AEs achieving annual quota. Their SDR research (2025, 351 companies) puts SDR ramp at 3.0 months, the lowest since 2010, with median tenure of 1.9 years and 60% of SDRs at quota, the lowest on record in that series.

Outside sales, Michael Watkins' The First 90 Days reports asking more than 200 CEOs how long a mid-level leader takes to reach "break-even" — the point at which they contribute as much value as they have consumed. The average answer: 6.2 months. Different research, different population, near-identical number: half a year to net-positive is the normal shape of joining anything.

Working ranges to plan against, not to quote as law:

Role Typical time to first meaningful output Typical time to full quota
SDR / BDR First qualified meetings, weeks 3–6 2–4 months
SMB / transactional AE First closes, months 2–4 3–6 months
Mid-market AE First closes, months 4–7 5–9 months
Enterprise / NHS / regulated AE First closes often months 7–12 9–15 months

The rule that beats all of the above

Ramp is measured in sales cycles, not calendar months. Jason Lemkin's standing advice at SaaStr is to expect a rep to close inside roughly one sales cycle and be fully ramped by about two — so a 30-day-cycle business should see production in 60 days, and a nine-month-cycle business should not expect a close in the first year. The first question of your ramp is therefore not "how am I doing?" but what is the average cycle length here, from first meeting to signature, for deals like mine? Get it from CRM data, not folklore. Then:

Your ninety-day revenue expectation = whatever your cycle length permits, and nothing more. Your ninety-day pipeline expectation is where the actual judgement happens.

On a five-month cycle, a closed deal by day 90 would require a deal to appear, qualify and complete faster than the business has ever managed. Anyone who expects it — including you — is confusing hope with arithmetic.

What "productive" means to your manager

Ask three sales managers what they need from a new rep at day 90 and you get the same three answers in the same order. Enough qualified pipeline that the number is mathematically possible — not "activity", but named opportunities with a value, a stage, a next step and a date. A forecast they can believe: a rep who says £40k in March and delivers £40k in March is worth more than one who says £150k and delivers £60k, because forecast accuracy is the currency of trust in every sales organisation. And the core motions run unaided — discovery, demo, proposal, objection handling, CRM hygiene, without a chaperone.

Notice what is not on that list: revenue, hours worked, dials, enthusiasm. Those are inputs or lagging outputs. The list is what your manager is assessed on by their manager, which is why it becomes the measure of you.

Field note

"Productive" is a moving target set by your manager's own reporting. Most first-line managers report weekly on three things — team pipeline coverage, forecast versus commit, and activity by rep — so your ramp reaches them as a row in a spreadsheet, updated whether or not you talk. Hence two rules: your CRM record is your reputation, because a deal that isn't in the system did not happen; and in week one, ask to see the exact report your manager submits upward. Understanding the row you occupy tells you more about what to prioritise than any onboarding deck.


2. Days 1–30: learn

The first month has one job: earn the right to an opinion. You are converting yourself from someone who has read the website into someone a buyer would sensibly spend thirty minutes with.

Run it as six parallel workstreams, not as whatever onboarding happens to serve up.

2.1 The product — how to learn it fast without engineering help

You will not get much engineering time and you should not need it. In order of value per hour:

  1. Use the product as a customer would. Sandbox on day one; complete the journeys customers actually care about, start to finish. What confused you is what confuses your buyer, and it's worth more than any feature list.
  2. Take whatever certification exists, immediately. If demo certification is normally week six, ask to sit it in week three. Volunteering to be tested early is the cheapest credibility a new rep can buy.
  3. Read the help centre and release notes — the product in the customer's vocabulary, plus what the company thinks matters and what recently broke.
  4. Read fifty support tickets. The fastest honest picture of where the product frustrates people — which is what you'll be objected to about in month two.
  5. Sit on two implementation calls. You learn what "yes" actually costs the customer, which is what makes late-stage deals stall.
  6. Build a one-page "how it works" — architecture, data flow, integrations, what it does not do — and have a solutions engineer check it. A specific fifteen minutes gets a yes where "can I pick your brain" gets a maybe.

The week-two deliverable is not knowledge; it is a three-minute explanation of what the product does, in plain English, to someone outside your industry. If you can't do that, you don't know it yet.

2.2 The ICP and the buyer

Your Ideal Customer Profile is not the marketing slide; it's a pattern in the data. Find it yourself:

  • Pull the last 20 closed-won and 20 closed-lost from the CRM. What do the wins share — size, sub-sector, existing systems, trigger, champion, problem named? What do the losses share? The gap between those two lists is the most valuable document you'll produce in month one.
  • Ask three customers directly. Have customer success introduce you for twenty minutes each: "I'm new and I want to understand what problem we actually solved for you." Ask what they did before, what triggered the search, who else was in the room, and what nearly stopped them buying.
  • Write the buyer's day. One page per persona: what they're measured on, what makes them look good to their boss, what they'd give up to buy from you. In UK health tech this cast is specific and learnable — Module 07 has the map; use it precisely rather than approximately.

2.3 The competition

Get the battlecards, then check them against reality — they're written by people motivated to win. Read the competitor's site and recent customer announcements, plus third-party reviews and, in health tech, published evaluations and framework listings; buyers read these, so read them first. Then ask customer success two questions — what did our customers switch from, and what made them switch? and what do we lose to, and why? — because those answers are your competitive positioning in the words of people who watched it happen. Finally, learn the do-nothing competitor, which wins more deals than any named rival: what does the buyer do today, why is it tolerable, and what makes it stop being tolerable?

2.4 The sales process and CRM conventions

Every CRM uses the same words and means different things by them. Get the local definitions in writing in week one: stage definitions and exit criteria (what must be true to move from stage 2 to stage 3 here); what counts as a qualified opportunity, the most-disputed definition in any sales org; forecast categories — commit, best case, pipeline, omitted — and who may change them; hygiene rules; and the qualification framework in local use, plus the more useful disqualification rules: what makes this company walk away.

Then adopt the conventions exactly, even if you think yours are better. A rep who quietly runs a private system is invisible in the report their manager submits — the only place their work is counted.

2.5 Listening to recorded calls — what to listen for

If your company records calls, you've been handed a training corpus most reps never open. Commit to twenty calls in thirty days — five wins, five losses, five first meetings, five late-stage — and score each against a fixed checklist rather than listening passively:

  • The first ninety seconds — agenda set, permission asked, time confirmed?
  • The talk ratio, honestly estimated, and the question count — which one made the customer stop and think?
  • The moment the customer revealed the real problem, and what the rep did in the next thirty seconds. The highest-value moment on any recording.
  • The objection — what was said, what did the rep do first, resolved or buried?
  • The close — what next step was agreed, how specific, was a date set in the call?
  • What you'd have done differently. One line, every call — the bit that turns listening into learning.

Keep the notes in one document. By call twenty you will have derived your company's real playbook, including the parts nobody wrote down.

Voice from the field

Gong's data team has analysed sales conversations at a scale no individual can: an often-cited study of 519,291 recorded calls found discovery calls performed best at roughly 11–14 seller questions, with the strongest talk-to-listen balance near 43% seller to 57% buyer, and conversion falling away once the seller passed about 65% of the airtime. The numbers matter less than the habit they should create: when you review a recording, yours or anyone's, count the questions and estimate the ratio — every time.

Voice from the field

"The first task in making a successful transition is to accelerate your learning… The more efficiently and effectively you learn, the more quickly you will close your window of vulnerability."
— Michael D. Watkins, The First 90 Days

2.6 Shadowing — how to do it so it counts

Shadowing is wasted when the new rep is a spectator. Three rules fix it: ask for a job on the call ("can I take the notes and send the recap?"), because you learn ten times more writing the summary and you've made yourself useful rather than expensive; pre-brief and debrief — two minutes before on the goal, five after on what you missed, since reps who won't give you an hour will give you seven minutes; and shadow losses too, because watching someone manage a stalled deal teaches more than watching a signature. Spread it across the top biller, a mid-performer whose technique is more copyable, customer success, and one procurement conversation.

2.7 The "teach it back" test

At day 30 you should pass three tests — set them up yourself if nobody sets them for you. The plain-English test: explain what the product does, who buys it and why, in three minutes, to someone outside your industry; if they can repeat it back, you pass. The objection gauntlet: a colleague fires the eight most common objections at you in ten minutes, and you need a structured answer to all eight. The demo pass: the standard demo, unaided, in the allotted time, without notes.

Failing these at day 30 is recoverable and useful. Discovering at day 60 that you would have failed them is not.

2.8 Week-by-week checklist, days 1–30

Week Do this
1 — access All systems live. Read the comp plan; confirm ramped quota, guarantee/draw type and ramp end date in writing. Agree the 1:1 rhythm and what "good" looks like at day 30/60/90 — write it down and send it back. Ask to see the report your manager submits upward. Complete the sandbox journeys. Book fifteen-minute introductions: two top reps, CS, a solutions engineer, marketing, implementation.
2 — product and process Sit or schedule certification. Read 50 support tickets, the help centre, last quarter's release notes. Write the one-page "how it works" and get it checked. Get stage definitions, exit criteria and forecast categories in writing. Score five recorded calls. Deliver the three-minute plain-English explanation.
3 — market and buyer Analyse 20 closed-won and 20 closed-lost; write the pattern document. Three customer conversations; a buyer-day page per persona. Competitive pass. Score eight more calls; shadow four live calls, writing the recap on each.
4 — territory and readiness Define the territory; build the tiered first 50 (Section 3). Draft two sequences and have a senior rep tear them apart. Sit the objection gauntlet and the demo pass. Book your first self-sourced meetings — the target is some, not many. Present a one-page day-30 summary: what you learned, what you built, what you need.

Checkpoint 1 · answer to continue reading
Question 1 of 3
Your offer includes 'a six-month draw at 100% of variable'. Why does the module say you must establish one further detail before relying on it?