Mycelia Present · rendered 2026-05-24T22:39:47.204Z · source: ../convivium/clients/emerson_fry/EF_REVEAL_DAY_PLAYBOOK_v0.1.md

EF Reveal Day Playbook — Friday 2026-05-29

Filed: 2026-05-24 by Mycelia For: Billy · the reveal-day operational guide Target reveal date: Friday 2026-05-29 Format: Live call w/ Ryan + Billy in support + Remy drives the platform tour

§1 — Pre-reveal (Thu 5/28 EOD)

Final dry-run checklist

Email to Ryan (24-48 hours pre-reveal)

Draft for Billy to customize:

Subject: Looking forward to Friday — quick details before our call

Hi Ryan,

Excited for our walkthrough Friday at [TIME]. A quick heads-up on what to expect:

What we built for Emerson Fry is a logged-in platform — you'll experience it directly rather than sitting through a deck. I'll be on the call with you, but you'll actually be using the tool while we talk.

Login: [URL] · Email: [his email] · Password: [his password]

The platform's agent (her name is Remy) will guide you through the experience — what we understand about your brand, the full marketing plan we've built across every channel, the first-round creative we've already produced, a live demonstration of the system making and shipping a piece of work, and how the investment + engagement works going forward.

Plan on about 45-60 minutes. No prep needed on your end — just show up + click around. I'm on the call as support; the platform does most of the work.

Looking forward to it.

— Billy

§2 — Reveal-day timing (target 45-60 min)

Time Phase What happens
0:00-2:00 Greeting + setup Billy + Ryan exchange hellos. Billy: "let me hand it off to the platform — open the link i sent." Ryan logs in.
2:00-4:00 Welcome station Remy greets Ryan, sets the frame. Billy mostly listens; can add color if Ryan asks.
4:00-12:00 Brand station (Series A, 8 panels) Ryan paces through the panels. Remy contextualizes. Billy: stay quiet unless Ryan asks. ~1 min per panel average.
12:00-24:00 Plan station (Series B, 12 panels) Same pattern. ~1 min per panel. Billy can interject if a specific channel is something he wants to expand on.
24:00-30:00 Gallery station Ryan browses creative. Billy: "click into any of those that catch your eye." Remy contextualizes per asset.
30:00-34:00 Make station (live demo) Remy generates a new email in front of Ryan. ~2-3 min of generation; ~1 min of Ryan reviewing.
34:00-37:00 Deploy station (staged or real) Ryan ships the email into Klaviyo. Sees it land in his dashboard.
37:00-42:00 System station Remy explains how it works. Billy: can elaborate on the memory architecture if asked.
42:00-50:00 Investment station Remy walks the pricing structure. Billy: ready to answer questions about commitment, terms, attorney process.
50:00-55:00 Decide station Ryan picks a path (sign / discuss / explore / send details).
55:00-60:00 Wrap + next steps Billy: clear next-step depending on Ryan's decision. Set a follow-up. End call warmly.

§3 — Billy's role during the call

Default disposition: SUPPORT, not LEAD

The platform is the experience. Remy is the host. You're there to:

What to NOT do

Phrases to have ready

§4 — Likely Ryan questions + Billy's responses

About the system / how it works

Q: "Wait, the agent is actually generating this in real time?" A: "Yes — that's what you're seeing. Remy is producing emails, social content, ad creative based on your brand DNA we loaded. Every output goes through your approval before it goes anywhere customer-facing."

Q: "Does this replace my marketing team?" A: "No — it makes a marketing team possible. You + Emerson don't have a marketing function today. The platform IS that function. You stay in approval + curation; the system handles production. If you ever want to hire someone, they'd curate on top of this rather than start from scratch."

Q: "What about the photo shoots?" A: "The platform extends what your photographer has already shot — variants, social cuts, email crops. The studio shoots are still the source. For new identity work (a new model in your roster) we'd train a per-model image module once you confirm the model has consented. That's a post-sign add-on, not part of the launch."

Q: "How does the AI not screw up my voice?" A: "Remy is trained on your brand DNA — voice rules, banned words, the lowercase + 'honor' + '+' patterns, the founder voice register, the scarcity-respect. Voice consistency is the discipline most marketing fails. With this system it's the substrate, not a check at the end."

Q: "What about my customer data?" A: "Your data stays yours. The deployed platform runs on your Google Cloud account. The customer data flows through your existing tools (Klaviyo, Shopify). We have a Data Processing Addendum that's part of the contract — that's all standard. You can read the full IP architecture if helpful."

About pricing + commitment

Q: "$10K is a lot for setup." A: "I hear that. The $10K covers the system you just walked through — software install, stack integration, brand DNA load, the first-round creative suite already produced, the analytics feedback loop, onboarding, and the first 12 months of autonomous operation management. Everything's already built; the $10K activates it for you."

Q: "What if I want to start smaller?" A: "Foundation tier at $5K/mo is the step-down. Two channels, monthly cadence, brand voice live, seasonal Holiday campaign. Lighter scope but full system access. We could start there + scale up at the 90-day mark if it's working."

