Home / Strategy / Launch and Go-To-Market

Affirmology 12-Day Launch Runway (to Monday 6/22 invite, then autopilot for the road trip)

Updated Jun 18, 2026 · Affirmology_LaunchRunway_12Day_v1.md

Affirmology 12-Day Launch Runway (to Monday 6/22 invite, then autopilot for the road trip)

Today: Thu 6/18. ~12 full lab days, then laptop-only/sporadic on the road (~late June → back mid-July). Milestone: Mon 6/22 - mass-send a segmented invitation to direct allies, routing them into beta tracks + investor conversations. Reframe that de-risks Monday: Monday = invite + capture, not full delivery. Compelling invite + clean routing + a solid demo. Personalized tester audios and deep onboarding roll out across the following days as people opt in (which also lets the corpus sprint land first).

Phase 1 - to Monday 6/22 (next 5 days): get launch-ready

Critical path, roughly in order: 1. Corpus pain-point sprint (in progress) so tester audios are strong. Numerology → Western → Vedic → Gene Keys structured this weekend. This gates audio QUALITY, not the Monday send, so it has the weekend. 2. The segmented invitation copy (Claude can draft): three versions, one voice, different doors: - Allies → Inner Orbit testers (experience + shape the app). - Astrology-fluent allies (Lauren, Monika, etc.) → Founding Constellation Lab / Affirmologist co-creators. - Investors → a conversation (demo + the master doc, not a hard pitch). Note: some Orbit testers can later upgrade; the invite plants that. 3. Beta program one-pager (Claude can draft, from the gamified-deal we logged): what a founding tester gets (founding status, free year → lifetime for depth, custom-audio rights for community holders) and the light ask (complete the journey, feedback per audio, try level-2 audios). 4. Signup + routing mechanism (lightweight, must work Monday): a simple form/landing that segments respondents into tracks AND captures birth data (date/time/place) for audio generation. Airtable form or MailerLite form → Airtable CRM. No heavy build. 5. Segment the people list in Airtable: allies/testers, lab candidates, investors, share-with. Ready to send. 6. Demo QA pass: confirm demo.affirmology.ai is flawless on desktop + mobile (it's the first impression).

Phase 2 - Monday 6/22: send

Mass-send the segmented invites → capture responses into the right tracks. Momentum day. Keep operational lift low: they experience the demo, they opt in, you capture them.

Phase 3 - remaining lab days (~6/23 - 6/30): onboard, generate, gather

• Generate testers' personalized audios via the cloud Studio as they opt in (corpus now stronger). This is where teams help.
• Collect feedback + testimonials fast: voice notes + per-audio ratings (the feedback mechanism from the Studio spec). Build superfans by making them feel founding.
• Investor conversations: demo + master doc; capture what resonates.
• Iterate content with the team based on real reactions.

Phase 4 - autopilot for the road trip (~2 weeks, laptop-only)

The point of everything built this week: the machine runs without your desk. - Cloud Studio serves 24/7 (done). - Nightly corpus crawler + listening engine run themselves (set the schedules before you leave). - A scheduled morning digest so you stay informed from a laptop (signups, feedback themes, "what the market wants," investor replies). - Async feedback + testimonial collection keeps flowing. - Light-touch: you respond to investors and key allies from the laptop; the team handles content/testimonials. - Prep the ads + marketing build to execute on your mid-July return (the growth-engine + funnel plans are the blueprint).

The one decision that shapes the build

How do testers get their own audio? Recommended for this window: a managed flow, they submit birth data on the signup form, you/Sol/team generate their Sacred Audio in the cloud Studio over the following days, and deliver the link. Self-serve generation can come later. This keeps Monday simple and quality controlled, and it's why Monday is capture-first.

Onboarding gate, NDA, and commitment (CATALOGED - decide later)

Delivery + commitment philosophy (open questions)

• Investor delivery format is undecided: one big investor video, vs. a video sent AFTER the demo experience, vs. an interactive page that walks them through a sequence of videos. Lean toward something interactive that also gauges engagement. To be designed.
• We are NOT dropping people into the app to do nothing. Entry is conditional on participation. We may lovingly bounce non-participants: "either participate now, or come join us when we're live." So onboarding must GAUGE interest + commitment, not just grant access.
• Implication: the gate should both protect IP (NDA) and filter for commitment (a small act of effort signals seriousness).

The NDA / gating problem (concrete, needs a real solution)

• Current state: the demo site has a weak checkbox. Not enough for letting real allies/investors see this at this stage.
• Bloom: pretty form, but too manual, hand-create a record per person, create a contract, push/email/link it. Does not scale.
• Need: a robust, SELF-SERVE process where an invitee views the full NDA, e-signs it (DocuSign/Adobe-style), and we automatically get a tracked record, with the demo gatekept until that record exists. Capture email to track.

Options to solve it (to evaluate when we choose)

1. Self-serve e-signature via reusable link (most formal): DocuSign PowerForms, Adobe Acrobat Sign web forms, or Dropbox Sign (cheaper, strong API). One link, the invitee fills + signs your NDA template themselves, the signed PDF is auto-stored, no manual record creation. A webhook pushes the signed record into Airtable. Kills the Bloom manual problem entirely.
2. Clickwrap NDA gate (lower friction, scales): a page that shows the full NDA, requires scroll + "I agree," and captures name/email/timestamp/IP as a logged, enforceable consent record (DocuSign Click, Ironclad Clickwrap, or a custom form). Best for volume; auto-records; lighter than a full signature.
3. Hybrid (likely best): clickwrap for the broad demo gate (fast, scalable, auto-tracked) + a full e-signed NDA (self-serve link) for the deeper tiers (Lab co-creators, investors who'll see more). Match formality to access level.
4. Gating wiring: a pre-demo signing page → on completion, redirect with a one-time token OR auto-add their email to Cloudflare Access → the demo opens only then. Signed record → Airtable via webhook (or Zapier/Make if no native hook). Zero manual steps per person.
5. Commitment filter on top: the same gate can ask 1 - 2 questions (why you're interested, will you complete the journey + give feedback) so we capture intent, not just a signature.

Recommendation direction (not final): a self-serve e-sign tool with reusable links + webhook→Airtable (Dropbox Sign or DocuSign PowerForms are the sweet spot), clickwrap level for most, full signature for inner tiers, gating the demo until the signed record lands. Have an attorney bless the NDA text and the clickwrap-vs-signature choice before it goes live.

What Claude can start now (just say go)

• Draft the three segmented invitations + the beta one-pager (today).
• Design the signup/routing form + the Airtable CRM segments.
• The pre-trip autopilot checklist (schedules, digest) when we get there.