Agent skill
sales-ramp-enablement
Design rep ramp as an instrumented system: milestone-gated 30-60-90 with certification evidence, ramp math wired into capacity and forecast, ramp- adjusted quota and comp, and the manager cadence that catches a drifting ramp in week three instead of month five.
Filed under Team and enablement.
From NEON-Rutger/B2B-revops-skills · 45 skills · 48 · pushed 2026-09-09
What it does when it runs
Design rep ramp as an instrumented system: milestone-gated 30-60-90 with certification evidence, ramp math wired into capacity and forecast, ramp- adjusted quota and comp, and the manager cadence that catches a drifting ramp in week three instead of month five. Triggers on 'ramp,' 'ramp time,' 'new rep onboarding,' 'time to productivity,' 'reps take too long to produce,' 'certification,' 'enablement program,' 'sales onboarding plan,' '30-60-90 for the new AE,' 'ramp quota,' or any situation where hiring is planned but the months between start date and full production are treated as weather instead of a system. BOUNDARY: a playbook-foundations skill owns the playbook document itself (what good looks like, written down); this skill assumes a playbook exists or names its absence as the first gap, and builds the SYSTEM that installs it into a new rep on a clock. Call-scoring skills own per-call quality scoring; this skill consumes those scores as certification evidence. gtm-compensation owns full comp design; this skill specifies only the ramp-period quota and draw logic. revops-org-chart owns hiring sequencing; capacity math here feeds it.
Read from the skill and the 1 file bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- neontriforce.com
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/NEON-Rutger/B2B-revops-skills.git /tmp/B2B-revops-skills git -C /tmp/B2B-revops-skills sparse-checkout set "sales-ramp-enablement" mkdir -p ~/.claude/skills/sales-ramp-enablement cp -R "/tmp/B2B-revops-skills/sales-ramp-enablement/." ~/.claude/skills/sales-ramp-enablement/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from NEON-Rutger/B2B-revops-skills/blob/d3d3dd967ffc7da0f2e9282ab124d51357160d69/sales-ramp-enablement/SKILL.md, which is licensed MIT (repository). 962 words, 7 headings.
Sales Ramp and Enablement: Productivity by Design, Not by Osmosis
Ramp is the most expensive unmanaged period in a GTM budget. SDRs average around 3.1 months to productivity, from the one surveyed-methodology source in this space (The Bridge Group SDR Metrics, 2023). AE figures are softer: 2025-2026 industry compilations, published without unified methodology, put average AE ramp toward 5-6 months with enterprise motions far longer; trust the segmentation shape and the lengthening trend, not the exact numbers. Multiply the months by loaded cost and missed quota coverage and a single slow ramp costs more than the enablement program that would have prevented it. Yet most companies run ramp as scheduled exposure: a training week, a shadowing rotation, a quota that switches on at a date the calendar picked.
The core rule: ramp is graduated by evidence, not elapsed time. Every element below either defines the evidence or wires the consequences.
Ramp Math First
Before designing content, put ramp into the revenue model, because that is what makes the program a CFO conversation instead of an HR one:
- Ramp cost per hire = months to full productivity x (loaded cost + quota coverage gap). Compute it for your last four hires; this number funds everything else in this skill.
- Capacity planning uses ramped-equivalent reps, not headcount: a rep in month two of a five-month ramp is 0.4 of a rep in the coverage model. Annual plans that count heads instead of ramped-equivalents manufacture a pipeline gap and then blame the market (feed this into the bottoms-up capacity model in revops-forecasting).
- Ramp-adjusted quota: stepped targets over the ramp arc with a draw or guarantee matched to the steps. A full quota on day one does not accelerate learning; it teaches new reps to chase bad deals, which your qualification gates then have to catch.
The Milestone Arc: Evidence-Gated 30-60-90
Default arc for a mid-market AE; compress or stretch by motion, keep the gate logic:
- By 30, certified on the story: can run the first-call pitch and discovery to standard, scored against your call-scoring rubric on real or roleplay calls, not self-assessed. Knows the ICP, the top loss causes (pull them from the win-loss program, not folklore), and the qualification bar.
- By 60, certified on the motion: running discovery on live at-bats with a manager or peer listening; first qualified opportunities created that survive the evidence gates. Leading indicators tracked from week one: time to first meeting booked, time to first qualified opportunity, activity quality scores.
- By 90, producing with fading scaffold: owns deals through mid-funnel, first closed or near-closed outcome appropriate to cycle length, and the scaffold (shadowing, call reviews on every call) steps down on evidence.
- Every gate has three outcomes: pass, targeted remediation with a named gap and a re-test date, or an honest early verdict. The most expensive ramp outcome is the rep who was never going to work, discovered at month nine; milestone gates exist to move that discovery to month two.
The structured-versus-unstructured gap is the one finding every source agrees on: teams with formal, milestone-based onboarding ramp materially faster than sink-or-swim (The Bridge Group, 2023; consistent across 2025-2026 aggregations). The exact multiplier varies by source; the direction never does.
Enablement as a System, Not a Binder
- One home: playbook, call library, and assets live in a single place with an owner and an update cadence. If the playbook does not exist, that is gap zero; build it before designing week two (see the playbook-foundations boundary).
- The call library is the curriculum: best-in-class recordings per stage, worst-call examples with commentary, and the new rep's own calls reviewed against them. Reps learn the standard from real calls, not slides.
- Certification content comes from reality: the pitch to certify is the one your best calls actually run; the objections to drill are last quarter's top loss causes; the ICP to memorize is the scored one, not the aspirational one.
- Measure enablement by ramp outcomes, not attendance: content completion is an input; time-to-first-qualified-opportunity by cohort is the scoreboard.
The Manager Cadence
Ramp fails silently without a manager rhythm: weekly 1:1 against the milestone plan (evidence reviewed, not feelings), two call reviews per week minimum through day 60, and a written monthly verdict (on track, remediation, or concern) that someone above the manager reads. A ramp plan without a manager cadence is a wish with milestones.
What Good Looks Like
The best ramp systems can show, for every cohort, the leading-indicator curve (first meeting, first qualified opp, first win) against the previous cohorts', and their certification gates have actually failed someone, kindly and early. The common failure is the celebratory version: full training week, a certificate for attending it, quota live in month two, and a "ramp problem" diagnosed in month six that was visible in the week-three indicators nobody was watching. You know it works when a hiring plan conversation quotes ramped-equivalent capacity by month, and when a struggling new rep's gap can be named from gate evidence instead of vibes.
Diagnostic Questions
- What did your last four hires cost in ramp months x loaded cost, and who owns shrinking that number?
- Does your capacity model count heads or ramped-equivalents? Recompute this year's plan with ramp curves and see if the pipeline target still holds.
- What evidence graduates a rep from ramp today: a date, or scored certifications? Has a gate ever failed anyone?
- What is your time-to-first-qualified-opportunity by hire cohort, and is it improving?
- Where does a new rep go to hear what a great discovery call sounds like, and how old is the newest example there?
Provenance and practice-based rules: read references/ramp-benchmarks.md.
Built by Neon Triforce
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- sales-enablement by coreyhaines31 · 49,731
- sales-enablement-tools by louisblythe · 151
- sales-enablement by shalintripathi · 12
- sales-enablement by 0xF4ng · 5
- sales-pipeline by ericosiu · 3,522
- sales-playbook by ericosiu · 3,522
- sales by zubair-trabzada · 1,196
- sales-competitors by zubair-trabzada · 1,196
Need help setting it up?
This page tells you what sales-ramp-enablement does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.