Find the problem and the people
Map a real workflow. Interview potential users. For individuals, test a working relationship with potential cofounders.
You leave with A problem brief, a user map, and an initial team agreement.
The curriculum
Less time in lectures.
More evidence from building.
A proposed twelve-week rhythm with clear milestones, working sessions, and time to make something real.
Rolling enrollment. Your start date, format, support, and participation terms are confirmed before you join. Applying does not commit you to equity or fees.
Test the hardest assumption
Build a small technical experiment. Establish a baseline, data rights, and a way to measure whether the approach works.
You leave with A reproducible experiment and a decision to continue, change, or stop.
Build one useful workflow
Create a usable prototype around one job. Review the interface, architecture, reliability, cost, and failure modes.
You leave with A prototype someone outside the team can try.
Put it in someone’s hands
Observe use. Find a design partner. Test adoption and pricing assumptions while documenting technical limitations.
You leave with A pilot plan, user observations, and a revised product.
Build the company around the work
Resolve ownership and university/employer IP questions. Draft the commercial model, operating budget, and founder responsibilities.
You leave with A company-readiness checklist and a six-month operating plan.
Show the evidence and choose what’s next
Demonstrate the actual product and what users taught you. Prepare a decision about customers, grants, investment, or more research.
You leave with A working demonstration, evidence brief, and next milestone.
A week with
room to work.
Monday: priorities
Set one meaningful weekly goal, name the blocker, and decide what evidence you need.
One working review
Bring the prototype, experiment, or customer learning to a focused product or technical review.
One mentor session
Use office hours for a specific decision. Specialist clinics replace a session when relevant.
Friday: show what changed
Share the work and the next decision. Keep the rest of the week available for building and customers.
Different tracks. Shared milestones.
AI and science teams may need research validation. Health teams may first need data permissions and a safe scope. Hardware teams may begin with simulation or design tools. Milestones should match the work, without promising clinical trials, fabrication, or wet-lab facilities.
Bring your curiosity. We’ll start there.
Apply with a company, an early idea, or simply the skills and ambition to build one.