The standard client delivery process — from kickoff to QBR — with the skills we have, the outputs we ship, and the skills we still need to build.
Onboarding through ongoing execution and quarterly strategy. The first three meetings + Creative Brief + QBR need dedicated skills built.
| ⏱ 2-Week Trial · Day 0 → Day 14 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Pre-Signing | Day 0 — Setup | Client Meetings | Day 9–10+ · Channel Execution & Reporting | Quarterly | ||||||
|
Start →
Verbal Client Approval
Confirm
|
S2
Kickoff Scheduling
Schedule
Same day if signed before 3pm ET · otherwise next business day
Drea → Rachelle via #mh1-meeting-scheduler
S3
Systems Access Request
Connect
Now: Manual request via email
Future: Client grants access via portal
+ Brand & Visual Guidelines
|
Day 1–3
Kickoff
Call Discover
EmailsPost-KOC
|
Day 4–7
Business Review
Analyze
EmailsPost-BizRev
|
Day 7–9
Channel Plan
Approve
EmailsPost-Ch Plan
|
Day 9+
Channel Execution
Execute
|
Day 10+
Channel Reporting
Inform
|
Quarterly
Quarterly Business Review (QBR)
Grow
|
|||
|
|
||||||||||
|
|
|
|
|
|
|
|
|
|||
|
↳ Trigger: Client verbal yes
1Post to #ai-deal-contracts
2Draft + Send Contract
Slack post in #ai-deal-contracts
Contract sent to client
|
↳ Trigger: Contract received
S1 ·Contract Signed
1Billing Setup Initiated
2Follow Up on Contract + Billing
3Create Slack Channels
Signed contract
Billing confirmed
#proj- & #cust- channels created
↳ Trigger: Billing complete
S2 ·Kickoff Scheduling
3Kickoff Call Scheduled
4Kickoff Invite Includes
60-min slot confirmed
2–4 business days out
↳ Trigger: Portal email sent
S3 ·Systems Access Request
5Client Completes Portal
6CMO Confirms Access
All platforms connected
MH2 ingestion started
↳ Trigger: KOC scheduled
S4 ·Internal Alignment
7CMO + Pod Assigned
8Internal Handoff Summary
9Share Report in Slack
10Team Prep (Non-Negotiable)
|
5 minIntroductions + roles
45 minClient business context — priorities, challenges, success definition
5 minMH-1 approach — next 2 weeks, how we operate, comms cadence
3 minData + access requirements — platforms, assets, dependencies
2 minNext steps + expectations — asks, timeline, ownership
Post-Call · Platform Access
|
|
|
|
|
|
|||
| Access requested at signing via Welcome Email + Customer Portal |
Access requirements discussed + documented |
Inputs
MH2
Audited
|
Primary Channels
confirmed in scope alignment · planned, executed & reported
expands
|
All Active Channels New channels proposed based on performance & opportunity | ||||||
The data MH2 ingests, scores, and surfaces at every phase — from raw customer records to executive KPIs, creative strategy, and optimization logs.
9 standardized delivery skills + 12 client-driven asks (Swimply · Mr. Christmas). These are the gaps between what we deliver and what's automated.
All existing skills available to run for any client. Click any category to expand.