Home / Ops / More in this area
The Founding Constellation - Post-Commit Experience + Weekend Process (v1)
Updated Jul 10, 2026 · Affirmology_PostCommit_Strategy_v1.md
Summary. Frame: the botched first form cost us trust. We win it back with CLARITY and momentum. Principle: NO DEAD AIR. The moment someone says yes, they immediately (1) unlock something real, (2) see exactly what happens next, and (3) start a value drip that carries t
The Founding Constellation - Post-Commit Experience + Weekend Process (v1)
Frame: the botched first form cost us trust. We win it back with CLARITY and momentum.
Principle: NO DEAD AIR. The moment someone says yes, they immediately (1) unlock something real,
(2) see exactly what happens next, and (3) start a value drip that carries them to launch.
Nobody ever wonders "did that work? what now?"
Timeline shift (confirmed): texts go Friday 7/10, but the APP launch is Sun 7/13 (soft) → Mon
7/14 (wide). Friday's job is to lock the commitment and make it feel alive, NOT to launch.
1. THE INSTANT UNLOCK (fires the second they commit, automated)
Three things happen at once when they sign the four boxes:
A) ON-PAGE: the acceptance card becomes a "You're in the Founding Constellation" welcome hub:
- A short welcome-in note + the Jeff & Sol video.
- Their weekend roadmap (below), so the wait is a plan, not silence.
- A gold button: "Open your Founding page" -> their results page (their permanent hub).
B) CONFIRMATION EMAIL (already built, timing updated below): same message + the roadmap + the
link to their page.
C) THEIR RESULTS PAGE BECOMES THEIR FOUNDING HUB. This is the "unlock somewhere." The first gift
waits there: their MIRROR reading (the deeper spoken chart reading). If a person's Mirror is
rendered, it shows immediately; if not, the page says "your Mirror unlocks within 24 hours."
Every new gift this weekend appears on this same page, so they keep coming back.
Net effect: yes -> welcome -> a real gift on their page -> a clear plan. That is the clarity.
2. THE WEEKEND DRIP (suspense + customer service, carries them to launch)
- FRI 7/10 (on commit): welcome hub + Mirror reading on their page + the roadmap. A warm personal
reply from Jeff to their text.
- SAT 7/11: one more gift audio drops to their page + a short "we're getting your app ready for you"
note (text or email). Keeps them warm, proves we deliver, builds anticipation.
- SUN 7/13 (SOFT LAUNCH): the TestFlight invite goes out (sequence below) + the WhatsApp circle
opens + the wiki + a 2-minute walkthrough video. App in hand.
- MON 7/14 (WIDE): full launch, first structured feedback ask, keep everyone flowing through
their /r/
links so we stay connected.
3. THE TESTFLIGHT GATE (Sunday) - the piece that was undefined
- TRIGGER: Sunday morning, sent to everyone with status = committed.
- WHO SENDS: an automated branded email from our system (so nobody is missed) PLUS a personal text
from Jeff to each (the human touch that has been working).
- EXACT INSTALL MESSAGE (draft):
"Your Affirmology beta is ready. On your iPhone:
1. Tap this link: [TestFlight link]
2. If prompted, install the free TestFlight app, then tap the link again.
3. Open Affirmology and sign in with THIS email.
4. Your first audios are waiting. Play one, then tell us how it landed.
Join the founding circle on WhatsApp: [link]. A 2-min walkthrough: [video]."
- FALLBACK: if the app slips, Sunday still delivers a gift + "app invite lands Monday," so the
soft-launch promise is never broken empty.
4. CONFIRMATION EMAIL - timing fix (do before any send)
Current copy promises "beta app Friday instructions" and "WhatsApp later this week." Update to the
weekend truth:
- "This weekend: Saturday, one more audio gift. Sunday, your app invite arrives and our WhatsApp
circle opens. From there we build it together."
Keep everything else (photo, warmth).
5. WHO BUILDS WHAT
- COWORK (me): the on-page welcome-hub copy + the roadmap block; the confirmation-email timing fix;
the Saturday gift note; the TestFlight email + text copy; the wiki page content; the walkthrough
video script.
- CODE: render each committer's Mirror + the Saturday gift audio and expose them on the results
page; the TestFlight build + the automated Sunday invite send; keep /api/admin/beta-submissions
as the source of truth for who has committed.
- JEFF + SOL: record the short walkthrough video; open the WhatsApp circle Sunday; send the personal
texts (Friday commit link, Sunday app invite); pick the Saturday gift.
6. OPEN DECISIONS (need your call to lock this)
- The Friday instant gift: is it their MIRROR reading (deeper, personalized, strongest) or a
simpler shared "welcome to the Constellation" audio (faster, everyone gets the same)? Mirror is
more powerful but needs each one rendered; the shared one is instant and safe.
- The Saturday gift: what is it (another reading? a morning/sleep audio? a founding blessing)?
- TestFlight Sunday: automated email + your personal text, or personal text only?
- Do we hold the whole thing until every committer's Mirror is rendered, or send on commit and let
Mirrors fill in within 24h?
Headcount (from the CRM + Code's submission log, 2026-07-10)
- Committed (signed the agreement): 3 real so far (Norm Adams, Iman Huschmand, Elmira Shahzeidi),
plus Jeff. (Code's admin log confirms 3 committed + 2 unresolved test submissions.)
- Beta invited (tracked link created, not yet committed): ~20.
- Took demo / have a Soul Song page: strong majority now have result pages (the earlier failed
renders for Taylor, Alex de Carvalho, and Leandro have all been RE-RENDERED and now have pages).
- Never finished the form / no page yet: a handful (Valeria, Gloria Ruiz, Ulyanna, Drtanya, etc.).
- Per-person tracked commit links (/r/
?to=commit) live in Code's system; pulling the full
name -> link mapping from Code so you can text each person their own.