Sales ramp time is four clocks running at once
- Knowledge. Product, market, competitors, pricing, positioning. The fastest of the four to fix, and the one every onboarding program over-invests in, because content is easy to build and easy to test. It is almost never the bottleneck.
- Systems. The CRM, the sequences, the dialer, where things live, who to ask when something is broken. Unglamorous, rarely in the plan, and quietly responsible for weeks of drag in most teams.
- Conversation ability. Whether the rep can run a call: hold a structure, ask a real question, handle the pushback, agree a next step. The slowest to build and the only one that requires another person on the other end.
- Pipeline maturation. Even a rep who was perfect on day one cannot close a deal faster than the sales cycle allows. Training cannot touch this clock at all, and confusing it with the other three is the single most common reason a good onboarding program looks like a failure.
That fourth clock is also why cross-company ramp comparisons are close to meaningless. A team with a two week cycle and a team with a nine month cycle are measuring two different phenomena with the same word. Benchmark surveys of SaaS sales organizations, such as the ones the Bridge Group has published for years, are useful for orientation and dangerous as targets, because the companies inside the average do not sell what you sell.
What plausibly moves it
| Intervention | Which clock | How you would know |
|---|---|---|
| Frequent spoken roleplay conversations | Conversation ability | The manager can predict a rep's live call before hearing one |
| Written answers to the questions new reps always ask | Knowledge, systems | Repeat questions in the team channel drop off |
| A named onboarding owner with protected hours | All four | The plan survives a busy quarter without quietly stopping |
| Shadowing plus a debrief the new rep must answer in | Knowledge, conversation | They can explain why the senior rep asked what they asked |
| Early live calls on low stakes accounts | Conversation, systems | The rep has run the full shape of a call before it matters |
| Certification on behavior before the first real call | Conversation | Weak spots surface in practice instead of in the pipeline |
What looks useful and mostly is not
- A longer program. Length is not intensity. A course measured in weeks with almost no speaking in it is weaker than a short one built entirely around speaking. Duration is easy to report to leadership, which is exactly why it gets optimized.
- Recorded content libraries. Genuinely useful as reference material and close to useless as training. Watching a library does not install the ability to speak, which is why a roleplay minute and a viewing minute are not the same minute.
- Product knowledge quizzes. They test the clock that was not the bottleneck, and they generate a satisfying pass rate that has no relationship to whether the rep can hold a discovery call.
- A buddy system with no time budget. Assigning a mentor without protecting their hours produces a mentor who is unavailable and a new rep who learns not to ask. That is worse than assigning nobody, because it closes the question.
- Hiring for experience as a ramp strategy. Experienced reps ramp faster on process and not at all on your market, and they are subject to the same pipeline clock as everybody else. They also arrive with habits, which is sometimes the point and sometimes the problem.
Why the number is hard to measure honestly
This is the part usually left out of articles on this topic, and it is the part a sales leader most needs before signing off on a program. Ramp improvement is one of the least reliable measurements in sales operations, for five separate reasons that stack.
- Definition. "Ramped" means first closed deal at one company, first month at quota at another, three consecutive months at quota at a third, and some share of a tenured rep's quota at a fourth. Those definitions can differ by a full quarter for the same person. Most cross-company comparisons are comparisons of definitions.
- Cohort size. Most teams hire a handful of reps a quarter. A result measured across four people is a result about four people, and one unusually strong hire moves that average further than any program will.
- Regression to the mean. Onboarding programs get launched right after a bad cohort. The next cohort will usually look better whatever you do, which is regression toward the mean rather than evidence, and it is the most common way a mediocre program acquires a reputation.
- Selection. If the program is optional, the reps who opt in are the reps who would have done well anyway. If the company got better known between cohorts, the program gets credit that belongs to recruiting.
- Territory and timing. A rep who ramps in a strong quarter with a good patch ramps quickly, and none of that is about training. Nobody reports this, because there is no incentive to.
If you cannot say in one sentence what "ramped" means at your company, any ramp improvement you report is a story about your definition.
How to measure it anyway, with the caveats attached
None of that means give up on measuring. It means measure with the caveats attached. Write the definition down and leave it unchanged for at least a year, even when a different one would flatter the quarter. Report cohorts rather than a rolling average, so a single hire cannot carry the story. And track a behavior measure alongside the outcome measure, so you can see whether the thing you trained actually changed before you ask whether revenue did. A roleplay score on a fixed scenario is one of the few behavior measures that is cheap enough to take weekly.
When the four clocks are weighted differently
In real estate and investor acquisitions teams the four clocks are weighted very differently. Product knowledge is thin: a buy box, the arithmetic, the contract. Systems matter more than people expect, because list discipline is most of the job. Conversation ability is close to everything, since the work is a high volume of similar calls where a small difference in the first minute compounds across hundreds of dials.
The pipeline clock is short compared with enterprise software, which is good news: feedback arrives in weeks rather than quarters, so you can actually tell whether something worked. It also means a bad conversational habit gets expensive fast. A new rep with a weak opening burns leads at exactly the rate they dial, and the list does not grow back.
Which is the argument for front-loading roleplay volume in this niche specifically. Every conversation a rep has before their first live list is a conversation that costs no address. In pichi.ai those calls run by voice against an AI seller, get scored against the criteria the team is coached on, and give a manager something to look at before the rep's first dial rather than after their first hundred. The same argument applied to a list you paid for is sales onboarding without burning leads, and the week by week view of month one is first 30 days of a new sales rep.