---
name: kickoff-meeting-builder
description: Build a complete kickoff meeting pack for a new client engagement — agenda, pre-reads, discovery questions, RACI starter, comms-cadence agreement, first-30-days plan, and post-meeting action log.
version: 1.0.0
author: VantagePoint Networks
author_url: https://www.vpnetworks.co.uk
audience: Consultants, Project Managers, MSP Account Managers, Agency Leads, Delivery Leads at any professional service firm
output_format: Formatted Markdown pack with pre-meeting email, meeting agenda, facilitator script, discovery question bank, outputs, and post-meeting action log.
license: MIT
last-reviewed: 2026-04
---

# Kickoff Meeting Builder

A Claude Code skill for the consultant or delivery lead turning a signed SoW into a real engagement — producing the first client meeting that sets the relationship up for success instead of scrambling through a generic template.

## How to use this skill

1. Download this `SKILL.md` file.
2. Place it in `~/.claude/commands/` (macOS/Linux) or `%USERPROFILE%\.claude\commands\` (Windows).
3. In Claude Code, run `/kickoff-meeting-builder`. Describe the engagement. Answer the clarifying questions. Receive the pack.

## When to use this

- SoW is signed, project starts in <2 weeks, you need a first meeting that's more than "nice to meet you".
- A new retainer client is starting and you want to set service expectations upfront.
- You're taking over an engagement mid-flight and want a re-kickoff to reset the relationship.
- You want a reusable kickoff template for your consultancy or MSP practice.

## What you'll get

A single Markdown document containing:

- **Pre-meeting email** (sent 5 days before)
- **Pre-reads list** (with who reviews what)
- **Meeting agenda** (60-90 min standard, 120 for complex)
- **Facilitator script** (exact phrasing for the tricky moments — introductions, scope alignment, risks)
- **Discovery question bank** (by topic: scope, stakeholders, risks, tech environment, success definition)
- **Outputs to produce live** (named RACI, comms cadence, first-30-days actions)
- **Post-meeting action log template**
- **Follow-up email** (within 24 hours of meeting)

## Clarifying questions I will ask you

1. **Client name, sector, size?**
2. **Engagement type?** (project / retainer / discovery / remediation)
3. **SoW / engagement summary in one sentence?**
4. **Who's attending from the client?** (names, roles)
5. **Who's attending from your side?**
6. **Meeting format?** (in-person, remote, hybrid)
7. **Duration you have?** (60 / 90 / 120 min)
8. **Client maturity with your type of work?** (first time, experienced, sceptical, enthusiastic)
9. **Any known sensitivities?** (recent failure, budget cut, change of sponsor, conflict)
10. **Tone preference?** (collegial, formal, efficient-no-nonsense)
11. **Deliverables due in first 2 weeks?** (drives the first-30-days section)
12. **Any regulatory / confidentiality context?** (legal privilege, FCA, NDA in place)

## Output template

```markdown
# Kickoff Pack — <client> × <your firm> — <date>

**Engagement:** <name> · **Sponsor:** <client role> · **Lead:** <your role>
**Meeting:** <date, time, duration, format> · **Location / link:** <>

## 1. Pre-Meeting Email (send T-5 days)
> Subject: Kickoff for <engagement> — <date>
>
> Hi <sponsor name>,
>
> Looking forward to our kickoff on <date> at <time> (<duration>).
>
> **Attendees:** <list your side + confirmed client side>. If anyone's missing, could you confirm by <date>?
>
> **Before the meeting (15-min read):**
> - <pre-read 1> — attached
> - <pre-read 2> — link
> - <pre-read 3> — summary below
>
> **What we'll cover:**
> 1. Introductions + roles
> 2. Recap of scope and outcomes
> 3. Success definition
> 4. Key risks and dependencies
> 5. Communications + cadence
> 6. First-30-days plan
>
> **What you'll leave with:**
> - Agreed RACI
> - Agreed comms cadence
> - Named owners for the first 5 actions
> - Dates for the first milestone
>
> If anything's top-of-mind or worrying you before we meet, feel free to send it my way.
>
> <signature>

