-
1
Pick a cohort size of 3 to 6 reps and set a 2-week start window
A cohort below three reps loses the peer-learning advantage and starts to feel like three parallel solo ramps on the same calendar. A cohort above six reps overwhelms the Enablement owner, waters down each rep's airtime in group sessions, and makes the certification scoring inconsistent because the scorers get fatigued by the back half. The sweet spot is 4 to 5 reps, with 3 and 6 as the edges. Set a 2-week start window so every rep in the cohort begins inside the same fortnight, which keeps the week-by-week agenda honest and lets the group hit each certification gate together instead of trailing by days.
- Target 4 to 5 reps per cohort; accept 3 on the low end and 6 on the high end, never more.
- Set a hard 2-week start window and align start dates to the Monday of week one so the agenda tracks cleanly.
- If hiring slips a candidate past the window, hold them for the next cohort rather than bolting them onto a running one.
- Publish the cohort name (Cohort 2026-Q4 Blue, for example) on day one so the group has shared identity from the first standup.
Tip: If the hiring pipeline cannot reliably land 3 reps in a 2-week window every quarter, run cohorts every other quarter instead of every quarter. A late, half-full cohort is worse than a well-timed cohort that lands two months later.
-
2
Write a 4-week agenda that every cohort runs identically
A cohort stops being a cohort the moment one rep gets a different week two than another. Write a single 4-week agenda with a theme per week, a daily block structure, and the same session order every cohort runs. Week one covers product, ICP, and the sales motion. Week two is call shadowing paired with role plays scored on the live-call rubric. Week three is supervised live calls on real but low-stakes pipeline. Week four is a graduation certification plus a cohort-wide ramp retro that feeds back into the agenda for the next cohort. Freeze the agenda at the start of each quarter and ship any changes to the next cohort rather than editing mid-flight on the group currently running.
- Week 1: product knowledge, ICP study, playbook read-through, written product test on day 5.
- Week 2: 10 shadowed live calls across stages, 2 scored mock discovery role plays, 1 scored mock demo.
- Week 3: 5 supervised live calls per rep, Enablement on mute, with same-day debrief in the cohort room.
- Week 4: graduation certification (live demo plus mock negotiation scored by two assessors), cohort retro, written ramp commitments for days 30 to 90.
Tip: Keep the daily blocks the same shape across weeks (morning content, midday live reps, afternoon group debrief). Reps retain more when the rhythm is predictable and they can plan around their own prep time.
-
3
Set up a cohort channel, a shared doc, and a Strkr workspace
Peer learning only compounds if the cohort has a shared place to show their work. Spin up a dedicated Slack or Teams channel, a shared cohort doc for notes and pattern libraries, and a Strkr workspace with a cohort-tagged pipeline so every rep can see the same practice deals as they move through the stages. Pin the agenda, the playbook, the certification rubric, and the ramp dashboard to the top of the channel on day one. Require every rep to post a short pattern note after each shadowed call, so by the end of week two the cohort has 50-plus observed moments to study together instead of each rep remembering 10 in isolation.
- Create a cohort channel on day one and pin the agenda, playbook, rubric, and ramp dashboard links at the top.
- Open a shared cohort doc with a section per week and a running pattern library the reps co-author as they shadow calls.
- Spin up a Strkr workspace with a cohort tag applied to every practice deal, so the pipeline view is scoped to the cohort.
- Require a 3-line pattern note in the channel after every shadowed call, co-signed by the rep who ran it where possible.
Tip: Delete the cohort channel 90 days after graduation on purpose. The channel is a learning tool, not a long-term support group, and letting it linger pulls the ramped reps back into cohort dynamics instead of integrating into the full team.
-
4
Run group certifications where cohort members assess each other
Group certification is the single highest-leverage cohort move. Instead of each rep delivering a mock demo one-on-one with the manager, pair cohort members to run mock calls on each other, score each other on the live-call rubric, and defend the score in front of the full group. The reps on the receiving end learn how a sharp buyer thinks because they just played one. The reps on the delivering end get feedback from four peers plus the Enablement scorer instead of one manager voice. The scoring stays honest because the rubric is written down, two assessors sign every score, and borderline passes get retried the next day instead of waved through.
- Pair cohort reps for mock discovery in week 2 and mock demo in weeks 3 and 4; rotate pairs so no rep works with the same partner twice.
- Score every mock on the same written rubric used for live calls, with two assessors (one peer, one Enablement) co-signing the score.
- Treat a certification miss as a next-day retry, not a cohort exit; graduate only when the rep clears two consecutive at-or-above-average scores.
- Record every mock certification and post it to the cohort doc so the next cohort can study prior passes and prior misses.
Tip: If two assessors disagree by more than one point on any rubric dimension, the rubric wording is too loose. Fix the rubric in the quarterly retro, not inside the current cohort, so the scoring stays stable for the group running right now.
-
5
Pair the cohort with tenured reps for shared ride-alongs
Shared ride-alongs are the cohort's secret weapon over solo onboarding. Instead of one new rep shadowing one tenured rep in isolation, send 2 or 3 cohort members on the same live call together and run a 15-minute group debrief inside the cohort channel immediately after. Every rep hears three different reads on the same call, the Enablement owner spots the moments the whole cohort missed, and the tenured rep answers one question that benefits three new reps instead of answering the same question three times across three solo ramps. Target 10 shared ride-alongs per rep across weeks two and three, with the ride-along mix weighted toward discovery and demo rather than negotiation.
- Schedule 10 ride-alongs per rep across weeks 2 and 3, with 2 or 3 cohort members on each live call.
- Weight the mix 5 discovery, 3 demo, 2 negotiation so the cohort studies the stages that drive early pipeline-gen first.
- Run a 15-minute group debrief in the cohort channel inside the hour after the call, with a written takeaway per rep.
- Rotate which tenured reps host so the cohort hears multiple styles rather than copying one voice.
Tip: Give tenured reps a $25 to $50 recognition in the team channel for every 5 ride-alongs they host, scoped to each cohort. The recognition keeps hosting from feeling like unpaid work on top of their quota.
-
6
Measure ramp velocity against a solo baseline, not just at day 90
A cohort program only earns its keep if the cohort hits certification and first-deal milestones faster than the trailing solo baseline. Build a cohort ramp dashboard in Strkr that tracks each milestone (product test pass, mock discovery pass, mock demo pass, first live call, first qualified opp, first demo, first closed deal) against the planned day it should land, and overlay the trailing three solo new-hire curves as the baseline. Review the dashboard with the sales leader every Friday during the 4 weeks and at every post-graduation 1:1 for the first 90 days. The ramp velocity gap is the number you defend the cohort program with, and it is also the signal that the agenda needs to change before the next cohort runs.
- Chart every milestone's planned day vs actual day on a shared cohort ramp dashboard, scoped by cohort tag in Strkr.
- Overlay the trailing three solo-onboarded reps as a baseline curve so the cohort gap is visible at a glance.
- Pair milestone progress with weekly rubric scores so skill lift and pipeline math get read together, not in isolation.
- Review the dashboard with the sales leader every Friday during the 4 weeks, and at every post-graduation 1:1 through day 90.
Tip: If the cohort ramp curve does not beat the solo baseline by at least 15 percent on first qualified opp by day 60, the agenda is wrong, not the reps. Rewrite the weak week before the next cohort starts; do not run the same program twice and hope.
-
7
Run a cohort retro before graduation and feed it into the next cohort
A 4-week cohort generates more learning signal in a month than most sales teams get out of six months of solo ramps, and almost all of it evaporates if there is no formal retro. On the morning of graduation day, run a 60-minute cohort retro with the full cohort, the Enablement owner, and the sales leader. Walk the ramp dashboard, read the pattern library the cohort co-authored, and ask the group three questions: which part of the agenda most moved the needle, which part felt like busywork, and which part they wish had come 2 weeks earlier or later. Capture the answers in the quarterly agenda changelog so the next cohort inherits an upgraded program, not a copy of the last one.
- Book a 60-minute cohort retro on graduation morning with the full cohort, Enablement, and the sales leader present.
- Open with the ramp dashboard and the pattern library so the retro starts on evidence, not opinion.
- Ask the three agenda questions, capture answers verbatim, and tag them to the specific day or session they reference.
- Publish the retro notes and the agenda changelog to the cohort doc inside 48 hours so the next Enablement planning cycle inherits them.
Tip: Invite one tenured rep who hosted ride-alongs to the retro as an outside observer. Their read on how prepared the cohort felt in the field is the strongest signal of whether the program is actually working outside the classroom.
-
8
Hand the cohort off to the sales manager with written ramp commitments
A cohort graduates on day 28, but the first closed deal is still 60 days out for most reps. Close the loop by writing a day 30 to 90 ramp commitment per rep on graduation day, co-signed by the rep, the sales manager, and the Enablement owner. The commitment carries forward the same milestones from the 30/60/90 plan the team already runs (first qualified opp, first solo demo, pipeline-gen target, first closed deal) and the same scoring rubric so the manager picks up the handoff without renegotiating standards. The Enablement owner stays on each rep's weekly 1:1 as a silent observer for the first four post-graduation weeks, so if the handoff drifts the signal shows up early instead of surfacing as a missed quarter.
- Write a day 30 to 90 ramp commitment per rep on graduation day, co-signed by the rep, the manager, and Enablement.
- Carry forward the same milestones and the same rubric from the team's existing 30/60/90 plan to keep the standard stable.
- Keep Enablement on each rep's weekly 1:1 as a silent observer for 4 post-graduation weeks, then step out cleanly.
- Track cohort-level graduation-to-first-closed-deal time as a program KPI, not just an individual rep stat.
Tip: If the manager and Enablement cannot agree on a rubric score inside the first post-graduation month, the handoff is already breaking. Fix the alignment in the next quarterly retro, not inside a 1:1 with the ramping rep in the room.
