ThinkWithPrompt by SynotticThinkWithPrompt

Plan a sales kickoff that changes how the team sells

A sales kickoff agenda built around a few behavior changes, with sessions, practice, and follow-through after the event.

MeetingsFew-ShotStandardSalesPlanFill-in Template

The prompt

Help me plan a sales kickoff (SKO). Audience and size: [roles, number of people, in person or virtual] Length: [e.g. 1 day, 2 days] Last year's results and this year's target: [HEADLINE NUMBERS] Strategic priorities for the year: [e.g. new product, move upmarket, new pricing, new territory model] Skill gaps we see: [e.g. discovery, multi-threading, negotiation] Budget and constraints: [DETAILS] Speakers available: [executives, customers, partners, product] Design the SKO around 3 behavior changes, not a list of topics: 1. Name the 3 behaviors we want reps doing differently by the end of Q1. 2. Build the agenda backward from those: each block either explains why, shows how, or has reps practice. 3. Keep no more than 40% of time on presentations; the rest is practice, role-play, and peer learning. 4. Include recognition moments, a customer voice, and time for regional or team breakouts. 5. Plan the follow-through: the 30/60/90-day reinforcement, manager coaching guides, and how we measure adoption. Return: - The 3 target behaviors and how we'll measure each. - A timed agenda: Time | Session | Format | Owner | Outcome. - A brief for each speaker (what to cover, what to avoid, length). - A post-event survey and reinforcement plan. - Logistics checklist. Use only the figures and speakers I provide; mark anything missing as [ADD].

Highlighted [brackets] are blanks to replace with your own details.

Fill in the blanks and use this promptMore Meetings prompts

What to fill in

  • roles, number of people, in person or virtual
  • e.g. 1 day, 2 days
  • HEADLINE NUMBERS
  • e.g. discovery, multi-threading, negotiation
  • DETAILS
  • executives, customers, partners, product
  • ADD

How this prompt is built

This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.

Related prompts

Find more prompts like this