A new account executive joins on a Monday. By the standard industry estimate, they will reach full productivity somewhere between month three and month six. For a team of ten with 25% annual turnover, that is roughly one rep-year of quota capacity spent every year on people who are not yet able to sell.
Most ramp programs treat this as a training problem: more sessions, more shadowing, a bigger playbook. It is mostly a knowledge-transfer problem. The things a new rep needs to know already exist inside the company. They are just not in a form anyone can hand over.
This guide lays out a framework for shortening ramp by fixing the transfer, not by adding training hours.
Why ramp takes as long as it does
Ask a sales leader what a rep needs to be productive and the list is consistent:
- Product knowledge: what it does, what it does not do, how to demo it
- Market knowledge: who buys, why, and what they say when they are deciding
- Objection knowledge: what prospects push back on and what actually works in response
- Competitive knowledge: who else is in the deal and how to position against them
- Account knowledge: for inherited territory, what has already happened with each account
Now ask where each of those lives. Product knowledge is in the docs and the enablement deck. Everything else is distributed across people. The best objection responses are in the heads of the top two reps. Competitive positioning is in a battle card that was current four months ago, plus whatever the PMM remembers from Slack. Account history is in sparse CRM notes and call recordings nobody has time to re-listen to.
The new rep's ramp is the time it takes to reconstruct all of that by osmosis: sitting in on calls, asking questions in Slack, losing a few deals, and slowly building the pattern library a veteran carries around. Three to six months is how long osmosis takes.
Two figures from the research behind this guide frame the cost. Reps spend roughly 30% of their time on administrative work rather than selling, much of it looking for information across tools that do not share it. And when a rep leaves, that pattern library leaves with them, so the next hire starts the reconstruction from zero.
Common approaches and where they fall short
| Approach | What it does well | Where it breaks | |----------|-------------------|-----------------| | Shadowing and ride-alongs | Exposes the rep to real conversations | Sample size is tiny. A rep sits in on 15 calls in a month and sees a random slice of what the team knows. | | Call recording libraries | Every call is available | Available is not the same as findable. A search for a competitor returns 47 calls with no way to isolate the objection pattern. | | Static playbooks | Codifies the basics | Goes stale in weeks. Objection responses written in January do not reflect what prospects said in June. | | Buddy systems | Puts a veteran on call | Bottlenecks on the veteran's time and mood. Knowledge transfer happens only when they are asked the right question. | | Certification programs | Verifies product knowledge | Tests the one category that was never the problem. Nobody fails ramp because they could not demo. |
Each of these addresses the symptom (the rep does not know things) with more exposure. None of them changes the underlying condition: the knowledge is unstructured, scattered, and current only in someone's head.
The better approach: treat ramp as a knowledge-transfer system
The teams that ramp fastest have, deliberately or by accident, built a system where institutional knowledge is captured as a byproduct of selling and made retrievable by anyone. The new rep does not reconstruct the pattern library. They inherit it.
The framework has four parts.
1. Inventory what a productive rep actually knows
Before building anything, list the knowledge categories and map where each currently lives. Be specific. "Competitive knowledge" is not one thing; it is positioning against three or four named competitors, each with its own set of objections and win conditions.
A worked inventory for a mid-market SaaS team might look like this:
| Knowledge category | Where it lives today | Who holds it | Retrievable by a new rep? | |--------------------|----------------------|--------------|---------------------------| | Product capabilities and demo flow | Enablement deck, docs | Enablement | Yes | | Top 10 objections and working responses | Heads of top 2 reps; scattered Slack threads | Reps | No | | Positioning vs. Competitor A, B, C | Battle card (4 months old); PMM's memory | PMM | Partially | | Buyer language by segment | Call recordings | Nobody | No | | Pricing objection patterns and discount history | Deal desk emails; CRM notes | Sales ops | No | | Account history for inherited territory | CRM notes (sparse); recordings | Departed rep | No |
The right-hand column is the ramp problem, made visible. Everything marked "No" is something the new rep will spend months rebuilding.
2. Capture from the work, not from the calendar
The reason playbooks go stale is that updating them is a separate task from selling, and separate tasks lose to quota. The fix is to capture knowledge from artifacts that already exist because selling happened: call transcripts, deal notes, loss reviews, email threads.
Practically, this means routing every call transcript through a step that extracts the objections raised, the competitors mentioned, the pain points stated in the prospect's words, and the outcome. Whether that step is a person with a template, a call-intelligence tool, or an AI extraction pipeline matters less than the fact that it runs on every call rather than on the 5% someone has time to review.
Teams evaluating tooling for this step can compare options in the call intelligence tools directory category. The criterion that matters for ramp is not transcription quality, which is table stakes; it is whether the tool produces structured, retrievable knowledge or a searchable pile of recordings.
3. Structure it so it can be handed over
Extracted knowledge needs a shape. A new rep should be able to ask "what do enterprise CFOs object to, and what works?" and get a ranked answer with examples, not a list of calls to listen to.
The minimum structure that works:
- Objections, each with frequency, the segments it appears in, and the responses that preceded a won deal versus a lost one
- Competitor profiles, each with the objections they generate, the deals they appear in, and the positioning that wins (see How to build competitive battle cards)
- Pain points by segment, in the customer's language, with the calls they came from
- Account summaries for any territory being handed over: last three interactions, open objections, competitors in play
This is where a template earns its keep. The competitive battle card template is the structure for the second item; the same discipline applies to the others.
4. Make retrieval part of the daily workflow
Knowledge that lives in a wiki the rep has to remember to visit will not be used. The retrieval step has to sit where the work happens: in call prep, in the CRM record, in the follow-up draft.
The test is call prep time. A veteran rep preps for a discovery call in five minutes because they already know the account's history, the likely objections, and the competitor to expect. A new rep with the same information in front of them can prep in five minutes too. If prep takes the new rep 30 minutes, the system is not delivering the knowledge at the point of use.
Step-by-step implementation
- Run the inventory (week 1). Use the table above. Interview your two best reps and your PMM. Mark every category the new rep cannot retrieve on their own.
- Pick the capture point (week 1). Choose the one artifact you will extract from first. For most teams it is call transcripts, because they carry objections, competitors, and buyer language in one place.
- Define the extraction schema (week 2). Decide what gets pulled from each call: objection, competitor mentioned, pain point (verbatim), outcome, segment. Keep it to five or six fields. A schema nobody fills in is worse than no schema.
- Backfill from the last quarter (weeks 2–3). Run the extraction over the previous 90 days of calls. This is the pattern library the new rep inherits on day one. Without backfill, the system only helps the hire after next.
- Build the four structured views (week 3). Objections ranked, competitor profiles, pain points by segment, account summaries. These are the onboarding curriculum.
- Rewrite the ramp plan around them (week 4). Replace "shadow 15 calls" with "review the top 10 objections and the working responses, then shadow 5 calls and identify which objections came up." The rep is now checking their inherited knowledge against reality rather than building it from scratch.
- Measure at 30, 60, and 90 days. Track call-prep time, first-meeting-to-opportunity conversion, and time to first closed deal. Compare against the last three hires.
Ramp checklist: 30, 60, 90
Use this as the skeleton for the new plan. Each item is something the rep can demonstrate, not something they attended.
By day 30
- [ ] Can list the top 10 objections and the working response to each, with an example call
- [ ] Can position against each named competitor in under two minutes, including where we lose
- [ ] Has reviewed the account summaries for every inherited account with activity in the last 90 days
- [ ] Preps for a discovery call in under 10 minutes using the structured views
By day 60
- [ ] Has run 20 discovery calls; at least 15 of the objections raised were already in the library
- [ ] Has contributed at least 3 new extractions (an objection, a competitor mention, a pain point) back to the library
- [ ] Preps for a call in under 5 minutes
By day 90
- [ ] First closed-won deal, or pipeline coverage at team median
- [ ] Win rate on competitive deals within 10 points of team average
- [ ] Ramp retrospective completed: which knowledge was missing from the library, and has it been added
The 60-day contribution item matters more than it looks. The moment a new rep adds to the library, the system has stopped being onboarding material and started being how the team works. The next hire inherits what this one learned.
What to expect
Teams that run this framework report the same shape of result: the product-knowledge portion of ramp is unchanged (it was never the bottleneck), and the market-knowledge portion collapses because the rep is reviewing a structured library instead of reconstructing one. Three to six months becomes six to twelve weeks for the categories that used to depend on osmosis.
The second-order effect is on turnover. When the pattern library belongs to the company rather than to the individual, a departure is a staffing problem instead of a knowledge-loss event.
This is also the problem TurnkeyGTM is built around. Every call transcript and document a team uploads is extracted into structured knowledge (objections, competitors, pain points, account context) and made retrievable in chat, with citations back to the source call. A new rep asks the question a veteran would answer and gets the team's accumulated answer, on day one. If you want to see what your last quarter of calls would produce, join the waitlist.
Related
- Guide: How to build competitive battle cards
- Template: Competitive battle card
- Directory: Call intelligence tools · AI sales tools
- Glossary: AI sales call analysis · Sales velocity