Ramp time is measured against your sales cycle, not against a benchmark: a rep rarely produces before one and a half cycles. What shortens it is not product training but early exposure to real customer conversations. The plan fits in three thirty-day blocks, each with one measure: understand, do supervised, do alone. A revenue target set before the third block manufactures bad qualification.
A hired salesperson costs their loaded salary for several months before returning anything. That is a known figure, rarely calculated, and almost never managed. In most companies, onboarding means a week of product training, access to the CRM, and instructions to start prospecting.
The result is a ramp that is endured rather than led, with two common outcomes: a rep who takes twice as long as expected, or one who leaves before producing. Both are expensive, and both are preventable.
Measure the ramp against your cycle, not a benchmark
The first mistake is comparing your ramp to a standard read elsewhere. The only reference that matters is your own sales cycle.
A rep does not sign before running a full cycle on deals they opened themselves, plus a learning margin. In practice, allow one and a half cycles before the first signatures, and two to three before cruising speed. With a three-month cycle, first deals arrive around month four or five, and that is normal.
Stating that expectation during the hiring interview changes two things: the candidate knows what they are signing up for, and leadership stops worrying in month two. An announced ramp can be managed; an implicit one produces pressure at the wrong moment.
Block one, thirty days: understand the customer
The usual order starts with the product, and that is the main cause of ramps that drag. A rep who knows every feature and cannot restate a prospect’s problem does not sell: they recite.
So start with the customer. The first thirty days serve four purposes: listening to recorded calls, won and lost; reading the notes from the last ten deals; talking to three existing customers; and talking to one lost deal. The product is learned in parallel, as an answer to problems heard, not as a catalogue.
The end-of-block measure is not a product test. It is a simple exercise: the rep must describe, without notes, a typical customer’s problem, the three most frequent objections, and what tips a decision. If they cannot, block two will be wasted.
This phase leans directly on what is written down. A company without a playbook mechanically adds several weeks to this block, and that is one of the hidden costs described in a sales playbook that survives your best closers.
Block two, thirty days: do it supervised
In the second month the rep speaks, but never alone. They run discovery calls with someone in the room, they write proposals that get reviewed, they handle objections with support.
The delicate part is the debrief. An accompanied meeting with no structured debrief teaches almost nothing: the rep retains a general impression. A useful debrief fits in three questions, asked immediately after: what did the customer say that we had not anticipated, at what point did the tone change, and what would we do differently.
The end-of-block measure is about qualification, not volume. Do the deals the rep created match the target? A newcomer creating many out-of-scope deals is learning a reflex that will have to be corrected, which costs more than creating nothing, and which points back to the targeting discipline described in why an ICP that is too broad kills growth.
Block three, thirty days: do it alone, with a net
In the third month the rep owns the full cycle, and that is when a revenue target becomes legitimate.
The net stays in place in two forms: the weekly pipeline review, where their deals are handled like everyone else’s, and one call listened to each week. That listening is what managers drop first when their calendar fills, and it is precisely what separates a three-month ramp from a six-month one.
The review ritual is not a control mechanism, it is where you decide what moves each deal forward, and it matters as much for a newcomer as for a veteran. We describe it in running a pipeline review that moves deals.
Why an early revenue target backfires
It is the most common reflex, and it produces exactly the opposite of what it seeks.
A rep asked for revenue in month two fills their pipeline with whatever they find, because they have to show activity. Out-of-scope deals come in, consume their time, and you will spend two quarters removing them. Worse, they will have learned that volume protects them, which is a durable reflex.
Before the third block, measure learning facts instead: customer conversations listened to, quality of qualification, ability to restate the problem. Those measures are less comfortable because they require judgement, and they are the only ones that predict what comes next.
The two signals of a ramp going badly
Deals created in quantity but out of scope. The rep produces visible activity and learns the wrong move. Intervene immediately, not at the quarterly review.
No questions after three weeks. It is almost always misread as autonomy. In most cases it signals someone who does not dare say they did not understand, and the recovery gets longer the more approximate habits they install.
What a well-run ramp returns
The immediate gain is time: one to two months saved on the first signature, which is easy to quantify by multiplying by the expected monthly revenue of the role.
The lasting gain is elsewhere. A structured ramp forces you to write down what was not written, and the document produced for the first hire serves every one after. That is the moment a company moves from competence held by people to competence held by the organisation, which is exactly what makes it less fragile to departures.
Where to start
Take your last sales hire and reconstruct their real ramp: start date, date of the first in-scope deal created, date of the first signature. Then compare to your sales cycle.
The gap tells you what your onboarding costs today. In most companies we open up, it represents several months of salary per hire, and nobody had ever calculated it.
Frequently asked questions
- How long is a B2B sales ramp?
- Allow one and a half sales cycles before the first signatures, and two to three cycles before cruising speed. With a three-month cycle that means four to five months for the first deals. Comparing your ramp to an external benchmark is meaningless: your cycle sets the floor.
- What should you teach first?
- The customer, not the product. A rep who knows the product by heart and cannot restate a prospect's problem does not sell. The order that works is: the problem, the typical customer, the real objections, then the product as an answer to all of it.
- When should you set a revenue target?
- From the third month, not before. A target set too early mechanically produces bad qualification: the rep fills their pipeline with whatever they find to show activity, and you will spend two quarters cleaning it up. Before that, measure learning facts, not revenue.
- How do you know a ramp is going badly?
- Look at the quality of the deals created, not their number. A rep creating many out-of-scope deals is learning the wrong reflex, and that takes longer to correct than creating nothing. The second signal is no questions after three weeks: it almost always means someone who does not dare say they did not understand.