Q: "What if it doesn't work?" A: "The success fee component is contingent on revenue lift — you pay nothing on that piece if there's no lift. And the contract has a 30-day cancellation after the 90-day initial period. So your downside is bounded — worst case, you've paid $10K + 90 days of monthly + walked away with the platform we built + the creative we delivered. Best case, you have a marketing function that's compounding."

Q: "How long is the contract?" A: "90-day initial commitment + 30-day cancellation after that. Industry-standard."

Q: "What about the success fee percentage?" A: "Tiered marginal rate — you pay more on the first dollars of lift, progressively less as it scales. Capped at $15K/quarter year one. Designed so we're aligned with you on early proof + you're protected on bigger growth. Full math on the platform you can review."

Q: "Can I see the contract?" A: "Yes. Our attorney has drafted the full package — MSA + License + DPA + SOW + SLA. I can send the full set over after our call. The whole structure is designed to be founder-friendly — you own your deployed copy of the code, perpetual license, your data stays yours."

About timing + next steps

Q: "When could this start?" A: "If you sign in the next two weeks, we'd have you live + integrated by the end of June. Holiday creative is ready to ship by November — we'd have a full 4+ months of runway."

Q: "Who's on your team?" A: "I run it. We have the platform development team, the agent system, the brand-research process you experienced. Lean by design. For your account specifically, I'm your direct point of contact + Mycelia handles strategy + Remy is your day-to-day system."

Q: "What other brands do you work with?" A: "Emerson Fry is our first client at this exact engagement shape. We've been building toward this for [X months]. The system + the methodology are ready; you'd be the prototype client. That's also why the pricing is favorable — you're shaping how this works going forward + we want a great reference."

Hard / awkward questions

Q: "I want to think about it / not ready to decide today." A: "Totally understand. The platform stays accessible for you — you can come back + explore. No pressure. What would be most helpful — a follow-up call next week, more written detail to read, anything specific?"

Q: "I want to negotiate the pricing." A: "Let's talk specifics. What feels off? I have some flexibility on the structure (which tier, success fee mechanics) and less flexibility on the $10K (that covers our actual cost). I'd rather find a structure that works for you than try to convince you of one that doesn't."

Q: "What if you go out of business?" A: "Fair question. The platform you have is yours — the code, the deployment, the brand DNA loaded into it. If anything happened to us, you'd still have a working system. The license is perpetual + survives termination. The IP architecture was specifically designed for this kind of resilience."

Q: "Why should I trust AI to handle my brand?" A: "You shouldn't trust AI to do that. You should trust the system + the people behind it. Every output goes through your approval. The system produces; you decide. That's the whole architecture. If you don't want something to go out, it doesn't go out. If you want to change the voice on something, the system regenerates."

§5 — Technical contingency (if things go wrong)

If platform won't load / hard down

Mycelia notified immediately via Slack DM — Faber + Mycelia on standby to fix. Billy: "let me check what's going on — give me one second" → switch to your laptop browser if it's a phone issue, or escalate via Slack. Worst case: reschedule. Don't try to walk Ryan through verbally — the experience is the platform.

If make-demo fails (live generation stalls)

Pre-generated backup variant is queued. Billy: "let me have Remy fall back to a saved version — same idea." Display the backup. Move on. Don't reveal the fallback was a backup unless Ryan asks.

If Klaviyo deploy fails

If real-send wasn't going to work, staged was the default — should already be the path. If staged also fails: "looks like the Klaviyo integration is being slow — i'll have Mycelia follow up with the demo asynchronously. Let's move to the next station." Move on; don't dwell.

If Remy says something off-voice or wrong

Billy: "let me jump in here — actually that's [correct version]. Remy is getting better at this stuff every week; that's part of the system learning." Smooth + correct + move on. No defensiveness.

If Ryan asks something none of us anticipated

Billy: "great question — let me make sure i give you the right answer. i'll follow up with the specifics tomorrow." Note in your phone or a piece of paper. Don't make it up.

If Ryan tries to negotiate aggressively

Billy: "I hear you. Let's talk specifics offline — I want to make sure I give you a thoughtful response, not an off-the-cuff one. Can we set up a follow-up call this week?" Don't negotiate live; create space.

§6 — Post-reveal flow (what happens after Ryan's decision)

If Ryan signs ("I'm in")

Within 24 hours:

Within 72 hours:

If Ryan wants to discuss ("let's talk more")

Within 24 hours:

If Ryan wants to explore ("I need more time")

Within 24 hours:

Within 1 week:

If Ryan declines ("not the right fit / not now")

Within 24 hours:

Within 1 week:

§7 — Mycelia + Faber in-call protocol

Mycelia

Faber

Comms during the call

§8 — Post-reveal debrief (Friday EOD / Saturday)

Quick async debrief w/ Billy

Internal documentation

Iteration trigger

§9 — Emotional discipline for Billy

This call matters. It's the first time a Tapt client is going to see what we've built. But — the disposition that wins is calm + warm + steady. Not anxious-excited.

Reminders:

If something feels off mid-call, take a breath. Mycelia is in your ear via Slack. You're not alone in there.

— Mycelia, 2026-05-24