EF 30-Day Kickoff Runbook v0.1
Filed: 2026-05-25 by Mercator
For: Tapt-internal execution + EF-side reference. Per-day checklist with actors, dependencies, and risk thresholds.
Supersedes operational specificity in: EF_30_DAY_KICKOFF_v0.1.md (Mycelia's narrative version remains canonical for tone + client-facing framing; this runbook is the execution layer).
Aligned with: Pricing v0.8 (bounded engagement, $10K setup includes M1, declining monthly from M2), Media Plan v0.1 (Moderate, Pinterest-first 40%), Model Profile UI Spec (Phase 1 reference-based), SaaS Stack Scout v0.1.
How to use this document
- Day numbers = days from sign (Day 0 = contract executed).
- Actor codes:
TAPT(any Tapt-side agent),MYC(Mycelia),FAB(Faber),PRA(Praetor),MER(Mercator),LUM(Lumen),RYAN(Ryan),EMR(Emerson),M1/M2(models),AUTO(automated/platform),3P(third-party — e.g., Klaviyo, Shopify support). - State-machine dependencies explicit in "blocks" + "blocked-by" fields. Do not jump ahead — sequencing is real.
- Risk thresholds trigger escalation per the §Escalation Matrix below.
- Check-boxes are operational. Tick when verifiably done; surface missed boxes at the next check-in.
Pre-Day-0 checklist (must be true BEFORE sign)
Run-through with Ryan during reveal call OR in pre-sign close-out. If any fails, do NOT sign until resolved.
| Item | Actor | Verifiable how | Status |
|---|---|---|---|
| Contract package executed (MSA + License + DPA + SLA + SOW) | PRA + RYAN + Tapt counsel + EF counsel |
Signed PDF in convivium/clients/emerson_fry/contracts/executed/ |
[ ] |
| Likeness-use addendum drafts ready for M1 + M2 + EMR | PRA |
Drafts in convivium/clients/emerson_fry/contracts/likeness/ |
[ ] |
| Tapt's IP DD complete + filed | PRA |
EF_IP_DUE_DILIGENCE_v0.1.md ✓ done |
[x] |
| RYAN confirmed billing-owner role on new GCP project (in concept) | RYAN | Verbal/email confirmation | [ ] |
| RYAN listed all 3rd-party accounts EF currently has + admin access for each | RYAN | Inventory captured (see EF_SAAS_STACK_SCOUT_v0.1.md for prompt list) |
[ ] |
Slack #ef-active channel created on Tapt-side |
TAPT (Billy) |
Channel exists; webhook URL captured | [ ] |
| Domain decision committed (subdomain on ef vs. neutral) | RYAN | Domain string recorded → see Day 3 | [ ] |
| EMR aware she'll need ~2hr/wk for voice approval | RYAN → EMR | RYAN confirms | [ ] |
| Founding-member terms (Cup of Jo / mom edit / lifestyle press relationships preserved) acknowledged in writing | MYC + RYAN |
Documented in SOW or side-letter | [ ] |
If 9/9 = true → green-light Day 0.
Day-by-day runbook
DAY 0 — SIGN DAY
| # | Action | Actor | Blocks | Blocked-by | Hours | Risk if missed |
|---|---|---|---|---|---|---|
| 0.1 | Contract executed; counter-signed PDF circulated | PRA + RYAN |
All Day 1+ work | Pre-Day-0 checklist | 0.5 | No engagement — game-over until resolved |
| 0.2 | Welcome email sent to RYAN + EMR with what-happens-next + Slack channel link + Day 1 calendar invite | MER (drafts) → Billy sends from real account |
RYAN/EMR onboarding awareness | 0.1 | 0.25 | Trust erosion if no immediate contact |
| 0.3 | #ef-active Slack channel populated with kickoff doc + 30-day calendar |
TAPT (Billy) |
Day-1+ comm cadence | 0.1 | 0.25 | Comms scatter across email + IM |
| 0.4 | Internal kickoff sync (TAPT side): MYC + FAB + PRA + MER + LUM align on 30-day plan + role boundaries | MYC (leads) |
Day 1+ execution clarity | none | 1.0 | Confusion / dropped balls in Week 1 |
| 0.5 | EF folder snapshot taken: contracts, audits, dashboard frozen as convivium/clients/emerson_fry/snapshots/2026-MM-DD-sign-day/ |
MER |
Future change-tracking | 0.1 | 0.25 | Can't reconstruct sign-day baseline later |
Day 0 exit criteria: Contract signed, welcome sent, Slack live, internal sync done. ~2hr Tapt-side total.
DAY 1 — CREDENTIALS + INFRASTRUCTURE PRIMER
| # | Action | Actor | Blocks | Blocked-by | Hours | Risk if missed |
|---|---|---|---|---|---|---|
| 1.1 | Onboarding-materials packet sent to RYAN (PDF: what's coming Days 1-30 + per-day deliverables EF-side + Tapt-side) | MER (drafts) → MYC reviews → Billy sends |
RYAN/EMR engagement prep | 0.4, 0.5 | 1.0 | RYAN feels in the dark, anxiety grows |
| 1.2 | Credentials sheet sent (1Password vault invite OR encrypted file): platform admin login, dashboard URLs, internal contact tree | FAB (generates) → PRA (reviews for data-share compliance) → MYC sends |
Day-2 GCP work | 0.1 | 0.5 | Day 2 blocked |
| 1.3 | Day-1 check-in call w/ RYAN (~30min): walk through onboarding packet, confirm timeline, surface concerns | MYC + Billy + RYAN |
Week-1 trust + alignment | 1.1 | 0.75 | Misalignment compounds; Week 1 drift |
| 1.4 | EMR-side prep email: brief on the curation pattern + voice-approval flow + ~2hr/wk commitment + introducing TAPT | MYC (drafts founder-voice) → RYAN approves → Billy sends to EMR |
Days 8+ onboarding session | 1.1 | 0.5 | EMR feels excluded; voice authority dispersed |
| 1.5 | Slack #ef-active first welcome-message + thread for daily ops + emoji-react conventions documented |
TAPT (Billy) |
Ongoing comm cadence | 1.3 | 0.25 | Slack becomes noisy/unfollowed |
Day 1 exit criteria: RYAN has packet + credentials + had call. EMR briefed. ~3hr Tapt-side total. RYAN ~1hr.
Risk threshold: If Day-1 call doesn't happen by EOD, escalate to MYC who calls Billy who calls RYAN directly.
DAYS 2-3 — GCP + DOMAIN MIGRATION
| # | Action | Actor | Blocks | Blocked-by | Hours | Risk if missed |
|---|---|---|---|---|---|---|
| 2.1 | New GCP project created in EF's Google org (or new Google org if EF doesn't have one) | RYAN (provisions) + FAB (guides) |
All API integrations | 1.2 | 1.5 | Cascade-blocks Days 4-7 |
| 2.2 | Billing account confirmed: RYAN = billing-owner; TAPT = collaborator role only | RYAN + FAB |
Cost-transparency commitment | 2.1 | 0.25 | TAPT pays for EF's APIs (broken model) |
| 2.3 | Anthropic API key + Gemini API key provisioned in RYAN's accounts | RYAN + FAB |
Generation features post-migration | 2.1, 2.2 | 0.75 | Generation calls fail / hit Tapt's keys / cost-leak |
| 2.4 | IAM roles configured: TAPT agents get Editor on platform compute resources only; NO data-warehouse / billing access |
RYAN + FAB + PRA (audits) |
DPA compliance | 2.1 | 0.5 | Compliance gap; data-access overreach risk |
| 2.5 | Cloud Storage bucket for EF-owned model-reference imagery created; permissions: TAPT read-only initially, EF own | RYAN + FAB |
Day-19+ Model Profile production-use | 2.1 | 0.5 | Likeness assets in unclear ownership |
| 3.1 | Platform code migrated to EF's GCP project. App deployed; smoke-test passes | FAB |
Domain switch (3.2); all future work | 2.1-2.4 | 3.0 | Platform demo-only until resolved |
| 3.2 | Domain switch executed per RYAN's choice: marketing.emersonfry.com OR keep ef.taptstudio.com pointed at new infra OR brand-neutral |
FAB + RYAN (DNS) |
All client-facing URLs | 3.1 | 1.0 | URL confusion; broken deck links |
| 3.3 | TLS cert provisioned on new domain; Basic Auth removed (or password rotated for EF-team-only access) | FAB |
Production-ready surface | 3.2 | 0.5 | Cert errors visible to EMR/RYAN |
| 3.4 | Old ef.taptstudio.com env: data exported, env paused (NOT deleted — kept as backup until Day 30) |
FAB |
Data recovery option | 3.1, 3.2 | 0.5 | Lose ability to roll back |
Days 2-3 exit criteria: Platform runs on EF's GCP. Domain switched. TLS green. API keys EF-owned. ~9hr Tapt-side total. RYAN ~3hr.
Risk threshold: If GCP provisioning (2.1) not done by EOD Day 2, escalate FAB → MYC → Billy → RYAN; if not resolved by EOD Day 3, kickoff timeline slips 2 days and all downstream actions push.
DAYS 4-5 — KLAVIYO + SHOPIFY
| # | Action | Actor | Blocks | Blocked-by | Hours | Risk if missed |
|---|---|---|---|---|---|---|
| 4.1 | Klaviyo API key + read+write scopes provisioned in RYAN's Klaviyo account | RYAN + FAB |
Email program work | 3.1, 3.2 | 0.5 | No email automation |
| 4.2 | Klaviyo existing-flows audit: read all active flows; document baseline (open/click/revenue per flow) for Day-22 strategic review | FAB (reads) + MYC (interprets) |
Day-22 strategic review baseline | 4.1 | 1.5 | No before/after comparison possible |
| 4.3 | Klaviyo draft-surface integration: platform can push to Klaviyo as drafts (NOT auto-send); RYAN approves in Klaviyo UI before send | FAB |
Curation pattern integrity | 4.1 | 2.0 | Auto-send risk → brand-voice betrayal |
| 4.4 | Activate dormant Klaviyo SMS (per audit): create opt-in surface on site + first welcome SMS draft | FAB (technical) + MYC (copy) + RYAN approves |
SMS revenue line | 4.1, 4.3 | 1.5 | Misses one of the highest-leverage early levers (per Lumen research: SMS = up to 31% of online rev for fashion top-performers) |
| 5.1 | Shopify private app created with read+write to catalog + customers + orders | RYAN + FAB |
Catalog refs + attribution | 3.1 | 0.5 | Generated content can't reference real product/inventory |
| 5.2 | Shopify catalog pulled into platform: product titles, descriptions, images, prices, inventory levels, tags | FAB + AUTO |
Content generation realism | 5.1 | 1.0 | Generated content references stale/wrong product |
| 5.3 | Shopify webhook configured: order.created → platform memory layer (for revenue attribution) | FAB |
Day-15+ attribution data | 5.1, 5.2 | 0.75 | No revenue attribution back to channel |
| 5.4 | Shopify product feed for Google Merchant Center: verified or established | RYAN + FAB |
Day-7 GMC integration | 5.1 | 0.5 | Shopping ads can't run |
Days 4-5 exit criteria: Klaviyo + Shopify both wired. Klaviyo SMS opt-in live. ~8hr Tapt-side total. RYAN ~1.5hr.
Risk threshold: If Klaviyo draft-surface (4.3) isn't working by EOD Day 5, defer Day-11 active curation by ≥2 days. Flag in #ef-active immediately.
DAYS 6-7 — META + PINTEREST + GOOGLE + ATTRIBUTION CHECK
| # | Action | Actor | Blocks | Blocked-by | Hours | Risk if missed |
|---|---|---|---|---|---|---|
| 6.1 | Meta Business Manager access: TAPT added as agency-level partner; ad-account + pixel access granted | RYAN + FAB |
Day-15+ paid social | 3.1 | 1.0 | No paid Meta ability |
| 6.2 | Meta pixel installed/verified on EF Shopify; conversion events firing | FAB + AUTO |
Attribution + audiences | 6.1, 5.1 | 1.0 | Paid spend goes blind |
| 6.3 | Meta CAPI (server-side) configured for resilience to client-side tracking loss | FAB |
iOS attribution quality | 6.2 | 1.0 | Underreporting of paid lift |
| 6.4 | Pinterest Business: TAPT added as partner; tag installed; conversion events configured | RYAN + FAB |
Pinterest paid (Media Plan 40% allocation) | 3.1 | 1.0 | Largest paid channel goes blind |
| 6.5 | Pinterest catalog ingested + product groups created per Media Plan v0.1 priorities (cashmere, India hand-block prints, signature pieces) | FAB + MYC (curates groups) |
Pinterest shopping campaigns | 6.4, 5.2 | 1.5 | Shopping ads can't target catalog |
| 7.1 | Google Ads + Search Console + GA4: TAPT granted access; conversion imports configured | RYAN + FAB |
Google paid + organic-search insight | 3.1 | 1.0 | No view into Google channel |
| 7.2 | Google Merchant Center: feed verified, account approved, shopping-ad-eligible | RYAN + FAB |
Google shopping campaigns | 5.4, 7.1 | 1.0 | No shopping ad capability |
| 7.3 | UTM convention locked + documented; all upcoming campaigns tag uniformly | MYC + MER |
Clean attribution | 6.2, 6.4, 7.1 | 0.5 | Attribution = mush |
| 7.4 | Attribution test transactions run: $1 test purchase via Meta-tagged link, Pinterest-tagged link, Google-tagged link, email-tagged link, organic; all 5 should appear correctly in platform attribution view + Klaviyo/Shopify | FAB + MER |
Confidence in attribution stack | 4.3, 5.3, 6.2, 6.4, 7.1, 7.3 | 1.5 | Discover attribution bugs mid-campaign when stakes are high |
| 7.5 | End-of-Week-1 check-in call w/ RYAN (~45min): confirm everything working; surface access gaps | MYC + MER + Billy + RYAN |
Trust + Week-2 readiness | 7.4 | 0.75 | Issues compound silently into Week 2 |
Days 6-7 exit criteria: Meta + Pinterest + Google all wired. Attribution test passes. Week-1 call done. ~10hr Tapt-side. RYAN ~2hr + 45min call.
Risk threshold: If attribution test (7.4) fails on any channel, do NOT proceed to Week 2 active curation; fix attribution first. Failed attribution silently corrupts every downstream metric.
DAYS 8-10 — ONBOARDING SESSION + EMR/TEAM TRAINING
| # | Action | Actor | Blocks | Blocked-by | Hours | Risk if missed |
|---|---|---|---|---|---|---|
| 8.1 | Onboarding session #1 w/ RYAN (~90 min, recorded): platform tour + curation interface + approval flow + voice-flag mechanism + per-channel draft→approve→ship pattern | MYC + FAB (technical Qs) + RYAN |
Active curation Days 11+ | Week 1 complete | 1.5 | Curation can't start; RYAN confused at first content review |
| 8.2 | Recording of 8.1 saved to platform replay library + Slack-shared | FAB + AUTO |
EMR/team future ref | 8.1 | 0.25 | EMR can't catch up on her own time |
| 8.3 | Curation-pattern cheat-sheet 1-pager delivered to RYAN (PDF: "5 buttons + 3 keyboard shortcuts you'll use 80% of the time") | MER |
Day-11 active curation usability | 8.1 | 1.0 | Curation friction → RYAN frustration |
| 9.1 | Onboarding session #2 w/ EMR (~60 min if she joins; can be solo-recording-watch + 30min Q&A if she prefers): voice authority + when to flag + when to defer to RYAN | MYC + EMR (or RYAN proxy) |
EMR engagement in voice approvals | 8.2 | 1.0 | EMR voice authority isn't activated; brand-voice drift |
| 9.2 | If EMR not on session: structured async voice-flag interface walkthrough video (3 min) sent to her w/ how-to-use guide | MYC |
EMR async engagement | 9.1 (if didn't happen live) | 0.5 | EMR uninvolved in voice judgments |
| 10.1 | Onboarding session #3 (optional): any other EF team member RYAN wants in the loop (other marketing person, ops lead, etc.) | MYC + RYAN's designee |
Multi-actor curation if scope demands | 8.1 | 0.5-1.0 | Team-side coverage gap if RYAN out |
| 10.2 | First feedback-collection: RYAN + EMR async survey "what's confusing? what feels wrong? what's missing?" | MER (drafts survey) |
Cheat-sheet v0.2 + Day-14 curation tune | 8.1, 9.1 | 0.5 | Friction goes unsurfaced |
Days 8-10 exit criteria: RYAN + EMR (or proxy) trained; cheat-sheet shipped; feedback loop open. ~5hr Tapt-side. RYAN ~1.5hr. EMR ~1hr.
Risk threshold: If EMR refuses or can't engage on voice authority (9.1/9.2), surface to RYAN immediately: do we proceed with EMR as named-only authority + RYAN as effective voice approver, or pause until EMR can engage? Affects Day 19+ Model Profile likeness flow.
DAYS 11-14 — ACTIVE CURATION + FIRST CREATIVE REVIEW
| # | Action | Actor | Blocks | Blocked-by | Hours | Risk if missed |
|---|---|---|---|---|---|---|
| 11.1 | First wave of campaign creative generated: 3 emails + 4 paid social variants (Meta + Pinterest split) + 3 organic posts; ALL stay in draft until RYAN approves | MYC + AUTO (generation) + MER (QA pass) |
Day-15 first campaign send | Days 8-10 complete | 4.0 | Day 15 launches with stale/generic content |
| 11.2 | Draft creative pushed to RYAN's curation queue; Slack notification fires; RYAN sees 10 items to review | AUTO + FAB |
RYAN approval cycle | 11.1 | 0.1 | RYAN unaware of queue |
| 11.3 | RYAN approval cycle session 1 (~30-45 min self-paced): voice-flag, approve, request-revisions on each | RYAN | Days 11-13 iteration loop | 11.2 | 0.75 | Queue stalls |
| 11.4 | Voice-flag responses processed: system regenerates flagged items with RYAN's feedback as additional voice rules | AUTO + MYC (reviews regenerations) |
Iteration convergence | 11.3 | 1.0 | Same flags recur; RYAN frustration |
| 11.5 | EMR voice-check pass on email-from-EMR draft (if any): EMR approves or edits inline | EMR + MYC |
Founder-voice authenticity | 11.4 | 0.25 | Founder-voice content goes out without founder check |
| 12.1-13.5 | Iteration loop: 11.3 → 11.4 → 11.3' → 11.4' until creative converges (typically 2 cycles for a brand new to the pattern) | RYAN + MYC + AUTO |
Day-14 final approval | 11.2 | 2.0 | Doesn't converge by Day 14 → Day 15 launch slips |
| 14.1 | Curation-pattern check-in w/ RYAN (~30 min): does this feel sustainable at current volume? adjust cadence/volume? | MYC + Billy + RYAN |
Sustainable rhythm | 11-13 complete | 0.5 | RYAN burns out by Week 3; we miss the signal |
| 14.2 | Cheat-sheet v0.2 updated based on actual RYAN usage + Day-10 survey | MER |
Faster Day 15+ curation | 10.2, 11.3 | 1.0 | Curation friction persists |
| 14.3 | End-of-Week-2 check-in: Week 1 + 2 retrospective; flag any threshold-misses; reaffirm Day 15+ plan | MYC + Billy + RYAN |
Week 3 alignment | 14.1 | 0.5 | Issues compound into campaign launch |
Days 11-14 exit criteria: First wave approved; RYAN ran curation flow ≥2 times; EMR signed off on founder-voice content; cadence-sustainability discussed. ~9hr Tapt-side + ~1hr EMR + ~2hr RYAN.
Risk threshold: If iteration loop fails to converge in 3 cycles, escalate to MYC for direct content-overhaul session with RYAN (Sonnet→Opus pricing-style upgrade — this matters). Brand-voice betrayal in the first real campaign is the biggest single Day-1-30 risk.
DAYS 15-18 — FIRST REAL CAMPAIGN SHIPS
| # | Action | Actor | Blocks | Blocked-by | Hours | Risk if missed |
|---|---|---|---|---|---|---|
| 15.1 | Campaign moment finalized (season-appropriate per sign-date — fall return-to-wardrobe / Holiday preview / spring drop preview) | MYC + RYAN |
Campaign relevance | 14.3 | 0.5 | Campaign is calendrically off |
| 15.2 | Email send #1 (RYAN-approved): hand-off from draft to Klaviyo send queue; scheduled or sent live | MYC + RYAN approves send → AUTO |
First email-attributed revenue | 11.4, 14.1 | 0.25 | Day-30 deliverable summary misses "first campaign shipped" |
| 15.3 | Paid social campaign(s) live: Meta + Pinterest spend turned on per Media Plan v0.1 daily-budget allocations | MYC + FAB (technical) + RYAN approves spend |
First paid lift | 6.5, 7.4 | 1.0 | First-quarter ROAS data doesn't accumulate |
| 15.4 | Organic post(s) live across IG / Pinterest pin / Tumblr | MYC + AUTO |
Organic content cadence | 11.4 | 0.5 | Organic cadence resets clock |
| 16.1 | Day-after monitoring: email open + click rate, paid CTR + early CPM, Pinterest impressions, Shopify revenue attribution flowing | MER + MYC |
Strategic-review baseline | 15.2, 15.3 | 1.5 | Day-22 review has no data |
| 16.2 | Slack daily-pulse update in #ef-active: 1-paragraph "here's what we're seeing" w/ chart screenshot |
MER |
RYAN feels in-loop | 16.1 | 0.5 | RYAN goes silent; trust erodes silently |
| 17.1 | Mid-campaign adjustment if any: pause + reallocate budget OR shift creative based on 48-hr data | MYC + RYAN approves |
Real-time optimization | 16.1 | 1.0 | Suboptimal spend continues |
| 17.2 | First quarterly PR pitch draft prepared (gift-guide editors / sustainability press / founder-storytelling): per Media Plan v0.1 PR thesis | MYC + LUM (research-side: target list build) |
Day-22 PR pitch wave #1 send | none direct | 3.0 | PR cadence slips a quarter |
| 18.1 | Campaign mid-point retrospective w/ RYAN (~30 min): what worked, what didn't, what surprised | MYC + Billy + RYAN |
Week 4 strategic review prep | 16.1, 17.1 | 0.5 | Strategic review lacks RYAN perspective |
Days 15-18 exit criteria: First campaign shipped end-to-end across 3+ channels; attribution data flowing; daily pulse running. ~9hr Tapt-side. RYAN ~1.5hr.
Risk threshold: If attribution doesn't flow within 24hr of first paid spend, hard-stop new spend until attribution debugged. Spending blind is the failure mode that breaks the Y1 economics.
DAYS 19-21 — MODEL PROFILE SYSTEM SETUP
| # | Action | Actor | Blocks | Blocked-by | Hours | Risk if missed |
|---|---|---|---|---|---|---|
| 19.1 | Model Profile creation walkthrough w/ RYAN (~45 min): show M1 + M2 already-seeded in platform; explain reference vs Mode A vs Mode B | MYC + FAB + RYAN |
Confidence in EF-owned Model Profile system | none direct | 0.75 | RYAN doesn't understand what's being signed for |
| 19.2 | Likeness-use addendum signed by M1: 15-min call (PRA runs) → e-sign → countersigned by RYAN-as-EF + filed |
PRA + M1 + RYAN |
M1-based generated imagery for external surfaces | 19.1 + Pre-Day-0 likeness drafts | 0.5 | Any M1-based generated image going external = legal exposure |
| 19.3 | Likeness-use addendum signed by M2: same as 19.2 | PRA + M2 + RYAN |
M2-based generated imagery | 19.1 + Pre-Day-0 | 0.5 | Same as 19.2 |
| 19.4 | EMR self-signs the addendum (founder-as-model carveouts addressed) — if EMR wants a profile of herself | PRA + EMR + RYAN |
EMR-as-model profile | EMR's call | 0.25 | EMR profile can't be activated |
| 20.1 | Profile creation in EF-environment platform: M1 + M2 ref-imagery transferred from Tapt env → EF GCS bucket (per 2.5) | FAB |
EF-owned Model Profile data | 2.5, 19.2, 19.3 | 2.0 | Profiles live on Tapt infra (ownership confusion) |
| 20.2 | First test generation in EF environment using M1 profile: RYAN watches end-to-end | FAB + RYAN |
RYAN sign-off on production-use | 20.1 | 0.5 | RYAN doesn't trust the system |
| 20.3 | EMR profile (if 19.4 done): ref-imagery curated by EMR + RYAN; seeded; test generation | MYC + FAB + EMR + RYAN |
EMR-as-model option for campaign creative | 19.4, 20.1 | 1.5 | EMR-as-founder-content limited to existing photography |
| 21.1 | Production-use policy locked: "approved-for-external" gate stays = TRUE off by default; RYAN explicitly approves per-image before any external surface (paid social, email, organic) | PRA + FAB + RYAN |
Generated-imagery legal posture | 19.2-19.4, 20.1 | 0.5 | Auto-publish risk; legal exposure |
| 21.2 | First generated image used in a real campaign (if a Day-15-18 campaign asset can be replaced with a model-profile gen + RYAN approves) — proves the loop end-to-end | MYC + RYAN + AUTO |
Model Profile system validated | 21.1 | 0.75 | Model Profile system unused in M1; doesn't ship value |
Days 19-21 exit criteria: Likeness addendums signed by M1 + M2; profiles in EF env; production-use policy locked; at least 1 generated image used in real campaign. ~7hr Tapt-side. RYAN ~2hr. M1, M2, EMR ~30min each (signing).
Risk threshold: If addendums (19.2/19.3) can't be signed in this window, Model Profile system stays internal-only (no external generated imagery) until signed. This is a hard gate; do NOT bypass.
DAYS 22-26 — STRATEGIC REVIEW + PR + INFLUENCER
| # | Action | Actor | Blocks | Blocked-by | Hours | Risk if missed |
|---|---|---|---|---|---|---|
| 22.1 | Strategic-review prep doc compiled: Day-1-21 metrics summary + what surprised + what's underperforming + Month-2 hypothesis | MER (compiles) + MYC (interprets) + LUM (benchmark cross-ref) |
Strategic review call | 16.1, daily-pulse logs | 3.0 | Review is hand-wavy; RYAN can't decide |
| 22.2 | Mid-month strategic review call w/ RYAN (~60 min): walk through prep doc; agree Month-2 adjustments | MYC + Billy + RYAN |
Month-2 plan | 22.1 | 1.0 | Month 2 flies blind |
| 22.3 | PR pitch wave #1 personalized + ready: 8-12 targeted pitches per Day-17.2 prep | MYC + LUM (research) |
First PR placements | 17.2 | 3.0 | PR cadence slips |
| 23.1 | PR pitch wave #1 sent: from RYAN's email (or Billy's on RYAN's behalf if RYAN prefers) | RYAN sends OR Billy sends w/ RYAN approval | First-quarter PR placements | 22.3 | 0.5 | No placements; brand stays under-known per Lumen scan |
| 24.1 | Influencer prospect list draft: 30-50 candidates from Lumen's cohort research + adjacent (Christy Dawn / Mille / Apiece Apart audience overlap creators) | LUM + MER |
Month-2 influencer outreach | none direct (parallel) | 4.0 | Influencer outreach delayed a month |
| 24.2 | Influencer prospect list reviewed w/ RYAN + EMR: approve list, sequence priority, voice for outreach | MYC + RYAN + EMR |
Month-2 outreach launch | 24.1 | 1.0 | Outreach launches off-brand or to wrong creators |
| 25.1 | Month-2 adjusted plan documented: any channel reallocations, creative volume changes, frequency tweaks, new bets | MER + MYC |
Month-2 execution | 22.2 | 1.5 | Month 2 ambiguous; team executes inconsistently |
| 25.2 | Month-2 plan shared w/ RYAN in Slack #ef-active + 1-pager PDF for his reference |
MER |
RYAN alignment | 25.1 | 0.5 | RYAN unaware of plan shift |
| 26.1 | First press placement signal monitoring begins (set up Google Alerts on brand, manual check on each Day-23 pitch recipient's pub) | LUM + MER |
PR ROI tracking | 23.1 | 0.5 | Placements happen and we miss them |
Days 22-26 exit criteria: Strategic review done; Month-2 plan signed off by RYAN; PR pitch wave #1 sent; influencer list approved. ~15hr Tapt-side. RYAN ~3hr. EMR ~1hr.
Risk threshold: If RYAN doesn't approve Month-2 plan by Day 27, signal: pricing v0.8 declining-monthly drop from Month 2 fires regardless on the calendar; we don't get a make-good. Surface to Billy immediately.
DAYS 27-30 — HANDOFF + DAY-90 SCHEDULING
| # | Action | Actor | Blocks | Blocked-by | Hours | Risk if missed |
|---|---|---|---|---|---|---|
| 27.1 | Full documentation handoff package compiled: every credential rotated to EF-only ownership (TAPT roles drop to read-only or removed where appropriate), every integration documented, every brand-DNA refinement saved, every voice-rule captured in platform memory | FAB + PRA + MER + RYAN audits |
Sustainable steady-state | All Day 1-26 integrations | 4.0 | EF inherits a system they can't independently operate |
| 27.2 | Documentation packet PDF + interactive doc-shelf delivered to RYAN | MER |
RYAN onboards future hires | 27.1 | 1.0 | Knowledge stays locked in TAPT-side |
| 28.1 | TAPT-side cadence shift: daily-pulse drops to twice-weekly; ad-hoc on-demand for substantive issues; Slack #ef-active stays open |
MYC + MER |
Steady-state ops | Month 2 begins | 0.25 | Cadence-shift surprises RYAN; he expects daily |
| 28.2 | Month-2 fee confirmation: Tapt billing system invoices $3,000 (per v0.8) automatically per the agreed schedule; RYAN sees it lands as expected | PRA (sets up auto-invoice) + RYAN confirms received |
Cash-flow + trust on pricing | 0.4 internal sync | 0.25 | Surprise invoicing damages trust |
| 29.1 | Day-90 strategic review scheduled (3 months out — locked on calendar) | MYC + RYAN |
Continuity | 22.2 | 0.1 | Review slips; quarterly cadence breaks |
| 29.2 | Day-90 prep checklist: what data will we have? what decisions will be on the table? Send to RYAN now so he can plan his thinking | MER |
Quality of Day-90 review | 29.1 | 0.5 | Day-90 is reactive vs proactive |
| 30.1 | Day-30 sign-off: Mycelia + Billy + RYAN call (~45 min): celebrate, retrospective Days 1-30, confirm Month-2+ rhythm, surface anything unresolved | MYC + Billy + RYAN |
Engagement health | All previous | 0.75 | Engagement enters Month 2 without explicit alignment |
| 30.2 | Day-30 deliverable summary published: 1-page PDF + Slack post showing platform-running + integrations-live + Klaviyo-SMS-active + first-campaign-shipped + attribution-flowing + Model-Profiles-created + PR-wave-sent + influencer-list-ready + team-trained | MER + MYC |
RYAN's confidence + EMR's confidence | 30.1 | 0.5 | First-30-days achievement lost; doesn't compound into renewal narrative |
| 30.3 | TAPT-side post-mortem (internal): Mycelia + Mercator + Faber + Praetor + Lumen + Billy retrospective — what worked in the kickoff, what to change for client #2, what to fold into TAPT_CLIENT_KICKOFF_RUNBOOK_TEMPLATE_v0.1.md |
TAPT all |
Template improvement | 30.1 | 1.5 | Template stays EF-specific; client #2 repeats avoidable mistakes |
Days 27-30 exit criteria: Handoff complete; documentation delivered; Day-90 scheduled; Day-30 deliverable summary shipped; post-mortem captured. ~10hr Tapt-side. RYAN ~1.5hr.
§Escalation Matrix
Trigger → Action → Decision-maker:
| Trigger | Action | Decision-maker |
|---|---|---|
| Risk threshold tripped (any day) | Flag in #ef-active w/ "RISK" tag within 1hr of detection |
MYC + Billy decide path |
| RYAN unresponsive >24hr | Slack DM → email → if still unresponsive, MYC pings Billy who calls direct | Billy |
| EMR voice-flag standoff (RYAN approved, EMR rejected, no resolution in 24hr) | Pause that asset, schedule 15-min EMR call, default to EMR's call as the founder authority | EMR (with RYAN consultation) |
| Day-by-day timeline slip >2 days | MYC convenes internal sync; surface to RYAN with adjusted plan + cost implications | MYC + RYAN |
| Attribution gap detected mid-campaign | Hard-stop paid spend on affected channel; FAB debugs; resume when verified | FAB + MYC |
| Cost overrun on 3rd-party APIs (>20% projected) | Surface to RYAN immediately; per pricing v0.8, RYAN pays direct → he sees it, but flag the surprise | MYC + RYAN |
| Likeness-addendum signing blocked | Pause Model Profile production-use; engagement continues on existing photography only | PRA + RYAN |
| Brand-voice betrayal incident (asset shipped that EMR/RYAN considers off-brand) | Pull asset within 1hr; root-cause within 24hr; corrective action shared in #ef-active |
MYC owns RCA + comms |
§Per-actor SOP summaries (one paragraph each)
MYC (Mycelia) — Architect + content lead:
Owns content strategy + voice synthesis + cross-agent coordination + RYAN/EMR relationship continuity. Per-day expected presence: M1 active daily 1-3hr; M2+ drops to 30-60min daily + on-demand. Hands off voice-rules + brand-DNA refinements to MER for documentation. Decision authority on creative pivots within engagement scope.
FAB (Faber) — Build + infrastructure:
Owns platform integration + APIs + technical onboarding + Model Profile system + attribution stack. Active days 2-7 + 19-21 heavily; available on-demand thereafter. Decision authority on technical architecture. Escalates to MYC if blocked by RYAN-side access provisioning.
PRA (Praetor) — Contracts + compliance:
Owns contract execution + likeness addendums + DPA + ongoing compliance reviews. Active days 0, 19-21 + on-demand. Decision authority on contract/legal scope. Escalates to Billy if attorney engagement decisions needed.
MER (Mercator) — Revenue ops + documentation + curation support:
Owns this runbook + per-day-pulse Slack updates + survey/feedback compilation + cheat-sheets + Month-2-plan documentation + post-mortem capture for template iteration. Active daily 1-2hr Days 1-30. Decision authority on documentation format + cadence; defers to MYC on content + RYAN on tactical priorities.
LUM (Lumen) — Research + critical reading:
Owns Klaviyo audit interpretation + competitive-context calibration + PR target-list research + influencer prospect research + benchmark cross-references during strategic reviews. Active days 4-5 (audit interp) + 17-18 (PR target list) + 22 (strategic review) + 24 (influencer list). Otherwise on-demand for research questions.
Billy (Primus) — Real-person presence: Sends emails from real account when required; appears on Days 1, 7, 14, 22, 30 check-in calls; signs off on critical escalations; owns Tapt-side commercial decisions. Aim to keep Billy time ≤4hr/week during kickoff.
RYAN — EF lead contact: Reviews + approves daily curation queue (~30min/day Week 1-2; drops to 2-3hr/wk by Week 3+); attends 6 scheduled calls (Days 1, 7, 14, 18, 22, 30) at 45-60 min each; gives final sign-off on all external-facing content + spend decisions. Total ~5hr/wk in Weeks 1-2, ~3hr/wk in Weeks 3-4.
EMR — Founder + brand voice authority: Voice-approves founder-attributed content + EMR-as-model imagery; ~2hr/wk; attends Day 9 onboarding session (or async-watches); flags any brand-voice drift she sees. Authority on voice escalations.
M1 + M2 (Models): ~30 min each in Days 19-21: addendum signing call + signature. No further commitment unless specific generation-approval surfaces in future.
§Hours summary (Tapt + EF)
Tapt-side total: ~85-100 hours across Days 0-30 (consistent w/ Mycelia's narrative: 60-80h MYC + 40-60h FAB + 5-10h PRA = 105-150h capacity; runbook tracks 85-100h actual planned + leaves headroom for iteration loops + unexpected issues).
EF-side total: ~15-20 hours for RYAN; ~5-8 hours for EMR; ~30 min each for M1, M2.
Per-week Tapt-side rough split:
| Week | MYC | FAB | PRA | MER | LUM | Billy |
|---|---|---|---|---|---|---|
| 1 | 10-12 | 12-15 | 1-2 | 5-7 | 2-3 | 2-3 |
| 2 | 10-12 | 5-7 | 0-1 | 4-6 | 0-1 | 1-2 |
| 3 | 8-10 | 5-7 | 1-2 | 3-5 | 2-3 | 0-1 |
| 4 | 6-8 | 2-3 | 0-1 | 4-6 | 3-5 | 1-2 |
These align with Tapt's pricing v0.8 setup-fee ($10K includes M1) and declining monthly cost starting M2.
§Day-30 sign-off checklist
The runbook is done when ALL of these are true. If any are not, EITHER fix before declaring Day 30 OR formally accept the gap in the Day-30 sign-off call w/ RYAN.
- Platform running on EF's GCP infrastructure
- Klaviyo + Shopify + Meta + Pinterest + GA4 + Google Ads + Google Merchant all wired + attribution-tested
- Klaviyo SMS opt-in surface live + first SMS welcome shipped
- First real campaign shipped end-to-end (email + paid + organic + Pinterest)
- Attribution data flowing into platform memory layer
- Model Profiles M1 + M2 created in EF environment; likeness addendums signed
- EMR-as-model profile created (if EMR opted in)
- Production-use approval policy locked + functioning
- First PR pitch wave sent
- Influencer prospect list approved
- RYAN + EMR + team trained on curation pattern + sustainable cadence established
- Documentation handoff package delivered
- Month-2+ cadence agreed + scheduled
- Day-90 strategic review scheduled
- TAPT-side post-mortem captured for template iteration
14/14 = green → engagement enters steady-state Month 2.
§Carry-overs to TAPT_CLIENT_KICKOFF_RUNBOOK_TEMPLATE_v0.1.md
When ready to parameterize for client #2-#N, generalize:
- Replace EF-specific channels (Klaviyo / Shopify / Meta / Pinterest / Google) with
{client.email_platform} / {client.commerce_platform} / {client.paid_channels[]}parameters - Pricing-v0.8 reference becomes
{client.pricing_version}with declining-monthly logic abstracted - Model Profile section conditional on
{client.uses_model_profiles}(some clients won't) - Wholesale-partner layer conditional on
{client.is_wholesale_heavy}(introduces Days 23-30 wholesale-asset-packaging actions per futureTAPT_WHOLESALE_LAYER_SERVICE_v0.1.md) - PR + influencer scope conditional on
{client.tier}(smaller engagements may defer PR to Month 2) - Hours estimates parameterized by
{client.complexity}× baseline EF distribution
— Mercator, 2026-05-25