How do you design kickoff content for AEs vs. SDRs vs. managers in 2027?

A 150-person kickoff that taught two-thirds of the room the wrong thing

Picture a mid-market B2B software company heading into January with 80 AEs, 50 SDRs, and 20 front-line managers. The enablement team books a hotel ballroom for three days, lines up a CRO keynote, a product roadmap session, a comp-plan reveal, a customer story, a methodology partner's main-stage talk, and an awards dinner. On paper it looks like a strong agenda. Every session is well-produced. The keynote lands. The awards dinner is genuinely moving. And ninety days later, nothing measurable has changed.

The reason is visible if you walk the room during the methodology session on day two. The content is a deal-qualification framework — economic buyer, decision criteria, decision process, champion, competition. For the 80 AEs, this is exactly right; it is the core of their job. For the 50 SDRs, it is theater. An SDR does not run a decision-process conversation with a CFO; an SDR books the first meeting and hands off. They are sitting through ninety minutes of content about a stage of the funnel they will not touch for another eighteen months, if they get promoted. And for the 20 managers, it is subtly wrong in a different way — they already know the framework, in most cases better than the reps do. What they need is not to *run* the framework but to *coach eight people who run it*, and to pressure-test a forecast built on it. That is a different skill and nobody is teaching it.

Run that arithmetic across a full agenda and the picture gets uncomfortable. If you audit each session and ask "which of the three roles is this genuinely core for," a typical single-track kickoff comes out with the majority of its content core for exactly one cohort. The AE majority does fine, because main-stage content in a sales org defaults to being pitched at closers. The SDR and manager minorities absorb almost all of the waste. They spend three days learning that the company invests in AEs and tolerates everyone else — which is a message nobody intended to send and everybody received.

The cost side sharpens it. Fully loaded per-attendee kickoff cost — flights, hotel, food, event production, and the value of three to five days out of seat — typically runs in the low thousands of dollars per person at a mid-market company and considerably higher at enterprise scale. For a 150-person event that is a several-hundred-thousand-dollar line item before you count methodology partners, LMS configuration, or the content-design effort itself. Three to five days out of the field is roughly one and a half to two and a half percent of a rep's productive selling year. When a meaningful fraction of that spend produces no behavior change in a role because the content did not match the job, the waste is not theoretical — it is one of the largest controllable, repeating line items in the go-to-market budget, and it recurs every single year until someone redesigns the agenda.

The fix is not a bigger budget or a better keynote speaker. It is architecture. Three roles with three different jobs, three different time horizons, and three different failure modes need three different curricula wrapped inside one shared narrative. That is the whole thesis, and everything below is the mechanics of executing it.

Why the three jobs are structurally orthogonal

The case for splitting the content is not a preference about variety. It rests on the observation that these three roles are measured on different clocks, work in different units, and fail in different ways.

Time horizon. An SDR lives on a weekly and monthly cadence — meetings booked this week, qualified opportunities created this month. An AE lives on a quarterly cadence — bookings closed in the quarter, pipeline built for the next one. A manager lives on a quarterly and annual cadence — team attainment, forecast accuracy across a whole book, and retention of the people on the roster. Content designed for a weekly operator lands differently than content designed for someone whose scoreboard resets four times a year.

Unit of work. The SDR's unit is a sequence and a live conversation. The AE's unit is a multi-stakeholder opportunity that lives for weeks or months. The manager's unit is a coached rep. You cannot teach all three with the same exercise, because the object being manipulated is not the same object.

Primary failure mode. An SDR fails through a thin or badly targeted top of funnel. An AE fails through a stalled, single-threaded deal that dies in procurement or to a competitor. A manager fails through an inaccurate forecast or an under-coached, churning team. Curriculum should be designed backward from the failure mode you are trying to prevent, and these three failure modes have almost nothing in common.

Seniority and authority. This one is routinely ignored. An SDR is typically in the first twelve to twenty-four months of a sales career and needs confidence, scripted repetition, and tool fluency. An AE is a seasoned closer who needs sharper frameworks and competitive edge, not fundamentals. A manager has stepped off the individual-contributor track entirely and — in most B2B software organizations — was promoted for being a strong AE without ever receiving formal management training. Compress a first-year SDR, a ten-year enterprise AE, and a six-month-old front-line manager into the same room with the same content and the content is wrong for at least two of them by construction.

