Source: frameworks/kit-advisory-onboarding/00-advisory-onboarding-start-here.md

00 — START HERE: Advisory Onboarding Kit

This is the setup and orientation document for the Advisory Onboarding Kit. Read this to understand what it is, what it does, what files it needs, and how to use it.

What This Is

A kit that produces the client-facing onboarding artifacts for an advisory engagement — primarily the roadmap, plus the supporting action plan and mutual-responsibility doc. Derived from a live interview with the practice owner, not from a form or solo recording.

Audience (kit user): The practice owner (advisor) — the person who will deliver the onboarding to their clients. Initially TPC cohort members; eventually Practice Builders cohort and beyond.

Audience (output): The advisory client. The roadmap and supporting artifacts are client-facing.

Format: HTML for the roadmap (visual, client-facing, shared); Markdown templates for the supporting artifacts that the advisor populates.

Lifecycle: One kit run per practice. The output (the roadmap) becomes the advisor's living document with their clients — it leaves the kit once delivered.

What This Produces

Deliverable	Format	Audience	Filename pattern
The roadmap	HTML	Client + advisor + team	`[practice]-advisory-roadmap.html`
Action plan template	Markdown	Advisor populates per client	`[practice]-action-plan-template.md`
Mutual-responsibility doc	Markdown	Advisor populates per client	`[practice]-mutual-responsibility-template.md`

Per-practice variants of all three live in the scoped cohort kit (e.g., kit-tpc-advisory-onboarding/03a-tpc-golden-rob.html), not in this universal kit.

The Two Phases

The kit runs in two distinct phases. Don't compress them.

Phase 1 — Live Interview (input)

The practice owner is interviewed about their advisory onboarding — trigger to completion. Embedded in an already-booked 1:1, not a standalone session. Time budget ~40 min of the slot.

See file 06-advisory-onboarding-interview-protocol.md for the full methodology: when to run it, the pivot move, the question arc, the extraction moves, the hand-off.

Output of Phase 1: Structural capture (not a transcript) — step sequence, named delegation, named tools, first-win mechanic, cadence, real-vs-aspirational separation.

Phase 2 — Roadmap Build (output)

Synthesize the interview output into the client-facing roadmap + supporting artifacts. Apply the universal patterns (file 01), enforce the locked terminology (file 02), produce against the quality bar (file 04).

Output of Phase 2: The three deliverables listed above.

Operating Modes

Mode	Trigger	What It Produces
Mode 1: Create	A practice owner is ready to have their onboarding built. Interview completed.	The roadmap + action plan template + mutual-responsibility template.
Mode 2: Improve	After running the kit, output changed by hand, QC found a gap, or process needs adjustment.	Updated kit files (golden, output skill, quality checklist). See file 05 step "Mode 2."

No Update mode. Once a practice owner has their roadmap, it's their living document — the kit doesn't keep updating it. Subsequent client-specific changes happen in the advisor's own workspace, not in the kit.

What This Does NOT Do

Does NOT produce the deliverable from a solo recording or written submission. Patterns-input ≠ golden-input. See cyp/tpc/lessons-learned/lesson-input-methodology-mirrors-output-2026-05-19.md.
Does NOT bake one member's proprietary content into the kit's spine. The kit captures universal structure; tactical edge stays with the practice. See cyp/tpc/lessons-learned/lesson-special-sauce-protection-2026-05-19.md.
Does NOT replace the cohort sessions where patterns get refined. Gaps surfacing in one interview get closed by asking the group, not by booking a second interview with the same member.
Does NOT produce pre-onboarding artifacts (discovery, presentation, signing process). Pre-onboarding is everything BEFORE the trigger; this kit produces what comes AFTER.
Does NOT cover the package-design layer in depth — the kit references it (see file 01), but the package-architecture build is a separate kit when extracted.

Critical Rule — Client Perspective Test

Every section of every output produced by this kit must pass the client perspective test:

"If the client read this cold, with no advisor present, would it (a) make sense, (b) feel respectful of their time and intelligence, (c) tell them what to expect, what they're committing to, and what they'll get?"

If any section fails any of those three, fix it before delivering. This rule is non-negotiable. The roadmap is the client's living document — not a draft for the advisor to interpret.

File Inventory

#	File	What It Is
00	`00-advisory-onboarding-start-here.md`	This file — orientation, modes, file inventory
01	`01-advisory-onboarding-context.md`	Required inputs, validation rules, patterns the kit enforces, special-sauce protection, audience boundary
02	`02-advisory-onboarding-terminology.md`	Locked vocabulary, forbidden terms, cohort reference cross-link
03	`03-advisory-onboarding-golden-example.html`	Placeholder — first production run that passes QC becomes the golden via Mode 2
04	`04-advisory-onboarding-quality.md`	Quality gate — pass/fail with blocking failures format
05	`05-advisory-onboarding-output-skill.md`	Production skill — how to take interview output and produce the roadmap + supporting artifacts
06	`06-advisory-onboarding-interview-protocol.md`	Consultant methodology — how to run the live interview that produces the kit's input

Total: 7 files. Extended kit (vs. 6-file standard) because the kit involves a live human session that needs its own methodology file.

Relationship to Other Kits

kit-tpc-advisory-onboarding/ (scoped cohort overlay) — holds the actual TPC member goldens (Rob's roadmap, Bev's roadmap). References this kit for all methodology; does not duplicate.
kit-builder/ — produced this kit via Mode 1. Future improvements run through kit-builder Mode 2.
kit-change-communication/ — adjacent kit, similar two-beat structure with consultant methodology file. Different output (communication artifacts vs. onboarding roadmap), shared structural pattern.
kit-blueprint/ — client-facing HTML structure reference. Different content (project status vs. onboarding journey), shared visual-design principles.

Self-Improvement Loop

After running this kit, ask:

Did I change anything in the output by hand? → If yes, update file 03 (golden) + file 05 (output skill) via Mode 2.
Did QC miss something I caught? → Update file 04 (quality) — add the check + add to common failure modes.
Is there something the kit should do that it doesn't? → Update file 05 (output skill) or file 06 (interview protocol).

Every manual fix becomes a kit fix. If you fixed it by hand, tell the kit so you never fix it by hand again.

File Location

advisory-os-vault/content/frameworks/kit-advisory-onboarding/
    00-advisory-onboarding-start-here.md          (this file)
    01-advisory-onboarding-context.md
    02-advisory-onboarding-terminology.md
    03-advisory-onboarding-golden-example.html
    04-advisory-onboarding-quality.md
    05-advisory-onboarding-output-skill.md
    06-advisory-onboarding-interview-protocol.md

Confirm Understanding Before Executing

Before any production run, the kit confirms its understanding with the practice owner:

"Here's what I'm going to do — interview you about your advisory onboarding, capture the structure, build the client-facing roadmap from what you give me. Here's what I'm working from: your reference data, the cohort patterns, the interview output we'll produce together. Does this match what you want, or am I missing something?"

Don't start production until the owner confirms. Wrong output that took 10 minutes is worse than a 30-second confirmation upfront.