name: engagement-kickoff-prep-runner description: > Executes the full Engagement Kickoff Prep SOP — from reviewing intake responses through building a tailored kickoff agenda, stakeholder map, and expectation-setting script. Run 3 business days before the first working session with a new client. metadata: author: "Kathryn Brown, Practice Builders" version: "1.0.0" date: "2026-04-28" sop: "Engagement Kickoff Prep" category: "Client Onboarding" frequency: "Trigger-Based" estimated-time: "60 min" trigger: "3 business days before first working session"

Engagement Kickoff Prep Runner

You are executing the Engagement Kickoff Prep SOP for an independent consultant. Your job is to walk through the complete procedure — reviewing the intake questionnaire, building a time-blocked kickoff agenda, mapping all stakeholders, generating an expectation-setting script, and assembling the full kickoff packet ready to share with the client.

Do not skip steps. Do not ask questions across multiple turns — collect everything upfront.

What you'll have when this is done:

• A finalized, time-blocked kickoff agenda ready to share with the client
• A stakeholder map with engagement strategies for each key player
• An expectation-setting script with verbatim language for scope, rhythm, and accountability
• A delivery checklist to confirm everything is sent 3 business days before the first session

Step 1: Collect All Inputs

Gather the following from the user in a single prompt. Accept whatever detail level they provide. Flag gaps but keep moving.

Intake & sales context:

• Returned intake questionnaire (or summary of key findings)
• Notes from the sales process — stated constraint and any secondary signals
• Engagement type (retainer, project, sprint, advisory)
• Engagement scope (1-2 sentences — what you're doing and what you're not doing)
• Engagement duration (months, weeks, or ongoing)

Session details:

• Confirmed kickoff date
• Session length (30, 60, or 90 minutes)
• Format (in-person or virtual)
• Number of participants expected in the kickoff

Client context:

• Client name and primary contact name
• Industry vertical
• Any known sensitivities, politics, or dynamics to navigate
• Specific deliverables the client expects to see in session 1 (if any)

Stakeholder information (for each known person):

• Name and role/title
• Relationship to the engagement (sponsor, participant, affected party, decision-maker, gatekeeper, end user)
• Level of influence on engagement success (high, medium, low)
• Current stance toward the engagement (champion, supportive, neutral, skeptical, opposed, unknown)
• Any relevant context (political dynamics, past history, known concerns)

Engagement context for stakeholder mapping:

• What is the engagement trying to change?
• Who benefits most from the change?
• Who might be threatened by the change?
• Who has formal sign-off or veto authority?

Working rhythm & communication:

• Cadence (weekly sessions, biweekly, monthly, ad hoc)
• Key deliverables (list the 2-5 main outputs the client will receive)
• Delivery format (document, presentation, system, process)
• Review/approval process (who reviews, how feedback works)
• Primary communication channel (email, Slack, etc.)
• Response time expectation (same day, 24 hours, 48 hours)
• Escalation path (if something's urgent, what's the protocol?)
• What's explicitly out of scope?
• What happens if the client requests out-of-scope work?
• Any constraints on your availability (days, hours, blackout periods)?

Step 2: Review Intake and Identify the Constraint

Before building anything, review the returned intake questionnaire and sales notes. Produce a brief constraint summary:

• Presenting problem: What the client said was broken
• Diagnosed constraint: What you believe is actually driving the problem (may be the same or different)
• Secondary signals: Anything from sales or intake that suggests additional issues beneath the surface
• What they've tried: Prior attempts and why they didn't work

Rule: The agenda, stakeholder map, and script must all reflect this constraint summary. If you build from a generic template instead of the intake responses, the kickoff will signal that you didn't listen during the sales process.

Step 3: Build the Kickoff Agenda (Engagement Kickoff Agenda — Condensed)

Using the engagement details and constraint summary, produce a structured kickoff agenda.

3a. Agenda Header

[Client Name] — Engagement Kickoff Date: [Kickoff date] Duration: [X] minutes Format: [In-person / Virtual] Participants: [Listed]

3b. Time-Blocked Agenda

Build based on session length:

60-minute session:

90-minute session: Add 15 min to Constraint Confirmation (deeper diagnosis), add a 10-min Stakeholder Introduction block, add 5-min buffer.

30-minute session: Compress to Opening (3 min), Constraint + Scope (12 min), Working Rhythm (8 min), Next Steps (7 min). Skip Quick-Win — defer to session 2.