There is a specific consequence worth naming: pricing content in the SDR track is a tell. SDRs are generally not authorized to negotiate. Putting discount-defense drills in front of them does not just waste ninety minutes; it broadcasts that whoever built the agenda does not understand what an SDR does all day. The reverse tell exists too — putting coaching-cadence frameworks in front of individual contributors, or MEDDICC role-play in front of managers who need to learn how to *inspect* MEDDICC rather than perform it.

The same orthogonality logic keeps applying as you scale, which is why stratification is fractal. A 200-AE organization running both a $250K-ACV enterprise motion and a $25K-ACV mid-market motion has two AE jobs, not one, and eventually needs enterprise and mid-market sub-tracks for the same reason it needed to separate AEs from SDRs. Once sales engineers, solution architects, partner-channel sellers, or customer success managers attend, the question is not whether they need their own content but whether each cohort is large enough to amortize the cost of building it. The test is always the same: do the jobs genuinely diverge, and is the cohort big enough to pay for its own track?

How the architecture actually works

The mechanism has three layers: a shared spine, three parallel tracks, and deliberate re-mixing.

The shared spine — 40-50% of agenda time. This is content that genuinely serves everyone: the CRO's fiscal-year narrative, the company all-hands moment, President's Club recognition, the high-level product roadmap, and a customer keynote. This content exists to build shared identity and shared context. It is the reason you flew everyone to one place instead of sending a video. Do not cut it — but audit it ruthlessly.

The audit tool is a role-coverage map: a single page listing every session on the agenda with three columns, one per role, each marked core / useful / skippable. Any main-stage session that is skippable for an entire cohort does not belong on the main stage. It belongs in a breakout or in an LMS module. A comp-plan deep dive is the classic offender — riveting for AEs whose plan just changed, structurally irrelevant for SDRs whose comp works completely differently. Build the map, and if any role has more "skippable" rows than "core" rows, the agenda is failing that role and needs rebalancing before content production starts. RevOps is usually the right owner for this artifact, because RevOps has the cross-org view and no incentive to favor one cohort over another.

The three tracks — 50-60% of agenda time. This is where the split earns its return, and it is where the practice happens. A crucial constraint: breakout blocks must be long enough to practice, not merely to listen. A forty-five-minute breakout is a lecture with a different room number. Two to three hours is enough for instruction, role-play, and debrief — and skill transfer lives in the role-play and the debrief, not the instruction. Protect practice time as fiercely as you protect keynote time.

The re-mixing layer. Stratification's genuine risk is that three well-designed tracks produce three tribes who do not trust each other. The antidote is scheduled, not improvised.

Day sequencing. A three-day event usually works as a sandwich. Day one is main stage: fiscal-year narrative, comp overview, roadmap, customer voice. Day two is breakouts plus the cross-role pairing block. Day three is a final breakout block with certification or role-play assessment, closing on the main stage with recognition and send-off. The order is deliberate — building the shared narrative first means that when reps walk into breakouts on day two, the skill content lands inside a frame they already understand. Open with breakouts and the drills feel disconnected from where the company is going. Close on the main stage and every cohort goes home on the same note, which protects the social fabric the split otherwise risks fraying.

Ownership is the load-bearing decision. Every track needs one named owner, not a committee. The AE track goes to the VP Sales or a regional leader who owns AE quota and lives in deal mechanics. The SDR track goes to the VP Sales Development who owns pipeline generation. The manager track goes to the VP Enablement or a CRO chief of staff — deliberately *not* the VP Sales, because placing it under sales leadership is how it quietly becomes an extension of the AE track. Committee-owned tracks reliably become unowned tracks.

Ownership means four concrete deliverables, not a name on a slide: the breakout agenda with learning objectives, the instructor and partner roster, the role-specific pre-work and post-event reinforcement plan, and the scorecard the track will be measured against at thirty, sixty, and ninety days. The honest test of ownership is whether, ninety days out, the owner can show data on whether their track moved its metric. Most organizations that claim to have track owners cannot, because ownership was assigned for the event and not for the outcome.

