Week 7: Build the Product Core
Translate the curriculum into product loops: onboarding, progression, review, and admin visibility.
What the machine expects from you.
This lesson turns the curriculum into product logic. You are defining how the learner moves through the system and where the system applies pressure.
A strong course can still fail as a product if the loop is muddy. If users do not know what to do, what they owe, and what happens next, the product loses force.
Think in states and transitions: visitor, onboarding, active learner, submitted, under review, revise, complete, blocked, capstone-ready.
This lesson focuses on the runtime contract that makes the course feel alive: roadmap generation, progression state, and structured review feedback.
Three dense lessons, one enforced deliverable.
Define the SaaS Loop
A learning product is a state machine disguised as an interface.
LessonRoadmaps, Progress, and AI Review Loops
Progression only matters when it changes user behavior.
LessonAdmin Controls and Operational Trust
Admin surfaces exist to preserve trust, not to look enterprise.
What survives the week.
Product Loop Map
A map of onboarding, learning, submission, review, and progression states.
A product loop map, review system flow, and admin spec.
Each week leaves behind portfolio evidence that compounds into the final SaaS and its operating narrative.