| Category | Client Onboarding |
|---|---|
| Time to Run | 10 min |
| Difficulty | Standard |
| Output | Document |
| Client-Facing | No — internal use |
You've signed a new client and the first working session is 3-5 days away. You know what the engagement covers at a high level, but you haven't structured the kickoff itself. The temptation is to wing it — you've done this before, you know the work. But an unstructured first session sends a signal: that you're making it up as you go. The kickoff is where the client forms their operational impression of you.
Run this when you need a structured agenda for the first working session with a new client. The agenda covers what you'll discuss, in what order, and how long each section gets. It's your internal playbook for running the meeting — not a document you send to the client (though you could share a simplified version if you choose).
Copy the code block below and save it as a .md file. Upload it to Claude as a Project Knowledge file or attach it directly to a conversation. Then provide the inputs listed above and Claude will generate your engagement kickoff agenda.
---
name: engagement-kickoff-agenda
description: Generates a structured agenda for the first working session with a new client — triggered 3-5 days before the kickoff meeting.
metadata:
author: "Kathryn Brown, Practice Builders"
version: "1.0.0"
date: "2026-04-25"
---
# Engagement Kickoff Agenda
Generates a time-blocked internal agenda for the first client working session that establishes structure, expectations, and momentum.
**Core Principle: The kickoff agenda is not a list of topics — it's a sequence that builds confidence. Open with alignment (we agree on what we're doing), move to mechanics (here's how we'll work), close with first action (here's what happens next week). That sequence is non-negotiable.**
## What This Skill Does
**Job 1: Time Blocking** — Takes the session length and allocates it across required agenda sections. The skill enforces time discipline: no section gets more than 30% of the meeting, and the "next steps" section always gets protected time at the end. Meetings that run out of time before defining next steps are failed kickoffs.
**Job 2: Content Mapping** — Populates each agenda section with specific talking points drawn from the engagement type, deliverables, and participants. Not generic placeholders — actual content based on what this engagement needs to cover.
**Job 3: Participant Awareness** — Identifies which participants need to be drawn into which sections. If there's a decision-maker who won't be involved in day-to-day work, the agenda ensures their concerns are addressed early before they disengage.
## Section 1: Engagement Alignment (15-20% of session)
Open with a brief restatement of the engagement scope. Not reading the SOW aloud — a 2-3 sentence summary of "here's what we agreed to do and why." Then ask: "Does this still match your understanding?" This catches misalignments before work begins.
**Include:** Engagement type, duration, key deliverables, and success criteria if defined.
**Do not include:** Pricing, contract terms, or administrative details. Those were handled before the kickoff.
## Section 2: Working Mechanics (20-25% of session)
Cover how the engagement will actually run:
- **Cadence** — meeting frequency and format
- **Communication** — primary channel, response time expectations
- **Deliverables** — how work products will be shared and reviewed
- **Access** — what you need from the client (systems, data, people)
This section prevents the "how do we work together?" confusion that plagues the first 2-3 weeks of most engagements.
## Section 3: Priorities and Sequencing (25-30% of session)
Walk through the key deliverables in the order you plan to address them. For each:
- What it is
- When you'll start it
- What you need from the client to begin
- What "done" looks like
This is the highest-value section. It turns the SOW from a static document into a working plan with dependencies named.
## Section 4: Participant Roles (10-15% of session)
Name who does what. If there are multiple stakeholders, clarify:
- Who is the primary point of contact
- Who approves deliverables
- Who provides inputs or data
- Who has veto authority
For smaller engagements (one client contact), this section can be brief. For larger ones with multiple stakeholders, it prevents the "I thought you were handling that" problems.
## Section 5: Next Steps and First Action (10-15% of session)
Close with exactly what happens next. Name:
- What you will deliver and by when
- What the client needs to provide and by when
- When the next meeting is
- One thing the client should expect in their inbox within 48 hours
**This section must never be cut for time.** If the meeting runs long, shorten the Priorities section, not this one.
## Section 6: What to Skip / What to Watch For
**Leave alone:** Don't try to solve problems in the kickoff. If the client raises an issue, note it and schedule it for a future session. The kickoff is for alignment and structure, not troubleshooting.
**Watch for:** Participants who don't speak. If someone is in the room but silent through the alignment and priorities sections, they either disagree and aren't saying so, or they don't know why they're there. Address it: "Maria, I want to make sure this tracks with what you're expecting from your side."
## Quality Check (Internal — never shown to the user)
| # | Check | Pass? |
|---|-------|-------|
| 1 | Do time allocations add up to the session length (with no section exceeding 30%)? | |
| 2 | Does every deliverable from the inputs appear in the Priorities section? | |
| 3 | Is there a protected "Next Steps" section that can't be bumped? | |
| 4 | Are participant roles named specifically (not "the team will...")? | |
| 5 | Does the agenda produce one clear first action with a date? | |
**Enforcement:** Run all five checks. Identify the weakest section. Rewrite it. Verify the rewrite improved the output. Present only the finished version.
## Rules
- Always include time allocations (in minutes) for each agenda section.
- Never let the agenda exceed the session length. If it doesn't fit, cut the Priorities section to top 3 items and note the rest for a follow-up session.
- Name specific participants by role in the agenda, not "attendees."
- Keep the agenda to one page. If it's longer, you've over-detailed it.
- Do not include icebreakers, team introductions, or "getting to know you" sections. The client hired you to work, not to socialize.
- If the session is 30 minutes, cut to three sections: Alignment, Top Priority, Next Steps. Don't try to fit a 60-minute agenda into 30 minutes.
- Every section must have a specific outcome (decision, alignment, action item) — not just a topic.
## Output Format
# Kickoff Agenda: [Client Name] — [Engagement Type]
**Date:** [To be scheduled]
**Duration:** [Session length]
**Participants:** [Names and roles]
---
## 1. Engagement Alignment ([X] min)
[2-3 sentence scope summary]
- Confirm understanding of deliverables
- Surface any changes since signing
- **Outcome:** Shared agreement on scope and success criteria
## 2. Working Mechanics ([X] min)
- Meeting cadence: [proposed schedule]
- Communication: [primary channel and response expectations]
- Deliverable review: [how work products will be shared]
- Access needed: [specific systems, data, or people]
- **Outcome:** Clear operating rhythm established
## 3. Priorities and Sequencing ([X] min)
| Priority | Start | Client Input Needed | Definition of Done |
|----------|-------|--------------------|--------------------|
| [Deliverable 1] | [When] | [What you need] | [What done looks like] |
| [Deliverable 2] | [When] | [What you need] | [What done looks like] |
| [Deliverable 3] | [When] | [What you need] | [What done looks like] |
**Signal:** [What in the SOW or intake suggests this sequencing]
**Do This:** [Confirm sequence with client; adjust if dependencies shift]
## 4. Roles ([X] min)
- **Primary contact:** [Name]
- **Approvals:** [Name]
- **Inputs/Data:** [Name]
- **Outcome:** Everyone knows their lane
## 5. Next Steps ([X] min)
- [ ] [Your action] — by [date]
- [ ] [Client action] — by [date]
- Next meeting: [date/time]
- 48-hour deliverable: [what the client will see in their inbox]
## What Makes This Different
Most kickoffs are conversations that feel productive but produce no structure. This skill builds a time-blocked agenda with specific outcomes for each section, enforced participant engagement, and a protected next-steps block that prevents the meeting from ending in vague good intentions. The result is a client who walks out of the first session thinking "this person is organized" — which is the single strongest predictor of engagement satisfaction.
---
Copyright (c) 2026 Kathryn Brown, Practice Builders
This skill is licensed for your personal and business use. You may run this skill inside your own practice and share the outputs it produces with your team and clients. "Your practice" includes employees and contractors engaged to perform work for your business under your direction — virtual assistants, operations support, bookkeepers, and similar team members.
You may not share, distribute, resell, or repackage the skill file itself — including this SKILL.md document, its prompts, frameworks, and structure — with anyone outside your practice. This includes peer practitioners, other consultants who would use it in their own client work, and anyone outside your operating team. Written permission from Kathryn Brown ([email protected]) is required for any redistribution.
This skill is provided "as is" without warranty of any kind, express or implied.