Blueprint Mapping Session — Start Here
What This Kit Does
This kit runs the full lifecycle of a Blueprint Mapping Session (BMS) — from pre-session intake through session facilitation to post-session deliverable production. One client, one session, one 90-day plan.
Production path: Intake answers received → Build advisor prep doc → Facilitate 90-minute session → Produce written summary email → Produce 90-day blueprint → Deliver to client.
What a Blueprint Mapping Session Is
A $500 standalone 90-minute paid session. The advisor (Kathryn) helps a business owner create a clear 90-day action plan. The client leaves with one testable offer and a concrete plan to take it to market.
This is NOT an ongoing engagement. The session happens once. The deliverables ship once. No weekly cadence, no builds, no deploy cycle.
When to Use This Kit
When a client books a Blueprint Mapping Session through Calendly. The trigger is: Calendly booking confirmed + payment received.
Do not use this kit for:
- Ongoing Advisory OS client sessions (use the weekly processing workflow)
- Systems Diagnostics (free, different structure)
- Deploy Sprints ($3,500, bounded project with multiple sessions)
- Internal sessions or cowork blocks
What It Produces
| Output | Format | Destination | When |
|---|---|---|---|
| Advisor session prep doc | Markdown | business-aos/khb-aos/projects/blueprint-sessions/[client]/ | Before the session |
| Written summary email | HTML (Gmail-ready) | business-aos/khb-aos/projects/blueprint-sessions/[client]/ | Within 24 hours after session |
| 90-day blueprint | HTML (standalone) | business-aos/khb-aos/projects/blueprint-sessions/[client]/ | Within 48 hours after session |
The client also receives a session recording (Zoom handles this — not part of this kit).
Operating Modes
| Mode | Trigger | What It Produces |
|---|---|---|
| Mode 1: Pre-Session | Intake answers received | Advisor prep doc populated with client context, session arc, strategic angles, scenarios |
| Mode 2: Post-Session | Session transcript or notes available | Written summary email + 90-day blueprint HTML |
| Mode 3: Improve This Kit | Manual changes were made to outputs, QC missed something, or process needs updating | Updated kit files |
Mode 1 — Pre-Session
Inputs: intake questionnaire answers, client background (company, role, known history), any prior relationship context. Output: advisor prep doc with populated session arc.
If intake answers haven't arrived, build the prep doc skeleton from whatever is known (Calendly booking info, prior relationship, LinkedIn profile). The skeleton still works — intake answers make it better but aren't blocking.
Mode 2 — Post-Session
Inputs: session transcript or detailed notes, decisions made during session (which path, which offer), first action committed to, resources discussed. Outputs: written summary email + 90-day blueprint.
Mode 3 — Improve This Kit
After each BMS: Did I change anything in the output by hand? → Update golden example + output skill. Did QC miss something? → Update quality checklist. Should the kit do something it doesn't? → Update relevant file.
What This Kit Does NOT Do
- Replace the weekly advisory workflow. BMS clients are not AOS clients.
- Sell Advisory OS in the deliverables. If the client is a fit for ongoing work, they'll come back. The session stands on its own.
- Produce build cards, deploy chains, prework sections, or any ongoing-engagement structure.
- Send emails or schedule calendar events. It drafts and presents for review. The advisor sends.
- Fabricate details the client didn't provide. Every claim in a deliverable must trace to what the client said in the intake or session.
Relationship to Other Kits
| Kit | Relationship |
|---|---|
Blueprint (kit-blueprint/) | Different product. kit-blueprint produces ongoing progress dashboards for AOS clients. This kit produces a one-time 90-day action plan. They share CSS design language but not structure. |
Post-Session Production (kit-post-session-production/) | Different workflow. Post-session production is for ongoing advisory clients (transcript → CPM → master plan → email). This kit has its own simpler post-session flow. |
Advisory Client Email (kit-client-email/) | Voice reference. The BMS summary email follows the same voice rules (peer advisory, direct, warm) but uses a simpler structure since there's no ongoing engagement to prep for. |
Session Recap (kit-session-recap/) | Voice reference for email tone and anti-patterns. |
New Client Kit (kit-new-client/) | Not triggered by BMS. Only runs if the client converts to an ongoing engagement after the session. |
Relationship to Product Ladder
The BMS sits between the free Systems Diagnostic and the $3,500 Deploy Sprint. It's a standalone paid session — not a stepping stone that assumes conversion. Some BMS clients will convert to Sprint or Advisory OS. Most won't. The deliverables don't mention other offers.
File Inventory
| # | File | Purpose | When to Use |
|---|---|---|---|
| 00 | 00-blueprint-mapping-session-start-here.md | This file — orientation, modes, scope | Start here every time |
| 01 | 01-blueprint-mapping-session-context.md | Required inputs, validation rules, content filtering, tone rules | Before every run — confirm inputs available |
| 02 | 02-blueprint-mapping-session-terminology.md | Locked vocabulary — what clients see vs. what stays internal | Reference throughout |
| 03 | 03-blueprint-mapping-session-golden-example.md | Reference output — the standard to match | Study before producing deliverables |
| 04 | 04-blueprint-mapping-session-quality.md | QC checklist — point-scored, pass/fail | Run after every draft, before presenting |
| 05 | 05-blueprint-mapping-session-output-skill.md | Production skill for both client deliverables (summary email + 90-day blueprint) | Follow for post-session production |
| -- | bms-facilitation-SKILL.md | Session facilitation guide — the 5-block arc, questions, scenario handling | Use during session prep and live facilitation |
Total: 7 files (standard kit + facilitation SKILL).