Plan and Outline a Digital Product or Course

1. Go to claude.ai and start a **new chat** (keep everything in this thread through step 5). 2. Paste this prompt and fill in the brackets: "I'm planning a digital product or course. Context: - Topic / niche: [one sentence] - Likely format: [async video course OR live cohort OR templates / downloads OR hybrid] - What I'm NOT willing to teach or include: [honest limits] Your job: help me define ONE clear transformation. Reply with: A) One sentence describing my **ideal reader** (who they are, what stage they're at) B) Their **skill level** going in (beginner / intermediate / advanced) C) **One transformation** after they finish — stated as: "After completing this, they can ___" (must be a single outcome, not a list) D) **Explicit exclusions** — what this offer will NOT cover (bullet list) E) Push back if I'm combining too many outcomes — suggest what to cut or spin into a separate product" 3. Read Claude's reply. If the transformation still sounds like 3+ outcomes squashed together, reply: "That's still too broad. Force ONE transformation only — merge or cut until it fits in one sentence." 4. Repeat until you accept the single transformation line. 5. Copy the final transformation sentence into your notes — you'll reuse it in every later prompt.

1. In the **same chat**, paste: "Using the transformation we locked in, propose a working **product title** (3 options) and exactly **3–5 modules**. Rules: - Each module must have a **student-facing outcome** — what they can do or have after that module, not a topic label. - No lesson lists yet. - No more than 5 modules. If you think we need more, merge modules instead. Format as a markdown table: | # | Module title | Outcome after this module | |---|--------------|---------------------------|" 2. Pick your favorite title option or blend two — rename anything jargon-heavy into plain language. 3. If you see **more than 5 rows**, delete or merge until you have at most 5. 4. Save the table — it's the spine for the next steps.

1. Still in the **same chat**, paste: "For each module in our table, design lessons. Constraints: - **4–7 lessons per module** (fewer is OK for a short product). - Each lesson row: **Lesson title** | **One objective** written as **Learner can ___** (use concrete verbs: write, build, diagnose, calculate…) - Add **estimated minutes** (15–45 typical) and **format hint**: video walkthrough | worksheet | template build | live touchpoint - Objectives must not duplicate across lessons — if two sound the same, merge lessons. Output one section per module with a markdown table." 2. Scan for duplicate objectives — ask Claude to merge any repeats. 3. If any lesson has fuzzy objectives ("understand marketing"), ask: "Rewrite objectives as observable actions — what would I see on screen or in a submitted file?"

1. In the **same chat**, paste: "For each lesson in the outline, add: - **Practice:** one exercise, worksheet prompt, mini-project, or template task - **Done looks like:** what artifact or checklist proves they finished (be specific) - **Feedback:** tag each lesson as **solo self-check** OR **needs peer/async feedback** (e.g. cohort critique, office hours, async Loom review) Keep exercises proportional to lesson length — a 20-minute lesson shouldn't have a 6-hour project. Return updated tables with new columns: Practice | Done looks like | Feedback model" 2. Scan for lessons with **only** "watch the video" — ask Claude to add at least a worksheet or checklist for those. 3. Circle any lesson that needs feedback but you're building async-only — decide later in pricing step or downgrade to self-check.

1. In the **same chat**, paste: "Given our outline, propose: 1) **Delivery format** — async only, cohort, or hybrid; justify in 2–3 bullets. 2) **Pricing ladder** — either **one tier + bonuses** OR **2–3 tiers**. For each tier: name, price range (USD), who it's for, what's included, access length. 3) **Stack placeholders** — only name tools (e.g. Teachable, Gumroad, Circle, Skool, Stripe). No signup instructions. 4) **If cohort:** what live touchpoints exist (calls, Slack weeks). **If async:** how support works (none, email, community). Keep everything outline-level — we're not implementing yet." 2. If you're torn on cohort vs async, ask Claude for a **decision matrix** (time you have, price point, feedback-heavy lessons). 3. Pick one ladder to carry into your export doc — you can revise pricing later.

1. Open **Google Docs** (or **Notion** if you prefer — same structure). 2. Create a new doc titled: **[Working title] — Curriculum outline** 3. Scroll up in your Claude chat and **copy the full outline** (transformation, modules, lessons, practice rows, pricing sketch). 4. Paste into the doc. Add headings: **Promise** | **Modules & lessons** | **Practice & deliverables** | **Pricing & format** 5. Add a final section **Launch milestones** with bullets only — example: - Outline locked - Beta / pilot students - Record / build assets - Publish sales page - (Optional) cohort dates 6. Read once for continuity — fix anything that references "see above" without context. 7. Share link with yourself or save in your product folder.