What goes in each track

The AE track should run roughly two-thirds practice, one-third instruction. Core modules: live deal review against a qualification framework; discovery and value articulation drilled in role-play; negotiation and discount defense; competitive displacement against named competitors; win-loss teardowns of the year's biggest wins and most painful losses; and short, tactical shares from top performers.

The single highest-value session is usually the live deal review, because it is where methodology stops being abstract. The format that works: every AE brings one real, in-flight opportunity. Groups of six to eight scrub it against the qualification framework with a facilitator and a manager in the room. The AE leaves with a concrete next-action list and a clear read on which qualification gap is most likely to kill the deal. This does double duty — it teaches the framework and it advances real pipeline, which is the cleanest possible answer when finance asks whether the event produced return.

Competitive content should be specific to the point of discomfort. An AE does not need to know a competitor exists. They need the three objections that competitor's reps raise in a live deal and the exact reframe that wins. That specificity is the difference between a battlecard that gets used and one that sits in a content library. Similarly, top-AE shares work when they are narrow and tactical — "here is the exact discovery question that surfaces the economic buyer" — not motivational. Motivation belongs on the main stage; the breakout is for transferable mechanics.

The SDR track covers outbound craft and messaging, ICP and persona refinement grounded in the year's actual closed-won and closed-lost data, multi-touch sequence design in whichever engagement platform the team runs, script rebuilding from real winning and losing call recordings pulled out of conversation intelligence, prospecting-tool fluency, and live supervised dialing. The SDR track is the one place on the entire agenda where live cold calls belong.

It has a design requirement the other two do not: it must build confidence as deliberately as it builds skill. The SDR job is emotionally punishing — high rejection volume, low individual control over outcomes, and a daily grind that burns reps out faster than any other seat in the org. A purely tactical SDR track, all mechanics and tool clicks, misses half the point. Pair the craft content with explicit reframing of rejection, visible career-path content — what the promotion to AE actually requires and roughly how long it takes — and shares from SDRs who recently earned it. That career-path content is also a retention lever, since a large share of first-year SDR attrition comes from reps who cannot see a future.

The SDR track is also where AI is most live. AI-assisted prospecting is reshaping this role faster than any other, and a track that pretends otherwise reads as dishonest to a cohort already using these tools daily. The workable framing is neither hype nor denial: AI absorbs volume and first-draft personalization, and the durable human value shifts toward judgment — which accounts to prioritize, when to break sequence, how to handle the live conversation. Teach reps to direct the tools rather than compete with them.

The manager track is the highest-leverage and most-skipped of the three. A manager with six to eight direct reports who leaves the event running a real coaching cadence replays that habit weekly across every rep they lead for the entire fiscal year — six to eight times the multiplication of any individual-contributor content. Yet the common default is "managers are AEs too, send them to the AE track," which destroys the leverage entirely.

Core modules: coaching cadence, forecasting methodology, 1:1 design, structured hiring and talent calibration, and comp-plan explainability. The hardest one to get right is coaching cadence, because most managers default to deal-coaching — "what's the status on Acme?" — which is inspection wearing a coaching costume. Real coaching is skill-coaching: observe actual behavior, name one specific skill to improve, follow up next week. Drill the distinction explicitly, ideally by having managers run a coaching conversation on a real rep in a paired exercise and receive feedback on whether they coached a skill or merely inspected a deal. A manager who leaves running weekly skill-coaching instead of weekly status checks is the single highest-ROI outcome the whole event can produce.

The forecasting module should install a shared definition of commit, best-case, and upside, plus a repeatable structure for the weekly forecast call. A call where reps recite numbers and the manager nods is theater; a call where every commit deal is pressure-tested against evidence is a discipline. And comp explainability is the module managers skip and most regret skipping — when the new plan lands, reps bring their questions to their manager first, and a manager who cannot confidently explain the plan amplifies confusion across the whole team.