## 2. Pre-Reads Index
| Document | For | Time to read | Location |
|---|---|---|---|
| SoW (current version) | All | 10 min | <link> |
| Project brief | All | 5 min | <link> |
| Team bios (your side) | Client side | 2 min | <link> |
| Your methodology primer | Client side | 5 min | <link> |
| Relevant past case study | Client side, optional | 3 min | <link> |

## 3. Meeting Agenda (90 min example)
| Time | Item | Owner | Output |
|---|---|---|---|
| 00-05 | Welcome + introductions | Lead | Everyone knows who's who and why they're here |
| 05-15 | Recap of engagement + outcomes | Lead | Shared understanding of SoW intent |
| 15-30 | Client context sharing | Sponsor | Your side understands the *why* beyond the SoW |
| 30-45 | Success definition | Lead | 3-5 measurable criteria agreed |
| 45-60 | Risks + dependencies | All | Initial risk register |
| 60-75 | Roles + RACI | Lead | Named owners per workstream |
| 75-85 | Comms + cadence | Lead | Agreed cadence, channel, meeting rhythm |
| 85-90 | Close + first actions | Lead | First 5 actions with owners + dates |

## 4. Facilitator Script (the tricky moments)

### Opening (00:00)
> "Thanks for making time today. Before we dig in, quick round: name, role, and in one sentence what does success look like for you from this engagement? I'll start."
>
> (Your side goes first — models the format, lowers stakes.)

### Recap of SoW (05:00)
> "Let me take 5 minutes to recap what we've scoped in the SoW, not to read it to you but to check we all heard it the same way. Then I want to ask what's changed since we signed, or what's come up that we should know."
>
> (Always ask "what's changed since signing" — answers reveal scope drift before it happens.)

### Success definition (30:00)
> "If we're sitting here in <end of engagement> reviewing what we delivered, what three things would make you say 'that was worth it'? Could be outcomes, could be operational things, could be what didn't happen."
>
> (Note these verbatim. Return to them at every steering meeting.)

