Blueprint Mapping Session — Context & Inputs
Required Inputs
Mode 1: Pre-Session (Advisor Prep Doc)
| Input | Priority | Source | Description |
|---|---|---|---|
| Intake questionnaire answers | Required (but skeleton works without) | Paperform submission | Client's answers to the pre-session intake |
| Calendly booking data | Required | Calendly confirmation | Session date, time, client name, company, website, social platform, areas of focus (free-text from booking) |
| Client background | Required | LinkedIn, prior relationship, reference files | Company, role, certifications, known history with Kathryn |
| Prior relationship context | If available | business-aos reference files, email history | Past engagement details, outcomes, rapport notes |
Mode 2: Post-Session (Summary Email + 90-Day Blueprint)
| Input | Priority | Source | Description |
|---|---|---|---|
| Session transcript or detailed notes | Required | Zoom recording transcription or advisor notes | Ground truth for what was discussed, decided, committed to |
| Decisions made | Required | Extracted from transcript/notes | Which direction chosen, which offer defined, why this path over others |
| First action committed to | Required | Extracted from transcript/notes | The specific thing the client agreed to do within 48 hours |
| Resources discussed | If available | Session conversation | Tools, templates, frameworks, references the advisor recommended |
| Intake answers (for reference) | Required | Paperform submission | Cross-reference to validate that deliverables address what the client came in wanting |
Input Validation Rules
Pre-Session
- If intake answers haven't arrived by session day: build prep doc from Calendly data + known background. Flag gaps.
- If no prior relationship exists: note "new relationship" — adjust session arc to include more rapport-building in Block 1.
- Never fabricate client details. If years in industry, revenue, or team size are unknown, leave them out.
Post-Session
- Use the transcript, not a summary or recap. If only notes are available, flag it and treat every factual claim as advisor's recollection, not verbatim.
- Every claim in the deliverables must trace to something the client said in the intake or session.
- Every decision in the 90-day blueprint must be something the client committed to during the session — not the advisor's recommendation that wasn't confirmed.
Content Filtering Rules
What Goes in Client-Facing Deliverables
| Content | Written Summary | 90-Day Blueprint |
|---|---|---|
| Session highlights / key moments | Yes | No |
| Decisions made and why | Yes (narrative) | Yes (structured) |
| The chosen direction | Yes (mentioned) | Yes (full section) |
| The defined offer | Yes (mentioned) | Yes (full section) |
| 90-day timeline with actions | No (referenced) | Yes (full section) |
| First action | Yes (reminder) | Yes (prominent callout) |
| Resources | Yes (listed or attached) | Yes (section) |
| What they'll receive | Yes (list deliverables) | No |
| Paths NOT chosen | No | No |
| Advisor's internal strategy notes | No | No |
| Constraint language or AOS methodology | No | No |
What Stays in the Advisor's Prep Doc Only
- Strategic angles and scenario planning
- Facilitation notes and time-boxing reminders
- Risk assessments about the client's direction
- Potential conversion to Sprint/OS (never surfaces in client deliverables)
Tone Rules
These apply to all client-facing BMS deliverables. Non-negotiable.
- Peer advisory, not coaching. Kathryn is a trusted advisor talking to a business owner she respects. Not a coach encouraging a coachee. Direct, warm, specific.
- No selling. The client already paid. The deliverables don't mention Advisory OS, Deploy Sprint, or "working together further." If it's the right fit, they'll come back.
- No internal jargon. No "constraint," "CPM," "deploy chain," "build" (in the AOS sense), "upstream/downstream," "GPS," "Mode."
- State facts, not interpretations. "You're selling the business and exploring AI services" — not "You're at a pivotal transition point in your career."
- Respect intelligence. The client knows their business. Don't over-explain why their own decisions matter.
- Do not sound like AI. No "That's exactly the kind of clarity that makes this work." No inspirational reframing. If it sounds like a LinkedIn post about leadership, delete it.
- Specifics over adjectives. Warmth comes from referencing real things the client said, not from adding "great" or "exciting" to generic observations.