The manager track also needs visible executive presence. The CRO sitting in the room, not sending a recorded message, is what tells managers their development is real. A nominal manager track starved of executive presence, methodology content, and a decent time slot is arguably worse than no track at all — it teaches managers that their growth is a checkbox.

The re-mixing block deserves its own slot on day two. The AE+SDR handoff is, in most funnels, the single largest source of pipeline leakage: an SDR books a meeting, the AE disqualifies it, the SDR feels their work was wasted, the AE feels they were sent garbage, and both are usually partly right because "qualified" was never defined the same way on both sides. Put the real AE and the real SDR who feed each other in a room with three recent disputed handoffs and have them negotiate a written definition of a qualified meeting. That artifact is worth more to conversion than most keynotes, and the relationship it builds changes how the handoff runs for the rest of the year. Manager+IC pairings serve a parallel purpose: managers practice coaching on someone who is not their direct report, which lowers the stakes; ICs experience structured coaching, often for the first time, and learn what to ask for. Mixed-role seating at meals is not a soft extra — it is the antidote to three tribes.

Numbers, ranges, and what the benchmarks actually support

Operators need defensible ranges to build a plan against, and they need to know how much confidence each range deserves.

Agenda split. The 40-50% shared / 50-60% breakout ratio is the working default. Below about 35% shared, the event stops functioning as a company moment and becomes three concurrent training classes that happened to book the same hotel. Above about 60% shared, you have effectively reverted to single-track with a token breakout. The band is wide because motion complexity moves it — a high-ACV enterprise org can justify more breakout depth; a transactional org needs less.

Cost per attendee. Fully loaded — travel, lodging, per diem, event production, and the cost of days out of seat — most B2B software companies land in the low-thousands-per-person range, with enterprise events at large companies running considerably higher. For a 150-person event that is a mid-six-figure direct cost. Layer on methodology partners, LMS configuration, and content design and total investment commonly reaches seven figures at that headcount. Partner engagements vary enormously — a single SDR-craft workshop and a multi-quarter enterprise methodology transformation are both "a methodology partner," and they differ by more than an order of magnitude.

Where the incremental spend actually sits. A well-run sales org already owns its LMS, conversation-intelligence platform, forecasting tool, and engagement platform for year-round use. The kickoff-incremental cost of those is *configuration* — building role-specific learning paths and role-specific scorecards — not new licenses. The genuinely incremental spend concentrates in methodology partners and content design. Content design is the most chronically under-budgeted line, which is precisely why breakouts so often feel recycled. Good role-specific curriculum is real work, and starving it is a false economy that resurfaces as content fatigue.

Reported lift. Published enablement and sales-development research consistently finds meaningful improvement in role-specific metrics from stratified, reinforced programs versus undifferentiated ones — typically reported in the mid-teens to high-twenties percent range on role-specific quota, pipeline, and forecast-accuracy measures, with a parallel retention benefit concentrated in the SDR and new-manager cohorts. Treat these as population statistics across many programs, not a guarantee for any single event. The variance is almost entirely execution quality: an organization that nominally splits tracks but skips reinforcement, embeds no partner in the breakouts, and de-prioritizes the manager track will land at the bottom of the range or below it. Benchmarks describe what disciplined execution achieves, not what an org chart delivers.

The retention argument is the one that funds the design. SDRs and newly promoted managers are the two cohorts most likely to leave within a year, and they are the two most damaged by an AE-pitched agenda. Fully loaded SDR replacement cost — recruiting, onboarding, and the ramp gap before the replacement produces — is substantial. Front-line manager replacement cost is far higher, because a departing manager destabilizes an entire team's pipeline and morale at once. Avoiding even a handful of departures per year across those two cohorts can approach the entire cost premium of the stratified design over the single-track one, before you count a single point of quota lift. That makes the retention case a hard cost-avoidance argument for the CFO conversation, not a soft morale argument.

Retention of content itself. Without structured reinforcement, learning content decays sharply within a quarter — the widely cited figure is that only a small fraction of unreinforced training content is retained after ninety days. This is the number that should scare an operator most, because it means the entire three-day investment is at the mercy of what happens in weeks four through thirteen.

