sales-ramp-enablement
Skill58 starsChanged 38 days agoMITView on GitHub
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 a 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 hiring plan that treats the months between start date and full production as weather. BOUNDARY: assumes a playbook exists or names its absence as the first gap. Call scoring feeds certification evidence. gtm-compensation owns full comp design; this skill sets only ramp-period quota and draw. revops-org-chart owns hiring sequencing; the capacity math here feeds it.
In this repository44 other files it gives its agents.
- abm-engagement-scoringSkill
- closed-lost-revivalSkill
- comp-plan-architectureSkill
- crm-migration-consolidationSkill
- cs-operationsSkill
- data-enrichmentSkill
- deal-desk-operationsSkill
- deal-qualification-gatesSkill
- deal-velocity-engineerSkill
- expansion-revenue-architectSkill
- gtm-compensationSkill
- gtm-data-architectureSkill
- gtm-planningSkill
- icp-builderSkill
- lead-routingSkill
- marketing-operationsSkill
- onboarding-activationSkill
- operating-cadence-designerSkill
- partner-channel-operationsSkill
- partner-ecosystem-architectSkill
- pipeline-visibilitySkill
- positioning-messaging-designerSkill
- pricing-monetization-opsSkill
- procurement-navigationSkill
- qbr-ebr-builderSkill
- renewal-save-motionSkill
- revenue-operating-cadenceSkill
- revops-change-managementSkill
- revops-crisisSkill
- revops-data-governanceSkill
- revops-diagnosticSkill
- revops-forecastingSkill
- revops-handoffsSkill
- revops-hubspotSkill
- revops-metricsSkill
- revops-org-chartSkill
- revops-revenue-planningSkill
- revops-salesforceSkill
- revops-strategySkill
- revops-tech-stackSkill
- saas-pnl-readingSkill
- sales-methodologySkill
- trial-poc-conversionSkill
- win-loss-programSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Before designing content, put ramp into the revenue model, because that is what makes the program a CFO conversation instead of an HR one:
- Distinctive: line 33
Default arc for a mid-market AE.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

