The 30-60-90 Ramp Plan When New Reps Work Alongside Agents
Ramp plans built for a world of scarce information break when research, drafting and summarising are free. Here is a rebuilt 30-60-90 with competency gates, supervision skills, and the two things that must not be automated in week one.
Jonathan Kvarfordt · Published September 7, 2026 · 12 min read
The short answer
How should a new rep ramp plan change when agents do the prep work?
Decision rule
Do not let a new rep use an agent for a task before they have done that task manually enough times to spot when the output is wrong.
Operator action
Rebuild your ramp around the six competency gates below, each with an observable pass test.
Supporting pages
- Adoption is real, measurable, and slower than the discourse the data behind this piece
- The Single-Player AI Problem definition
- The Proof Gap definition
Last reviewed
The classic ramp plan is an information transfer schedule. Week one product, week two competitors, week three process, week four shadowing. It exists because information used to be scarce and slow to acquire.
That constraint is gone. A new rep can now produce an account brief in ninety seconds that would have taken a senior rep an afternoon in 2022. If the ramp plan does not change, you are spending thirty days teaching something the tooling already delivers, and skipping the thing that now decides performance: judgement about machine output.
The argument
How this playbook breaks down
A map of the sections ahead, in the order the case is made. Schematic, not a dataset. Source-cited charts live in the research library.
Contents diagram for The 30-60-90 Ramp Plan When New Reps Work Alongside Agents, listing the sections: What ramp is actually gating on now, Days 1 to 30: manual first, deliberately, Days 31 to 60: supervised leverage, Days 61 to 90: unsupervised, with limits, What enablement stops doing, Measuring the ramp itself.What ramp is actually gating on now
Three capabilities separate a productive new rep from a fast-typing one.
- Discrimination. Can they tell a good machine output from a plausible wrong one. This is the editor's skill, and it is learned by doing the work manually first. The reasoning is in the editor's mind.
- Qualification judgement. Can they hold a disqualification decision under pressure from a manager who wants pipeline coverage.
- Commercial construction. Can they build a deal shape, not just a proposal, including the multi-threading and the internal path to signature.
30-60-90
Ramp gates on judgement, not on information
- 01
Days 1 to 14: manual calibration
Brief, summarise and qualify by hand
- 02
Gate: finds a real error in machine output
Discrimination proved
- 03
Days 15 to 60: supervised leverage
Edits reviewed, not drafts
- 04
Gate: intervention rate falling, quality holding
Judgement proved
- 05
Days 61 to 90: limited autonomy
Own book, gated irreversible actions
- 06
Gate: accurate forecast call and one post-mortem
Commercial judgement proved
Each gate is an observable test, not a completed module. Schematic, not a dataset. Source-cited charts live in the research library.
Ramp gates on judgement, not on information. Diagram showing Days 1 to 14: manual calibration, Gate: finds a real error in machine output, Days 15 to 60: supervised leverage, Gate: intervention rate falling, quality holding, Days 61 to 90: limited autonomy, Gate: accurate forecast call and one post-mortem.None of these are content problems. All three are practice problems, which means ramp becomes a rehearsal schedule rather than a curriculum.
Days 1 to 30: manual first, deliberately
The counterintuitive move is to withhold the agent for the first two weeks on the tasks the rep must be able to judge later. Not as hazing. As calibration.
- Write five account briefs by hand. Then read five machine-generated ones and mark the errors. The gap between the two is the lesson.
- Listen to ten recorded calls and write the summary yourself before comparing to the automated summary.
- Learn the qualification criteria as a decision, not a form. Practise disqualifying out loud.
- Learn the systems, the stage definitions and what each field means, because those definitions are now production dependencies rather than reporting preferences.
Gate one: the rep can find at least one material error in a machine-generated account brief, unprompted.
Gate two: the rep can state, in one sentence per criterion, why a named prospect is not qualified.
Days 31 to 60: supervised leverage
Now switch the tooling on and change the measure. The rep is no longer judged on output volume, which is now trivially high. They are judged on the intervention rate and the quality of what shipped.
- Every machine-drafted message is edited before send, and the edit is logged. Managers review the edits, not the drafts.
- Live call practice against the three objections that lose the most deals in your data, not the three that are easiest to script.
- First multi-threading exercise: name every person required for a decision in a real open deal, and the path to each.
- Weekly deal review where the rep presents evidence, not narrative. This is the same standard applied to vendors in the pipeline truth test.
Gate three: intervention rate is falling and shipped quality is holding, measured by manager review of a random sample.
Gate four: the rep has run one full discovery call end to end with a scoring sheet completed by an observer.
Days 61 to 90: unsupervised, with limits
Full tooling, own pipeline, defined limits. Discounting, contract language and anything irreversible still require a gate, exactly as they do for agents. The reversibility test applies to humans in ramp too.
- Own a defined territory or book with a named coach, not a shared one.
- Deliver one internal teach-back on a competitor or a segment. Teaching is the fastest test of understanding.
- Complete a pipeline review with a forecast call, and be scored on the accuracy of that call two weeks later.
Gate five: a forecast call that proved accurate within an agreed tolerance.
Gate six: one closed-won or closed-lost deal with a written post-mortem the team can reuse.
What enablement stops doing
Two categories of enablement work lose their value in this model. Static content libraries, because retrieval at the moment of need beats memorisation, and certification quizzes that test recall of information now available instantly. Replace both with delivery at the point of work and observed competency tests. The delivery model is in just-in-time enablement with AI, and the wider role change is in enablement in the age of agents.
Measuring the ramp itself
Track four numbers and compare cohorts, not individuals: days to first qualified opportunity, days to first closed deal, intervention rate at day sixty, and forecast-call accuracy at day ninety. If the tooling is working, the first two fall and the last two improve. If only the first two fall, you have built a faster path to bad pipeline.
Related: Just-in-time enablement · The editor's mind · Systems beat talent · Skill: building onboarding ramp plans
Take it to the room
The short list this issue leaves you with
Pulled from the argument above, written so you can read it out in a pipeline or board review. Schematic, not a dataset.
Checklist diagram summarising The 30-60-90 Ramp Plan When New Reps Work Alongside Agents: Own a defined territory or book with a named coach,…; Deliver one internal teach-back on a competitor or…; Complete a pipeline review with a forecast call, an….Frequently asked questions
- Should new reps use AI tools from day one?
- Not on the tasks they must later judge. Two weeks of manual work on briefs, summaries and qualification builds the discrimination needed to catch plausible but wrong machine output.
- Does agent support shorten ramp?
- It shortens time to first qualified opportunity because prep stops being the bottleneck. It does not shorten time to sound judgement, which is why the gates must test judgement rather than throughput.
- What should managers review during ramp?
- The edits, not the drafts. Reviewing what a rep changed in machine output shows their judgement far faster than reviewing what they shipped.
- What are the ramp metrics?
- Days to first qualified opportunity, days to first closed deal, intervention rate at day sixty, and forecast-call accuracy at day ninety, compared across cohorts.
- What must never be automated in ramp?
- Disqualification decisions, discounting, contract language, and any irreversible action. Those follow the same reversibility rule applied to production agents.
- Does this apply to customer success and support hires?
- Yes. The structure holds: manual calibration first, supervised leverage second, limited autonomy third, with gates that test judgement rather than recall.
Subscribe
Get the next operator playbook in your inbox.
Keep reading
Playbook
The Reversal Ledger: Counting the AI Decisions Your Team Had to Undo
Every revenue org tracks what AI did. Almost none track what humans had to reverse. That second number is the one that tells you whether your agents are earning trust or borrowing it.
Playbook
Renewal and Expansion Planning When Agents Watch the Account
Risk detection can be automated. The renewal conversation cannot. Here is the split, the four signal classes worth acting on, and a 120-day renewal plan that says exactly which steps a machine owns.