Reinforcement must be stratified too. The most common self-inflicted wound is a beautifully split kickoff followed by an undifferentiated reinforcement program — identical LMS modules pushed to every role, one generic 1:1 template, one scorecard. That unwinds the split the moment the event ends. Each cohort needs its own track:

• AE reinforcement — the qualification scorecard becomes a habit, with every commit deal scrubbed in the weekly 1:1, plus spaced micro-drills on objection handling and negotiation reframes.
• SDR reinforcement — weekly sequence-performance review plus one real call listened to together by rep and manager each week, with a single named improvement.
• Manager reinforcement — the manager actually running the coaching cadence they learned, and being held accountable for it by their own leader, who asks in *their* 1:1 how many skill-coaching sessions happened that week.

Pre-work matters as much as post-work. Role-tailored pre-event modules delivered roughly four weeks out let breakout time go to practice instead of baseline instruction. Identical pre-work for all roles becomes generic noise nobody completes.

The scorecard is the spine. RevOps should build the role-specific 30/60/90 scorecard *before* the event, not improvise it after. AE metrics: pipeline coverage ratio, qualification-scorecard adoption, attainment. SDR metrics: meetings booked, sequence performance, connect rate. Manager metrics: team forecast accuracy, 1:1 frequency, coaching sessions run. If the scorecard does not exist on day one of reinforcement, the reinforcement program has no feedback loop and will drift. The honest test at ninety days is whether role-specific behavior is measurably above the pre-event baseline. If you cannot show that, you ran an event, not an investment.

And the deepest reason the manager track outranks the others: the manager is the delivery mechanism for everyone else's reinforcement. Software prompts the behavior; the weekly 1:1 makes it stick. Skimp on the manager track and the reinforcement of every other track quietly fails alongside it.

Trade-offs, alternatives, and when not to split

Splitting the agenda is the right default, not a universal law. A disciplined operator pressure-tests it against the cases where it fails.

Below roughly twenty reps, do not split. Three parallel tracks carry fixed costs — three instructors, three rooms, three sets of content design, potentially three partner engagements — that do not amortize across a small headcount. A twelve-rep startup copying a large enterprise's track architecture will spend more on structure than the structure returns. The right design at that scale is a unified main stage plus short role-specific clinics plus a strong post-event LMS. Stratification is something an org grows into.

Between roughly twenty and fifty reps, go hybrid. Run full AE and manager tracks; run the SDR content as a partial track or a deep clinic depending on SDR headcount. Above fifty, full three-track. Above a hundred and fifty, the question shifts to whether to add fourth and fifth tracks for sales engineers and customer success, and whether regional sub-tracks make sense.

Methodology maturity flips the recommendation. An organization adopting a sales methodology for the *first time* should not split methodology content by role. Teach one methodology to the entire sales org so all three cohorts share a common language, then stratify the *application* of it. Splitting methodology before the foundation exists produces three cohorts speaking three dialects who cannot collaborate across the funnel. Once the methodology is mature and adopted, split aggressively — the breakouts can go straight to advanced role-specific application.

Tenure distribution is a second modifier. A company in a heavy hiring phase, where half the room joined in the last six months, should weight toward foundational content and ramp integration; advanced enterprise-deal drills are wasted on a room of new hires. A stable, tenured team can go straight to edge cases. The agenda that energizes a tenured team overwhelms new hires, and vice versa. Make the tenure decision and the stratification decision together.

Virtual and hybrid formats require redesign, not a port. Parallel video breakout rooms have lower engagement, no informal cross-role mixing, and a fraction of the energy of physical breakouts. An organization that runs a virtual kickoff by replicating its in-person multi-track agenda produces exhausted, disengaged attendees and a worse outcome than a well-designed unified virtual event would have. Virtual stratification needs shorter sessions, higher production value, dedicated per-track moderators, and a much heavier async supplement. It is a different design.

Motion fit governs partner selection. A framework built for $500K enterprise deals is the wrong tool for a $20K transactional motion, and the reverse is equally true. Choose the partner whose framework matches your actual motion, insist on continuity — the strongest engagements make the breakout the kickoff of a year-round curriculum rather than a one-time appearance — and vet the *actual breakout instructor*, not the brand. The named founder may deliver the keynote; a staff instructor will run your breakout, and the engagement is only as good as that person.

