Brandedflow client-onboarding

Run Phase 1 (Onboarding) of the branded+Flow Client Delivery Flow. Handles SOW lock, client profile + Airtable IDs, access/asset inventory, automation rails, SKU recording, kickoff, stakeholder map, handoff to research. Does NOT do website, brand, or content work.

install

source · Clone the upstream repo

git clone https://github.com/JenCW/brandedflow

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/JenCW/brandedflow "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.cursor/skills/client-onboarding" ~/.claude/skills/jencw-brandedflow-client-onboarding-ee358d && rm -rf "$T"

manifest: .cursor/skills/client-onboarding/SKILL.md

source content

Client Onboarding (Phase 1)

When to use

A new client has signed and needs to be brought into the system
Re-running onboarding for an existing client (exit conditions need re-verifying)
Running the delivery sequence for a new branded+Flow client

Source of truth

Directive:

foundation/directives/setup-client-onboarding.md

(full HOW for each milestone)

Manifest:

client-delivery-factory/milestones/manifest.json

(canonical milestone list)

Read the directive first. This skill is an index — it does not restate the directive's steps.

The 8 onboarding milestones

#	Milestone
1	Commercial lock — SOW + scope boundaries
2	Client profile + Airtable master + client base IDs
3	Access & asset inventory (DNS, analytics, brand files, logins)
4	Automation rails (MCP/n8n/env verified)
5	SKU / tracks recorded (Foundation / Elevate / add-ons)
6	Kickoff held with outcomes captured
7	Stakeholder map
8	Handoff to Phase 2 (Research)

Exit condition: all 8 green. Then Phase 2 begins.

Inputs needed before starting

Client legal name + display name +
```
client_id
```
(kebab-case)
Signed SOW filed
Primary contact (name, role, email, phone)
Tier purchased: Foundation or Elevate
Add-ons purchased (Lead Radar, social, templates, landing pages)
Kickoff date agreed
DNS registrar access plan
Analytics plan (existing GA4 or new)
Brand files status (existing or build from scratch)

Executors called

MCPs — via

https://brandedflow.onrender.com/run

MCP	Used for milestone
`create-client-folder`	2
`extract-client-info`	2
`add-client-to-airtable`	2
`ensure-airtable-fields`	2, 4
`process-client-intake`	2 (optional)
`upsert-portal-user`	Elevate tier only, 6/8

Post-onboarding checklist

foundation/client-governance/{client_id}/client-profile.json

exists + populated

Master Airtable base has the record; client base has required fields
SOW link in profile
Stakeholder map in profile
Kickoff outcomes in profile
Research handoff payload ready for Phase 2

Out of scope (do NOT do these in onboarding)

Website creation / copy / design → Phase 4
Brand strategy / logo / typography → Phase 3
Research / ICP / target list → Phase 2
Legacy Loop / referral setup → later phase
Anything customer-visible that depends on brand decisions

End of task

State:

END-OF-TASK: Directive [updated/created/N/A]. Self-annealing [applied: <what> / N/A].

"Directive updated" means a file under

foundation/directives/

actually changed. CLAUDE.md edits, memory writes, or code changes do NOT count as directive updates.