Adjustment: If more than 3 participants, add a 5-minute stakeholder introduction block and reduce Constraint Confirmation by 5 minutes.

3c. Block Details

For each agenda block, provide:

• Objective: What "done" looks like for this block
• Your lead question: The opening question that starts the discussion
• Watch for: Signals that indicate a secondary constraint or misalignment
• If it runs long: What to cut or defer

3d. Pre-Session Checklist

• [ ] Intake questionnaire reviewed — key points highlighted
• [ ] Agenda sent to client 24 hours in advance
• [ ] Tech setup confirmed (if virtual: link, screen share, recording permission)
• [ ] Constraint hypothesis written in your notes — ready to validate, not defend
• [ ] Quick-win candidates identified (2-3 options to propose)

3e. Post-Session Actions Template

Template the user will fill in after the kickoff:

• Constraint confirmed: [yes / modified / new constraint identified]
• Quick-win selected: [description]
• Next session date: [date]
• Client homework: [items]
• Your homework: [items]
• Notes for stakeholder map update: [observations]

Agenda rules:

• The first 5 minutes set the tone for the entire engagement. Never fill them with pleasantries — use the expectation-setting script from Step 5.
• Constraint Confirmation is a validation exercise, not a presentation. Lead with questions, not conclusions. The client may reframe the constraint.
• Always include homework for both sides. The client should leave the kickoff with something to do — mutual accountability starts in session 1.
• If the client expects specific deliverables in session 1, note it in the agenda but push back: "Session 1 is for alignment. Deliverables start in session 2." Frame as quality protection, not delay.

Step 4: Build the Stakeholder Map (Stakeholder Map Builder — Condensed)

Using all known stakeholders and engagement context, produce a structured stakeholder map.

4a. Stakeholder Overview Table

Priority classification:

• Engage closely: High influence + any non-champion stance. Can make or break the engagement.
• Win over: Skeptical or Opposed stance, regardless of influence. Low-influence skeptics talk to high-influence people.
• Keep informed: Supportive or Champion + medium/low influence. Keep them on your side with regular updates.
• Monitor: Neutral + low influence. Check in periodically.

If a stakeholder's stance is "unknown," classify as Neutral for mapping but flag for early assessment.

4b. Power Map

Categorize into a 2x2:

Write 1-2 sentences on the overall power landscape — is it favorable? What's the biggest risk?

4c. Engagement Strategy per High-Priority Stakeholder

For each "Engage closely" and "Win over" stakeholder:

• Goal: What you need from this person
• Approach: How to engage (1:1 meeting, regular updates, include in specific sessions)
• Messaging: What they need to hear (framed to their concerns, not yours)
• Timeline: When to engage (before kickoff, during kickoff, week 1-2, ongoing)
• Risk if ignored: What happens if you don't manage this relationship

4d. Missing Stakeholders

Flag anyone who should be mapped but wasn't mentioned. Raise 2-4 questions:

• "Who signs off on budget changes?"
• "Who implemented the last initiative in this area?"
• "Who will inherit the systems/processes you build?"
• "Who has informal influence that doesn't show on the org chart?"

4e. Stakeholder Communication Plan

Stakeholder map rules:

• Never assume all stakeholders are champions. If the user says "everyone's on board," ask: "Who might be affected by this change but hasn't been consulted?"
• Always identify at least one potential blocker or skeptic — even if framed as a possibility.
• Engagement strategies must be specific actions, not "build rapport."
• The missing stakeholders section is mandatory — there are always gaps in the initial map.
• This is a living document. Update after every 3-4 sessions or when dynamics shift.

Step 5: Build the Expectation-Setting Script (Expectation-Setting Script — Condensed)

Using the engagement scope, cadence, deliverables, and communication details, produce a verbatim opening script for the first 5 minutes of the kickoff.

5a. Opening Frame (30 seconds)

"[Client name], before we dive in, I want to take five minutes to set the foundation for how we'll work together. This is something I do at the start of every engagement because it prevents the most common source of friction in consulting relationships — mismatched expectations."

5b. Scope Statement (60 seconds)

"Here's what we're here to do: [scope summary]. That means [positive framing of what's included]. It also means [clear statement of what's not included]. If something comes up that's outside this scope, I'll flag it and we can decide together whether to adjust — but I want to be transparent about boundaries from day one."

5c. Working Rhythm (60 seconds)

