The offsite was in Lisbon. Three days, 90 people from four countries, a keynote speaker who had rowed across an ocean, and a printed folder on every seat with the new compensation plan inside. On the morning of day two the CRO put up the new territory map. Eleven AEs learned from that slide that their biggest account had moved to someone else in the room.
The rest of the event was fine. Good food, decent breakouts, a product session everyone said was useful. Then everybody flew home and spent the next three weeks arguing with their manager about accounts instead of selling. February pipeline creation came in well under the previous February. Nobody connected the two things out loud, because the kickoff had been rated 4.6 out of 5 in the feedback survey.
I have sat in about a dozen of these, on both sides. Once I built the deck. What I have come around to is that a sales kickoff is not a motivational event with some operational content attached. It is a deployment event with some motivation attached, and almost every team gets that order backwards.
What an SKO actually costs
Start with the money, because most founders never see the fully loaded number.
The per-attendee benchmark for 2026 sits somewhere between $2,500 and $5,500 depending on venue and production, with one analysis putting the US average around $3,144. Other sources land in the $2,000 to $4,000 band, which for a mid-sized revenue org works out to $100,000 to $400,000 for the event itself.
Then add the part that never appears on the budget line. A 60 person GTM team out of the field for three days is 1,440 working hours. If your average AE carries a $900k quota, three days of every seller in the company not selling is real money, and it lands in the quarter where your pipeline is thinnest anyway.
So the honest cost of a January kickoff for a 60 person team is somewhere north of $350,000 once you count the selling days. That is a headcount. You would interview four people and run three reference calls before approving a headcount. Most companies approve the kickoff because they ran one last year.
The 30-day problem nobody budgets for
Here is the uncomfortable research. Without reinforcement, people forget roughly 70 percent of new information within 24 hours and close to 90 percent within a week. Studies of lecture-style training put the loss at more than 80 percent by day 90. Ebbinghaus described the shape of this in 1885 and nothing about a hotel ballroom has improved it since.
Share of content from a traditional one-off training workshop that is gone from memory by day 30. Your kickoff is a training workshop with better lighting.
I want to be careful here, because the forgetting curve gets quoted by every vendor selling reinforcement software, and the underlying studies were about nonsense syllables, not about how to sell to a CFO. The precise percentage is not the point. The direction is well established and matches what any sales manager can tell you: whatever was taught in the ballroom is invisible on call recordings by March.
That is not an argument against holding a kickoff. It is an argument against the specific belief that the event is where learning happens. The event is where you announce, align, and start practising. Learning happens in the 90 days after, or it does not happen.
The real failure: three jobs jammed into one event
Most kickoffs try to do three unrelated things in the same 72 hours, and the three interfere with each other.
The first job is deployment. New comp plans, new territories, new quotas, new segments, new pricing, new stage definitions, new tooling. This is operations work with legal and financial consequences.
The second job is capability. Teaching a new play, a new objection pattern, a new discovery structure, a new product story. This is training work that needs repetition and coaching.
The third job is belonging. People who work remotely across five time zones getting to eat dinner together and remember they are on a team. This is genuinely valuable and it is the only one of the three that actually requires everyone to be in the same building.
Bundle them and each one degrades. You announce a territory change on stage, and every seller in the room stops listening to the rest of the day because they are calculating what happened to their number. You teach a new discovery framework in a 45 minute session with 90 people watching, which is a lecture, not practice. And the belonging part gets crowded out by an agenda so packed that the only unstructured time is the bar at 11pm.
Ship the changes before the event, not at it
This is the single change I would make if I could only make one. Comp plans, territories, quotas, and account assignments go out in writing at least two to three weeks before anyone gets on a plane. Individually. With the manager, not from a stage.
The reasoning is simple. Territory and comp changes trigger a grief cycle, and you cannot run useful training through a room full of people in the anger stage. McKinsey has found that more than half of executives report productivity dropping during the transition window of a reorganization. You do not want that window opening on day two of the event you spent $350,000 on. You want it opening earlier, in private, so the kickoff becomes the place where people ask their remaining questions about a decision they have already absorbed.
Never announce a territory change from a stage.
A slide with the new account map turns half the room into people doing arithmetic about their own income. They stop hearing everything that follows. Send it individually two to three weeks out, let managers absorb the reaction one to one, and use the event for the questions that survive that conversation.
The RevOps pre-flight list
By the time the first session starts, all of this should already be live in the system, not sitting in a spreadsheet waiting for someone to load it:
- New territories and account ownership written into the CRM, with open pipeline reassigned and the old owner still visible on the record for history.
- Quotas loaded per rep per period, so forecast reports do not break on 1 January.
- Comp plans signed. Not sent, signed. If you are on a spreadsheet and it is creaking, that is a signal about commission tooling, not a reason to delay.
- New deal stage definitions and exit criteria updated in the pipeline itself, with the field help text rewritten to match.
- Any new segmentation reflected in lead routing rules, so the first inbound lead of the year does not go to last year's owner.
- Reporting rebuilt against the new structure and checked against December actuals, so the first Monday pipeline review does not turn into a debate about whether the dashboard is broken.
None of that is glamorous and all of it is what determines whether the quarter starts clean. We do this work as part of CRM and RevOps builds and it is consistently the least discussed, most expensive thing to get wrong. A territory change that lands in the CRM three weeks late costs more than the entire event.
An agenda built around practice, not slides
Once deployment is out of the way, the event has room to do the thing it is uniquely good at: making people practise in front of each other.
My rule of thumb is that at least half the programmed time should be reps talking, not leadership presenting. Practical version for a two day agenda:
Day one morning is context. Where the number comes from, what changed in the market, which two segments we are actually going after, and one customer on stage walking through how they bought. A real customer beats any keynote you can hire. They will say something about your sales process that no internal person is allowed to say.
Day one afternoon is the play. Pick one motion. One. The new ICP, or the expansion motion, or the competitive displacement play. Teach it for 40 minutes, then spend two hours in groups of six running it live with a scorecard, with managers scoring. Record the sessions.
Day two morning is deals. Not hypothetical roleplay, actual open pipeline. Each rep brings one stuck deal and gets 15 minutes of structured challenge from peers and a manager. This is where the multithreading gaps and the missing economic buyer show up in front of everybody, which is far more persuasive than a slide saying you should multithread.
Day two afternoon is commitments and logistics. Every rep leaves with a written, specific 90-day behaviour commitment tied to the play. Not "I will do better discovery." Something like "every deal I open above $50k will have a documented mutual action plan by stage three, and I will bring the first three to coaching."
Keep programmed content under six to eight hours a day. People stop absorbing after that, and the informal conversations at dinner are doing more for retention than your seventh session.
The 90 days that decide whether it worked
The event is the small part. The reinforcement plan is the part that almost nobody builds, and it is the reason the same company runs the same kickoff every year and gets nothing.
The mechanics of the reinforcement do not need to be expensive. A 20 minute weekly drill inside the existing team meeting. One recorded call per rep per month, scored against the same rubric you used at the event. A certification gate at week eight where the rep runs the play once, cleanly, in front of their manager. If you already have conversation intelligence recording every call, the scoring can be partly automated, and this is one of the few places where AI in the workflow earns its keep rather than generating more noise.
What kills reinforcement is always the same thing: the manager. A frontline manager with 8 direct reports, their own forecast, and no protected coaching time will drop the drill by week three. If you are not willing to take something off the managers' plate to make room, do not promise the reinforcement plan. Run a shorter event and save the money.
How to measure an SKO without lying to yourself
Feedback surveys measure catering. Here is what I would actually instrument, and the important part is capturing the baseline before the event, because after the fact everybody remembers the old number as worse than it was.
Leading indicators, weeks 1 to 8: certification completion on the new play, share of calls where the new message shows up in the recording, number of coaching sessions actually held against the number scheduled, and adoption of whatever field or artifact the play requires (mutual action plan attached, new qualification field filled).
Lagging indicators, weeks 8 to 26: win rate on deals worked with the new play against deals that were not, pipeline coverage in the emphasized segment, average deal size in the new ICP, and ramp time for anyone onboarded around the event.
One honest caveat on all of this. You cannot cleanly attribute a Q2 win rate change to a January event, because ten other things changed at the same time. What you can do is compare reps who certified early against reps who certified late, or the segment you emphasized against the one you did not. It is not a controlled experiment and I would not present it to a board as one. It is still infinitely better than a satisfaction score.
What I would cut
If I were trimming a typical kickoff agenda tomorrow, in order:
The external motivational keynote. It costs $15,000 to $40,000 and produces a feeling that lasts until the airport. Spend it on a customer panel and two extra coaches.
The full product roadmap walkthrough. Sellers do not need 60 slides of roadmap, they need the three things they can say to a prospect this quarter and the two things they must stop promising. Send the rest as a document.
Every session where one person presents to more than 30 people for more than 20 minutes. Record it and make it pre-work. Meeting people in person is expensive. Use the room for the things that only work in a room.
The awards ceremony that runs 90 minutes. Recognition matters, but the same six people win every year and the other 54 are watching a show about somebody else.
Cutting those four usually gives back a full day, which means either a cheaper two day event or the same three days with real practice in them. And if your team is under 15 sellers, skip the production entirely. One good day in a room you already have, with the playbook rewritten first, will beat a hotel.
Kickoff in January, comp plans still in a spreadsheet?
We build the CRM, territory, quota and reporting layer so the event is about selling, not about fixing the system afterwards. Book a 30 minute audit and we will tell you what needs to ship first.
Book an audit →Frequently asked questions
When should we start planning our sales kickoff?
Sixteen to twenty weeks out for the event itself, which for a late January or February kickoff means starting in September or October. The operational work runs on its own clock and should start earlier: territory design and comp modelling need to be substantially done ten weeks before, because they have to be built in the CRM, tested, and delivered to people individually before anyone travels.
How long should an SKO be?
Two days for most B2B teams under 100 sellers, three only if you have genuine regional complexity or a major product launch to train. Keep programmed content to six or seven hours a day. The value of a third day drops sharply once people stop absorbing, and you are paying for it twice, once in cost and once in selling time.
Should the kickoff be in person or virtual?
In person for the practice and the belonging, virtual for anything that is one person talking to a crowd. The hybrid model that works is pre-work delivered async in the two weeks before (product updates, market context, comp plan details), then a shorter in person event that assumes everyone did the reading. The model that fails is a three day video call, which is just a webinar nobody can leave.
How much should we budget per person?
Current benchmarks land between $2,500 and $5,500 per attendee for a fully produced event, with an average near $3,100. Below about $1,500 you are running an internal meeting with sandwiches, which is completely fine for a team of 12. The number that matters more is the ratio: if less than 20 percent of your budget is going to coaching, practice design, and the reinforcement programme afterwards, you are buying an event rather than a capability.
How do we stop the kickoff from being forgotten by March?
Pick one play instead of five, make people practise it in front of each other at the event with a scorecard, then run a 20 minute weekly drill and one scored call per rep per month for twelve weeks. Put a certification gate at week eight. Protect the managers' time so they can actually run it. Everything else is optional; without that loop, the content is gone within a month whatever you spend on the venue.
Nothing about this is complicated. It is just unglamorous, and it happens in the weeks either side of the event rather than in the room, which is why it keeps getting skipped. If the operational half of your kickoff is the part you are worried about, tell us what January looks like and we will help you sequence it.