Instructor Book with deeper day-by-day content you can actually teach from.
This is the founder-only teaching surface: opening frames, what to teach, live demos, rescue lines, build drills, and what must be locked before each class ends. Students should never see this side.
Every tab below includes the content you actually need in the room: opening language, lessons, demos, drills, rescue lines, and dismissal locks.
Day 1
Product Lock, Standards, and Platform Identity
Kill vagueness. Lock the product, target user, pain, transformation, recurring value, and first-version scope.
Opening frame
“Today is not about being vaguely creative. Today is about getting specific. A vague product is not a product. A vague audience is not an audience. A vague promise is not a business.”
What to teach
Explain the difference between an app idea and a platform concept.
Force one user, one repeated pain, one transformation, and one recurring reason to return.
Teach the five locks: product name, target user, problem, transformation, recurring value.
What to demo live
Take a weak idea and sharpen it live into a product statement.
Model a clean one-page product blueprint with 3 features max.
Build drills
Have every student write a 60-second product lock statement.
Run “too broad / too vague / too many features” corrections publicly.
Rescue lines
“That is not a buyer. That is a population.”
“What repeats here monthly?”
“What changes after they use your app?”
Must lock before dismissal
Product name
Target user
Problem and transformation
Primary feature
Version-one scope
Homework / next step
Tighten the one-sentence positioning line and cut anything that does not belong in version one.
Day 2
Brand System, User Journey, and App Structure
Make the product visible. Build the first branded shell and map the user journey.
Opening frame
“A real product tells the user where they are, what it does, and what to do next. If the first screen confuses them, the app is already losing.”
What to teach
Teach headline, subheadline, CTA, navigation, workspace, and trust path.
Split the app into public surface, work surface, and result surface.
Teach “land → understand → click → use → receive result → return.”
What to demo live
Build a homepage shell and a dashboard shell.
Rewrite weak homepage copy into direct product language.
Build drills
Students sketch or build their shell.
Each student explains the first action a user takes in five seconds.
Rescue lines
“Tell the truth faster.”
“What is the main action?”
“What belongs on page one and what does not?”
Must lock before dismissal
Homepage copy
CTA path
Page map
Main workspace frame
User journey
Homework / next step
Finish headline, subheadline, CTA, and the main first-screen structure.
Day 3
Build the First Real Lane
Make the app honest. One lane must actually work from input to result.
Opening frame
“Today fake apps die. If it only looks like it works, today is the day that stops.”
What to teach
Break one feature into input, action, process, output, saved state, and next step.
Teach that one strong lane beats six fake features.
Keep them from feature sprawl.
What to demo live
Build one real flow all the way through: intake → action → result.
Show success, empty, and correction states.
Build drills
Students choose one lane only.
Each student must demo their lane in under two minutes before class ends.
Rescue lines
“No second feature.”
“What does the user get back?”
“Would you let a stranger use this?”
Must lock before dismissal
One real working lane
Honest button labels
Output formatting
Empty and success states
Homework / next step
Remove dead controls and clean the flow until it can be shown without explanation.
Day 4
AI Lane, Automation Logic, and Infrastructure Thinking
Treat AI like a governed service lane inside the product, not magic dust.
Opening frame
“AI is not the product. It is a capability inside the product. Today we make the intelligence serve the workflow instead of distracting from it.”
What to teach
Use the simple logic model: screen → brain → save → result.
Translate that into frontend, processing layer, state, and output.
Teach useful AI jobs: transform, summarize, classify, generate, support.
What to demo live
Build one structured AI lane with a clear result surface.
Show how to make the output usable instead of generic.
Build drills
Students add one AI or automation lane only.
Run output quality reviews: what makes this actually useful?
Rescue lines
“Why is AI the right tool here?”
“What should the result look like?”
“Does this make the workflow clearer or messier?”
Must lock before dismissal
One AI or automation lane
Structured input/output
Review step
Usable result formatting
Homework / next step
Tighten the prompt or logic and improve the result surface.
Day 5
Monetization, Offer Design, and Commercial Structure
Wrap a clean offer around the product so it can actually be sold.
Opening frame
“If your product cannot be explained commercially, you do not have a business yet. Today we turn the product into an offer.”
What to teach
Teach the difference between product, offer, buyer, and user.
Show monthly subscription, setup plus monthly, and support-based options.
Force recurring value logic.
What to demo live
Build a pricing / offer section live.
Write offer copy around outcome, not around feature clutter.
Build drills
Students state buyer, user, offer, and recurring reason.
Rewrite weak pricing language into clear value language.
Rescue lines
“What exactly is being sold?”
“Who signs off on buying this?”
“Why would they keep paying next month?”
Must lock before dismissal
Offer structure
Pricing direction
Buyer logic
CTA and follow-up path
Homework / next step
Tighten the pricing copy and the reason the buyer cares.
Day 6
Trust, Proof, Authority, and Launch Readiness
Make the app believable enough to show without standing next to it.
Opening frame
“Trust is not decoration. Trust is product language, proof, contact, and completeness.”
What to teach
Teach about sections, proof sections, contact blocks, FAQ, and trust surfaces.
Use honest proof instead of hype.
Run the polish pass on readability, spacing, labels, and links.
What to demo live
Add trust modules to a sample product and show how it changes credibility.
Show proof blocks, founder/about logic, and clean CTA flow.
Build drills
Students add about, proof, FAQ, and contact.
Run a trust audit: would a stranger believe this?
Rescue lines
“Why should a stranger trust this?”
“What proof can you actually show?”
“Can someone contact you right now?”
Must lock before dismissal
Trust surface
Proof block
Contact block
Polished CTA path
Homework / next step
Fix broken links, remove fake elements, and polish visible pages.
Day 7
Final Demo, Operator Handoff, and Next-Step Path
Present a coherent product story with a real next-step path.
Opening frame
“Today is not a celebration of effort. It is a presentation of outcome.”
What to teach
Teach the five-minute demo structure: name, user, problem, main lane, AI lane, offer, next step.
Coach them to start with the result and end with the business path.
What to demo live
Run a model final demo.
Show how to avoid rambling and stay outcome-first.
Build drills
Students rehearse in pairs before final demos.
Run scoring against clarity, coherence, feature honesty, AI lane, trust, and presentation.
Rescue lines
“Start with the result.”
“Show the strongest lane first.”
“Do not narrate your struggle. Show the product.”
Must lock before dismissal
Five-minute final demo
Operator handoff packet
Next-step roadmap
Homework / next step
None. Ship the presentation cleanly.
4-hour rhythm
Use the same class spine every day
Hour 1 · Frame + teach
State the outcome for the day, teach the concept, and show exactly what strong output looks like.
Hour 2 · Build-along
Model the build yourself. Keep it clean, explain the logic, and stop before overbuilding.
Hour 3 · Student sprint
Students build their own version while you correct scope, copy, clarity, and fake lanes fast.
Hour 4 · Review + lock
Students demo what exists now. No vague promises. Lock the day before anyone leaves.
Example live product lanes
Fast examples to teach from
Service intake and proposal generator for local businesses
Internal operations board for tasks, approvals, and notes
AI content engine for niche authority publishing
Directory or resource search app with filters and output cards
Client request portal with structured summaries and status tracking
Community or youth support portal with role-based resources
Fast interventions
Lines to use when the room drifts
What is this actually for?
Who pays for this?
What happens right after the click?
What does the user get back?
Why would they return?
What can we cut?
What is still fake?
Founder reset
Two-minute room reset prompt
Use this if the room starts drifting into chaos:
Stop building for two minutes. Answer these now:
What is your product?
Who is it for?
What is the main working lane?
What is still fake?
What are you locking before class ends?
Founder session is locked on this device. Use Founder Access first.
