Below is a day-by-day outline for the 7-Day First Product Sprint that your VA/designer can turn into:

• A PDF workbook

• A simple course outline (7 modules, 7 days)

• Daily checklists + templates

I’ll assume they’re coming into the Sprint with:

• The Snapshot Workbook done

• 1 main idea chosen

• A rough one-sentence offer

7-Day First Product Sprint

Working promise:

“In 7 focused days, you’ll turn one of your chosen ideas into a real product with a simple sales page and a way to take payment.”

Day 0 – Orientation (Pre-Work)

Goal: Show up prepared so Day 1 is not spent “catching up.”

What they do before Day 1:

• Re-read their Snapshot Workbook output

• Confirm:

  • Chosen idea

  • Who it helps

  • Problem it solves

• Gather:

  • 3–5 stories from their career related to this problem

  • Any existing materials: slides, checklists, SOPs, notes

Deliverables:

• One chosen offer idea

• One sentence: “This week I am building: ______”

You can present this as a short orientation video + 1-page checklist.

Day 1 – Position & Promise

Theme: Get brutally clear on who it’s for and what it promises.

Big goal for Day 1:
By the end of the day they have a sharp, believable “Who + Problem + Outcome” that everything else hangs on.

Components:

1. Refine the Who

   • “Who is the specific person this product is for?”

   • Prompt examples:

     • “New clinic managers in small medical practices”

     • “Boomer small business owners with 3–10 employees”

     • “Newly retired nurses starting consulting”

2. Define the Core Problem

   • One sentence in their customer’s language:

     • “I keep losing new staff before they hit 90 days.”

     • “I’m terrified I’ll mess up compliance and get fined.”

3. Craft the Product Promise
   Use a template like:

   “In [time frame], you’ll go from [frustrating situation] to [clear outcome] without [big fear].”

   Example:

   • “In 30 days, you’ll go from ‘winging it’ with new hires to running a simple onboarding system that keeps your best people.”

4. Name the Product (Good Enough Name)

   • Simple, descriptive, not cute:

     • “New Hire 90-Day Onboarding Playbook”

     • “Clinic Calm: Difficult Patient Conversation Scripts”

Day 1 Deliverables:

• Final Who statement

• Final Problem statement

• Final Promise sentence

• Working Product Name

Day 2 – Decide the Format & Scope

Theme: Make the product small enough to finish, big enough to be valuable.

Big goal for Day 2:
Decide exactly what kind of product this will be and what’s in / out.

Components:

1. Choose 1 Primary Format
   From a short menu:

   • Short guide / playbook (PDF)

   • Live or recorded workshop (60–90 minutes)

   • Checklist + template bundle

   • Starter toolkit (combo of the above, but still tight)

2. Define 3–5 Core Components

   • If it’s a playbook: 3–5 sections

   • If workshop: 3–5 segments

   • If bundle: 3–5 tools (checklist, SOP, template, script, etc.)

3. Set Constraints

   • Target time to deliver:

     • Readable in under 90 minutes, or

     • Watchable in under 90 minutes

   • “No extra modules.” If it doesn’t serve the Day 1 promise, it’s out.

4. Draft a Simple Table of Contents
   Example for a guide:

   • Section 1: Where most clinics lose new staff

   • Section 2: The 3-step onboarding rhythm

   • Section 3: First-week scripts and checklists

   • Section 4: How to run 30/60/90 day check-ins

Day 2 Deliverables:

• Chosen product format

• List of 3–5 core components

• Draft Table of Contents / Section List

Day 3 – Outline the Content (Don’t Write It All)

Theme: Skeleton first, flesh later. No “write the whole book” trap.

Big goal for Day 3:
A tight outline with bullets for each section, not polished prose.

Components:

1. For Each Section / Component:
   Create a mini-outline:

   • Purpose of this section

   • 3–7 bullet points they’ll cover (steps, ideas, examples)

   • Any stories they’ll tell (from their career)

   • Any tools that belong here (checklists, scripts, templates)

2. Use a Simple Prompt Pattern
   For each section, answer:

   • “What does the person not know yet?”

   • “What mistake are they currently making?”

   • “What new way of seeing this do I need to give them?”

   • “What do I want them to do differently after this section?”

3. Identify Where AI Can Help Draft

   • Mark sections with “AI can draft first pass.”

   • Mark sections where only they can write (stories, examples, unique know-how).

Day 3 Deliverables:

• Fully filled outline for each section (bullets, not paragraphs)

• Notes on where to use AI to draft vs. where they write personally

Day 4 – Build the Core Asset (MVP Version)

Theme: Create a usable Version 1. Ugly but complete.

Big goal for Day 4:
Finish a rough but complete first version of the product.

Components:

