Part 1. Questions to settle on the call
Decisions only you / the business can make.
Tiers, pricing & what each tier gets
- What are the membership tiers, and the price of each? (Mentored, a lower community tier, course-only?)
- For each tier: which tools are unlocked, which are locked or hidden, and what the limits are (how much Cofounder chat, which automations).
- Confirm the model: every paid tier gets Cofounder chat, and lower tiers see the locked tools as the reason to upgrade to Mentored — still right?
- Who counts as "community" vs "Mentored," and is it the same Studio with different access?
The course-only product
- Is there a course-only offer — your framework sold as just the course, with no Studio tools and no Cofounder?
- What's in it, and does the buyer get any Studio access (e.g. read-only lessons) or none?
- Price — and is it a funnel into the Studio, or a standalone product?
Commercial terms
- How does Ryan get paid — flat fee, per-member, revenue share, or build fee plus ongoing — and on what schedule?
- Who covers the running costs (AI usage + hosting) — passed through, or absorbed in the deal?
How a paying member gets into the Studio
- What's your checkout / payment system today?
- Should a new paying member get access automatically from your payment system, through their Circle membership, or be added manually at first?
- One login or two — do members sign in with their Circle account, or a separate Studio login?
The playbook & the unlock journey
- Is the current playbook the final, launch-ready version?
- Approve the "complete this lesson → unlock this tool" sequence (the pathway map).
- Hard gate or soft? Block a tool until the matching lesson is done, or just recommend the order?
- What counts as "completing" a lesson to unlock its tools — watching the video, or finishing the exercise / filling the playbook field?
- Should any tool unlock earlier as a taster to hook new members (e.g. the Compliment writer)?
Method sign-offs
- Approve the exact weekly check-in questions members must fill in (for the new weekly gate).
- Red vs Blue targets: give the minimum & stretch numbers per metric, or let the app simply compute "did you hit your weekly target."
- Provide the baseline call-audit material so we build the Sales Call Analyzer to your real scoring.
Chat & the AI surface
- Keep the in-Studio Cofounder chat, gate it by tier, or have members use their own Claude / ChatGPT for chat (with a light in-Studio helper)?
- Comfortable with your frameworks passing through ChatGPT for ChatGPT users? (Claude is the cleaner path.)
Build priority
- Of the planned tools, which 2–3 are must-haves to launch with first?
Part 2. What your team audits / verifies before go-live
Work on your side — not call questions.
Content & data
- Audit the full playbook for accuracy — it's the source of truth the whole Studio is built on.
- Make sure the playbook's example text is clearly separate from where members fill in their own answers, so we never import your examples as a member's.
- Publish one standard set of Kondo label names — members using different spellings break the automatic number-tracking.
- Define the Red / Blue target numbers (or decide on one target).
- Hand over the call-audit material for the Sales Call Analyzer.
Sign-offs & setup
- Spot-check each tool's live output to confirm it's your method, not generic AI advice.
- Approve the lesson → tool unlock map.
- Confirm your Circle plan supports the automatic Studio login (it needs Circle's Business plan), or we add a manual access step.
- Confirm none of your own content still uses old names ("216", "Co-Pilot", "Mentor").
The three that unblock everything else
- Tiers + pricing + what each gets — nothing about access, gating, or payment can be built until this is set.
- The course-only decision — it's a separate product with its own access rules; define it or explicitly defer it.
- The playbook audit + label standardization — every automation's quality depends on your content being clean.