ARC-OPS-006: ARC Launch Checklist (Concept → Beta)

Move ARC from concept to a live beta cohort with paying members, operating rhythm, and measurable performance.

• Never place API keys, webhook secrets, or tokens inside SOP pages.
• Store secrets only in approved environment variable stores (.env.personal / Vercel env / platform secret manager).
• If a key is ever exposed in chat/docs, rotate it immediately.

• Minimum beta members: 10
• Weekly attendance target: 70%+
• Weekly action completion target: 60%+
• Time to onboard new paid member: <24 hours

1. [ ] Lock offer + trial messaging: 2-week trial, no money collected up front, and fit-first screening.
2. [ ] Lock public pricing language: "Memberships start as low as $100/month".
3. [ ] Lock post-trial paid plans for accepted members ($125 / $333 / $1200).
4. [ ] Lock applicant policy: not every applicant is accepted; fit and culture alignment are required.
5. [ ] Lock affiliate + facilitator commission policies.
6. [ ] Finalize legal pages (terms, refund, affiliate terms, trial terms).
7. [ ] Confirm ARC SOP hub is live and private.

1. [ ] Mintbird products + checkout flows live and tested.
2. [ ] Stripe connected and payment events verified.
3. [ ] Global Control tags + onboarding automations live.
4. [ ] CourseSprout Start Here module live.
5. [ ] Telegram group rules/pinned onboarding message live.
6. [ ] Cal.com onboarding/help link ready.
7. [ ] Jitsi room + recurring schedule ready.

1. [ ] Build Beta Invite list (warm contacts first).
2. [ ] Publish invite content + DM outreach plan.
3. [ ] Set first 4 weekly call dates/times.
4. [ ] Preload week-1 member check-in prompts.
5. [ ] Confirm KPI tracker is ready (attendance, completion, invites, joins).

1. [ ] Accept first beta members via checkout.
2. [ ] Run onboarding workflow end-to-end.
3. [ ] Hold first weekly live call.
4. [ ] Log commitments and run weekly follow-up loop.
5. [ ] Collect member feedback and issues list.

1. [ ] Resolve onboarding friction points.
2. [ ] Tighten call agenda based on attendance/completion data.
3. [ ] Tune invite messaging from conversion feedback.
4. [ ] Document facilitator training requirements from real operations.
5. [ ] Prepare to onboard first non-Ryan facilitator.

• New members joined
• Call attendance %
• Action completion %
• DM conversations started
• Invites sent
• Churn/cancellations

• 4 consecutive weeks of consistent call cadence
• 70%+ attendance sustained
• 60%+ action completion sustained
• Onboarding + moderation SOPs stable with low manual firefighting

If beta stalls (low joins, low attendance, low completion) for 2 straight weeks, pause expansion and run a focused fix sprint before inviting more members.