1. Draft Using the Outline

   • Use ChatGPT/AI to turn Day 3 bullets into paragraphs, then edit for voice.

   • Or record audio talking through the outline, then transcribe and clean.

2. Keep It Simple

   • One font, simple formatting.

   • Clear headings and bullet points.

   • No obsessive design polishing.

3. Create / Extract Tools

   • Turn steps into checklists.

   • Turn “do this like this” into templates or scripts.

   • Make sure the person can do something after using it.

4. Quick Internal Sanity Check
   Answer:

   • “Could my past self follow this and get value?”

   • “Is anything obviously missing for them to act?”

Day 4 Deliverables:

• Draft Version 1 of the product (PDF draft, slide deck, or script/outline for the workshop)

• Draft checklists/templates that go with it

Day 5 – Create a Simple Sales Page Skeleton

Theme: Sell it like an adult. No hype, just clarity.

Big goal for Day 5:
A functional, copy-complete sales page (or long-form checkout page).

Components:

Use a standard structure (your VA can turn this into Elementor sections):

1. Headline

   • “Turn [who’s] [pain] into [outcome] in [time]”

2. Subheadline

   • One sentence about who it’s for and what it does.

3. Problem Section

   • 3–5 bullets describing their current frustration in their language.

4. Promise / Outcome Section

   • What life looks like “after” using your product.

5. What’s Inside / Module List

   • The 3–5 components from Day 2 written as benefits.

6. Who It’s For / Who It’s Not For

   • Filter and attract.

7. Price & Guarantee

   • Starter price (e.g., $49, $97, whatever makes sense for them)

   • Simple guarantee: “If you use it and it doesn’t help, email me.”

8. FAQ

   • 3–5 basic questions (time, tech level, who it’s for, etc.)

Day 5 Deliverables:

• Complete sales page copy in a doc (ready to hand to VA)

• A clear product price and guarantee statement

Day 6 – Tech & Delivery Setup

Theme: Make it buyable and deliverable, not perfect.

Big goal for Day 6:
A working, end-to-end flow: sales page → payment → delivery.

Components:

1. Pick a Simple Payment Method

   • Gumroad, ThriveCart, WooCommerce, Stripe checkout link, etc.

   • One product, one price.

2. Upload or Connect the Product

   • PDF or zip folder.

   • Workshop link (Zoom, Loom, etc.) if it’s a live or recorded event.

3. Set Up Delivery

   • Automatic email with:

     • “Thank you”

     • Link to download / access

     • How to get support if stuck

4. Connect the Sales Page Button

   • “Get the [Product Name]” → direct to checkout.

5. Test the Whole Flow

   • Click from sales page to checkout.

   • Do a test purchase (or at least a test run through).

   • Confirm delivery email and links work.

Day 6 Deliverables:

• Live checkout link

• Live delivery email

• Sales page button connected and tested

Day 7 – Launch & First 10 Eyeballs

Theme: Don’t wait for perfection. Put it in front of real humans.

Big goal for Day 7:
Get the product in front of at least 10 real people and collect early proof.

Components:

1. Send a Simple Launch Email
   Template:

   • Subject: “I built this for you” or “New: [Product Name]”

   • Body:

     • Acknowledge the problem.

     • Explain what you made and who it’s for.

     • Link to the sales page.

2. Post Once on One Platform

   • LinkedIn, Facebook, or email to a small personal list.

   • Keep it simple:

     • “Here’s the problem you have.”

     • “Here’s what I built.”

     • “Here’s the link.”

3. Invite 2–3 “Friendly Beta Buyers”

   • Former colleagues, clients, people who already trust them.

   • Offer:

     • A beta price or

     • Bonus (short call, extra template) in exchange for feedback/testimonial.

4. Collect First Feedback / Wins

   • Ask:

     • “What was most useful?”

     • “What was confusing?”

     • “Would you recommend this to someone like you?”

Day 7 Deliverables:

• 1 launch email sent

• 1 simple public post made

• At least 10 real people have seen the sales page

• At least 1–3 early buyers or testers (if possible)

• Notes for “V1.1 improvements” based on feedback

Wrap-Up – What They Leave With

By the end of the 7-Day First Product Sprint, they should have:

• A clearly positioned product (Who + Problem + Promise)

• A real, usable asset (guide, workshop, toolkit, etc.)

• A complete sales page with adult, no-hype copy

• A working payment + delivery flow

• Initial exposure to real humans and, ideally, at least a couple of real buyers

If you want, I can now:

• Turn this into a workbook structure like we did for the Snapshot Workbook (with exercises and blanks), or

• Draft the sales page copy for the 7-Day First Product Sprint so it slots neatly between the Snapshot Workbook and your AI Clone Launchpad.