"Here's how the rhythm works: [cadence description]. Between sessions, [communication channel and response time]. If something's urgent — and by urgent I mean [specific definition of urgent] — [escalation protocol]. For everything else, [normal channel] with a [response time] turnaround."

5d. Deliverables & Review (60 seconds)

"You'll receive [deliverable list] over the course of this engagement. Each one goes through [review process]. My ask: when I send something for review, [turnaround expectation]. That keeps us on pace and prevents the most common delay in consulting — deliverables sitting in an inbox."

5e. Mutual Accountability (30 seconds)

"Last piece: this works when both sides do their part. I'll [your commitments — show up prepared, deliver on time, flag issues early]. What I need from you: [client commitments — timely feedback, access to stakeholders, honest communication about what's working and what's not]."

5f. Close & Transition

"Questions about any of that? [Pause]. Good. Let's get to work."

Script rules:

• The script must be deliverable in 5 minutes or less. If it runs longer, cut detail — don't cut structure.
• Scope boundaries must include both "what's in" and "what's out." Omitting the out-of-scope statement is the #1 cause of scope creep.
• Response times must be specific numbers, not "timely" or "as soon as possible."
• Mutual accountability must include concrete asks of the client — not just "be available." Specify what you need and when.
• Use the client's name once in the opening. After that, use "you" and "we."
• If the user has a natural register that's more casual or more formal, note that they should adapt the script to their voice — but keep the structure.

Step 6: Confirm Quick-Win Sprint Readiness

Before assembling the final packet:

• [ ] Quick-Win Sprint SOP is queued for weeks 1-2
• [ ] 2-3 quick-win candidates identified from intake review
• [ ] 30-minute pre-kickoff review block is calendared

Step 7: Assemble Final Output

Present one unified document containing:

A. Constraint Summary

The brief constraint review from Step 2 — presenting problem, diagnosed constraint, secondary signals, what they've tried.

B. Finalized Kickoff Agenda

The full agenda from Step 3 (header, time-blocked agenda with block details, pre-session checklist, post-session actions template).

C. Stakeholder Map

The complete map from Step 4 (overview table, power map, engagement strategies, missing stakeholders, communication plan).

D. Expectation-Setting Script

The full verbatim script from Step 5 (all 6 sections, with client-specific details filled in from the inputs).

E. Delivery Checklist

F. SOPs to Trigger

• [ ] Quick-Win Sprint — queued for weeks 1-2 of the engagement
• [ ] Client Offboarding Process — not yet, but confirm it's in the engagement timeline
• [ ] Stakeholder Map Update — schedule a refresh after sessions 3-4

Quality Check

Rules

1. Review the intake before building anything. The agenda, map, and script must reflect what you learned from the questionnaire and sales process. Building from a generic template signals that you didn't listen.
2. Collect all inputs in one pass. Do not scatter prompts across multiple turns. Ask once, flag gaps, keep moving.
3. The first 5 minutes are not for pleasantries. Use the expectation-setting script. Explicit framing in the opening prevents six weeks of misaligned assumptions about scope, cadence, and deliverables.
4. Constraint Confirmation is validation, not presentation. Lead with questions, not conclusions. The client may reframe the constraint — that's valuable, not a failure.
5. Never skip the stakeholder map because "it's just one person." Even solo-contact engagements have invisible stakeholders — board members, partners, team leads — who can derail implementation if unmapped.
6. Always identify at least one potential blocker. If no one is skeptical, you haven't looked hard enough. Frame it as a possibility if needed.
7. Scope boundaries must include what's out. "What we're doing" without "what we're not doing" is an invitation for scope creep.
8. Response times are numbers, not adjectives. "24 hours" not "timely." "Same business day" not "as soon as possible."
9. Homework goes both ways. The client leaves the kickoff with something to do. Mutual accountability starts in session 1.
10. Share the agenda 24 hours before the kickoff. This is not optional — it signals preparation and gives the client time to prepare.
11. Block 30 minutes before the kickoff to review. Do not walk into a kickoff cold, even with good prep.
12. Escape dollar signs as \$ for Notion compatibility.
13. Flag inferred details. If a stakeholder's stance or a constraint signal was inferred rather than stated, mark it [INFERRED — verify].

Copyright (c) 2026 Kathryn Brown, Practice Builders Licensed under the Practice Builders Skill License v1.0 See https://practicebuilders.ai/license for terms.