The novelty trade-off. Splitting answers "is this content for the right audience?" It does not answer "is this content worth the audience's time this year?" Those are independent questions, and an organization can run a textbook three-track design every January and still produce a flat event if the AE track recycles last year's drills and the manager track repeats the same coaching framework. The fix is to anchor each year's curricula to gaps surfaced in the prior year's actual data — the qualification element AEs most often skip, the channel where SDR sequences underperformed, the coaching habit managers failed to sustain. Role-correct *and* demonstrably responsive.

Pitfalls and how to avoid them

Diffuse ownership. The most reliable predictor of a weak track is a track that "belongs to enablement and sales leadership together." Shared ownership becomes no ownership. Fix: one accountable name per track, everyone else a contributor or reviewer. Enforce it by requiring each owner to sign off on their own track in writing and requiring the CRO to arbitrate main-stage allocation conflicts. An agenda that has not been negotiated across the VP layer has not been designed; it has accumulated.

The single-owner delegation trap. Kickoff content design is frequently handed to one enablement program manager who lacks the authority to tell a VP Sales that their beloved main-stage session does not serve the SDR cohort. Without explicit VP-level alignment, the agenda defaults to whoever carries the most political weight — almost always sales leadership, almost always the AE-heavy design. Treat the agenda as a contract, not a document.

The Friday-afternoon SDR slot. Where a track sits on the calendar is a status signal the cohort reads instantly. SDR content scheduled after the AE track ends, in the worst room, with no executive present, tells fifty people exactly what the org thinks of them. Audit slot quality as deliberately as content quality.

Main-stage dilution. The instinct to make every keynote serve every role produces sessions stretched so thin they land for nobody. Better to accept that a session is core for one role and useful for another, and put the role-specific material where it belongs. The role-coverage map is the enforcement tool.

Skipping cross-role mixing because nobody owns it. The pairing block sits between three track owners and therefore belongs to none of them. Assign it explicitly, usually to enablement, and put it on the agenda in ink. "If there's time" means it will never happen.

Skipping measurement because it is invisible for ninety days. This is the first thing cut and the most expensive to lose, because without it every subsequent year's design is guesswork. Build the scorecards during the design phase, not after the event.

Starting the design too late. Twelve weeks out is the minimum, and it is genuinely tight. Weeks twelve to ten: lock the architecture and the split, secure VP alignment and budget, name track owners. Weeks ten to eight: contract partners with the breakout-embedding requirement made explicit, not just keynotes. Weeks eight to six: each owner drafts their breakout agenda while enablement builds the role-coverage map. Weeks six to four: design the cross-role exercises, finalize the day-by-day agenda, and build the scorecards with RevOps. Weeks four to one: launch role-tailored pre-work and run a content dry-run. Strong methodology partners book out months ahead, so start partner conversations sixteen to twenty weeks out even though contracting happens later.

Skipping the dry run. The week-four content dry-run — track owners and partner instructors walking their breakouts in front of the enablement leader, with any session still lecture-heavy or off-role sent back — is the most commonly skipped checkpoint and the most common reason a well-architected event still delivers weak breakouts. The architecture was right; the execution was never pressure-tested.

Treating the event as an event. The strongest programs treat kickoff as the high-visibility anchor of a continuous, year-round enablement system: the breakout introduces a framework, the LMS reinforces it, quarterly business reviews inspect it, and next year's design builds on it. Organizations that treat it as a standalone burst get a burst of energy that decays within weeks no matter how well the three days were designed.

Running the same agenda on inertia. The three checkpoints that break this cycle are the week-twelve architecture lock, the week-four dry run, and the ninety-day outcome review where RevOps presents scorecard movement that feeds directly into next year's design. Run all three and the event improves annually. Run none and you rerun last year's agenda forever, wondering why the lift never compounds.

Related questions

How long should the kickoff be?