### Risks (45:00)
> "Let's do a quick risk inventory. I'll share three I'm thinking about, then I'd like each of you to add one you're worried about — even if it feels obvious."
>
> (Surfaces the sponsor's unspoken anxieties.)

### Comms cadence (75:00)
> "I'd like to agree one standing check-in, one channel for urgent things, and one channel for everything else. My suggestion: weekly 30-min steering with <sponsor>, Teams / Slack for everyday, and I'll send a written status every <cadence>. Does that work for you, or would you prefer different?"
>
> (Propose, don't ask. Easier to adjust a proposal than to co-create in meeting.)

### Close (85:00)
> "Before we wrap, let's nail down the first five actions. I'll type, you confirm who and by when."
>
> (Type live on shared screen. Commitments with witnesses stick.)

## 5. Discovery Question Bank

### Scope & outcomes
- What was the problem you were trying to solve when you decided to run this engagement?
- What does the Board / Partners expect from this?
- Is there anything in the SoW that you'd change now you've slept on it?
- What's explicitly NOT your goal?

### Stakeholders
- Who, besides you, will be watching what we deliver?
- Who would be the loudest detractor if this goes wrong?
- Who would benefit politically / operationally from this succeeding?
- Is there anyone we should brief that isn't in this meeting?

### Tech environment (if relevant)
- Which systems are in scope?
- Who administers them?
- Any recent incidents / outages / projects we should know about?
- Any frozen change windows coming up?
- Any compliance / audit windows in our period?

### Risks
- What are you most worried might derail this?
- What have you tried before that didn't work, and why?
- Who might be a single point of failure (on your side) we should plan around?

### Success
- How will you measure it?
- What's "just enough" vs. "over-delivered"?
- What would make this a repeat engagement?

### Operational
- Where / how should we store working documents?
- What information-handling rules apply (NDA, sector, privilege)?
- Holiday / absence plans in the engagement window?
- Budget for expenses / travel / tools?

## 6. Outputs Produced in the Meeting

### Agreed RACI (example structure)
| Workstream | Responsible | Accountable | Consulted | Informed |
|---|---|---|---|---|
| Discovery | <your role> | Sponsor | SME, IT Lead | All-hands |
| Design | <your role> | Sponsor | IT Lead | Partners |
| Delivery | <your role> | Sponsor | IT Lead, end-users | All-hands |
| Sign-off | Sponsor | Sponsor | — | All |

### Agreed comms cadence
- **Standing steering:** weekly, <day>, <time>, <attendees>
- **Status update:** written, <cadence>, to <distribution>
- **Everyday channel:** <Teams / Slack> — response within <N> business hours
- **Urgent:** phone/text to <named> — response within 30 min

### First-30-Days Plan
| Week | Milestone | Owner | Dependencies |
|---|---|---|---|
| 1 | Kickoff + access provision | All | Sponsor provides access |
| 2 | Discovery interviews complete | Your | Client makes SMEs available |
| 3 | Draft design / findings | Your | — |
| 4 | Design review meeting | All | — |

## 7. Post-Meeting Action Log (produced in meeting, emailed within 4 hours)
| # | Action | Owner | Due | Status |
|---|---|---|---|---|
| 1 | | | | |
| 2 | | | | |
| 3 | | | | |

## 8. 24-Hour Follow-Up Email
> Subject: Kickoff follow-up — <engagement>
>
> Hi <sponsor>,
>
> Thanks for the kickoff yesterday — a useful session. As agreed:
>
> **Success criteria** — we'll measure against: (1) <>, (2) <>, (3) <>.
>
> **Top risks** — we'll keep an eye on: (1) <>, (2) <>, (3) <>.
>
> **Next steps (this week):**
> 1. <action, owner, by when>
> 2. <action, owner, by when>
> 3. <action, owner, by when>
>
> **Comms cadence** — weekly steering on <day/time>; written status every <cadence>; Teams for everyday; phone to <name> for urgent.
>
> Anything I've misrepresented, please shout. Otherwise, see you <next meeting>.
>
> <signature>
```

## Example invocation

**User:** "New retainer with a 40-person London law firm, £3k/month, covering general IT support, security monitoring, and a Cyber Essentials renewal. Sponsor is a managing partner, quite sceptical because previous MSP underperformed."

**What the skill will do:**
1. Ask 12 questions, pressing on: what "underperformed" meant specifically (response time? quality? communication?), who the sceptic's allies are on the client side, whether the Cyber Essentials renewal has a hard deadline.
2. Produce the pack with:
   - A facilitator script that explicitly addresses the sceptical sponsor: "I know previous experience hasn't been great. What specifically matters most to you that we get right?"
   - Success criteria including "monthly written report the Partners can read in 5 minutes" (a frequent MSP-relationship-failure point)
   - Comms cadence proposing a monthly in-person partners' update in addition to weekly steering (over-invests early in sceptical-sponsor relationships)
   - First-30-days focused on quick wins: helpdesk responsiveness metric baseline; visible Cyber Essentials progress; clean monthly report format
3. Flag that the 4-week mark is the first "is this working?" moment for a sceptical client — prep a small value-demonstration deliverable for the week-4 steering.

## Notes for the requester

- **Set scope expectations in the first 15 minutes.** Clients who don't hear a clear recap of scope will interpret gaps as "still to do."
- **Ask what's changed since signing.** Budget decisions, leadership changes, or a competitor's move may have altered the client's context without them telling you.
- **Commitment with witnesses sticks.** Capturing action owners live beats sending a draft for review.
- **Cadence over cleverness.** Boring, predictable communication beats brilliant quarterly reports.
- **Kick-off is a chance to re-scope politely.** "The SoW says X. Having talked today, my sense is we should focus first on Y. That OK?" — establishes you as a thoughtful operator, not a script-follower.
- **Good looks like:** within 48 hours the sponsor has emailed the post-meeting summary to their stakeholders without rewriting it.

---
*VantagePoint Networks · <https://www.vpnetworks.co.uk> · Authored by Hak · Free under the MIT licence*