Three days is the common default and works for most mid-market orgs: one main-stage day, one and a half breakout days, and a closing session. Two days forces cuts to practice time; five days is hard to justify against lost selling days unless the org is large and geographically dispersed.

Should sales engineers get their own track?

Once the SE cohort passes roughly fifteen to twenty people, yes. Their job — technical discovery, demo architecture, proof-of-concept design — diverges from an AE's as much as an SDR's does. Below that, embed them in the AE track with dedicated technical-depth sessions.

Who should build the role-coverage map?

RevOps, working with enablement. RevOps has the cross-functional view and no incentive to favor a cohort. Enablement owns the remediation once the map exposes gaps, and the CRO arbitrates when a track owner and the main-stage owner disagree about where a session belongs.

What if AEs and SDRs report into different leaders?

That is the norm, and it is why VP-level alignment is a hard gate. Each leader owns their track's curriculum and outcomes, but the agenda split and the cross-role pairing block must be negotiated jointly, with the CRO breaking ties.

Can you split content at a virtual kickoff?

Yes, but not by copying the in-person agenda. Shorten every session, assign a dedicated moderator to each track, cut total live hours substantially, and shift more content to asynchronous modules before and after. Treat it as a separate design exercise.

FAQ

What is the right split between shared and role-specific content?

Roughly 40-50% shared main stage and 50-60% role-specific breakouts. The shared portion carries the fiscal-year narrative, roadmap, customer voice, and recognition — the reasons you gathered everyone physically. The breakout portion carries the skill work where the three jobs diverge. Motion complexity shifts the ratio: enterprise motions justify more breakout depth, transactional motions less.

Why is the manager track considered the highest-leverage?

Because a manager with six to eight reports replays what they learn across their whole team every week for a year. Individual-contributor content improves one person's performance; manager content multiplies across a team. The manager is also the delivery mechanism for everyone else's reinforcement — the weekly 1:1 is what makes AE and SDR content stick after the event ends.

Is it worth splitting the agenda for a small sales team?

Below roughly twenty reps, no. Three parallel tracks carry instructor, room, and content-design costs that do not amortize at that scale. Run a unified main stage with short role-specific clinics and a strong post-event LMS instead. Between twenty and fifty, run full AE and manager tracks with the SDR content as a clinic or partial track.

How far in advance should content design start?

Twelve weeks is the minimum for the full design cycle, and it is tight. Architecture and ownership lock at week twelve, partners contract by week eight, curricula draft through week six, cross-role exercises and scorecards finalize by week four, and pre-work launches in the final month. Begin partner conversations sixteen to twenty weeks out, since strong instructors book far ahead.

What happens if reinforcement is skipped?

Retention of unreinforced content decays sharply within ninety days, which means the entire investment is at the mercy of what happens in the weeks after the event. Without role-specific spaced repetition, a role-specific 1:1 agenda, and a 30/60/90 scorecard built beforehand by RevOps, the design produces energy rather than durable behavior change.

How do you keep three tracks from creating three tribes?

Schedule the re-mixing rather than hoping for it. Pair each AE with the SDR who actually feeds them for a handoff exercise producing a written definition of a qualified meeting. Pair managers with ICs who are not their direct reports for coaching practice. Seat people across roles at meals. Stratify the skill content; deliberately mix the handoff content and the social fabric.

Sources

• https://hbr.org/2016/12/how-to-really-motivate-salespeople
• https://www.gartner.com/en/sales/insights/sales-enablement
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights
• https://www.salesforce.com/resources/articles/sales-enablement/
• https://www.hubspot.com/sales-enablement
• https://www.gong.io/resources/
• https://blog.bridgegroupinc.com/
• https://www.salesreadinessgroup.com/blog
• https://www.rainsalestraining.com/blog
• https://www.forrester.com/blogs/category/sales-enablement/

Related on PULSE

• What are the core design pillars of an effective sales kickoff?
• In-person vs. virtual sales kickoff: which format wins?
• How do you build a 90-day post-kickoff reinforcement system?
• How do you measure sales kickoff ROI?
• How do you communicate comp plan changes at kickoff?
• How do you integrate new-hire ramp into kickoff planning?