How to teach entrepreneurship so students actually build something
Students remember the part of an entrepreneurship course where they had to do it: the interview that killed their idea, the price nobody would pay, the pitch that went better than expected. The hard part for the instructor is giving every team that experience every week without throwing out the lectures, readings and cases that already work. This is a plan that keeps both.
The weekly rhythm: teach it Monday, apply it by Friday
The simplest structure that holds up over a semester is a fixed week. The lecture stays the lecture. Outside class, each team applies that week's topic to its own company, and the work is due at the same time every week. A fixed rhythm matters more than any single assignment, because it lets students plan and lets you grade in one sitting.
Monday, in class
Teach the topic: opportunity recognition, customer discovery, business models, pricing.
Tuesday to Thursday
Teams do the team hand-in for that topic. Each student also owns an individual role piece (CEO, CFO, CMO, COO or CTO), which is how you see who did the work.
Friday
Hand-ins lock. Each student writes a short memo: what the team decided, what they learned, what changed.
Every one to three weeks
A short earnings call: each team reports to the class in a few minutes. It keeps teams honest and lets them learn from each other.
A nine-week plan
Nine weeks takes a team from a problem to an investor presentation. Fifteen-week semesters fit it with room for exams and guest speakers; a twelve-week version adds a second product version, real orders, deeper finance and a rehearsal week before Demo Day.
| Week | Topic | What each team hands in |
|---|---|---|
| 1 | Problem + market | Pick a real problem, write three testable hypotheses, size the market and pitch it on Launch Day. |
| 2 | Solution + business model | The product concept, who pays and how, and the first customer interviews. |
| 3 | Market research + competition | Where the industry is heading, what customers already say, a competitor map and the one difference that matters. |
| 4 | Build the MVP | Brand, a live website and a prototype a customer can react to, demoed in a sales pitch round. |
| 5 | Marketing + sales | A two-week growth plan, a media kit, an ad design and the partners who make it happen. |
| 6 | Financial planning | Startup costs and a launch budget, a 12-month pro forma P&L, cash flow and runway. |
| 7 | Pricing + unit economics | A pricing strategy, unit economics, and what customers pay for the alternative today. |
| 8 | Operations + fundraising | How the work gets done, a hiring plan, a funding strategy and what the raise does to ownership. |
| 9 | Scale + investor presentation | A 12-month growth plan, the investor presentation on Demo Day, and a final memo on what they believed, learned and changed. |
Mapping it onto a syllabus you already have
You don't need to adopt anyone's week order. Take your existing syllabus, find the closest module for each week, and leave the rest as lecture only. Here is a typical fifteen-week syllabus, mapped:
| Week | Your topic | Hands-on module |
|---|---|---|
| 2 | Opportunity recognition | Problem + market |
| 3 | Customer discovery | Customer discovery interviews |
| 5 | Business models | Solution + business model |
| 6 | Midterm | Lecture only |
| 7 | Prototyping and MVP | Build the MVP |
| 9 | Pricing | Pricing + unit economics |
| 10 | Financial projections | Financial planning |
| 12 | Legal structures | Legal + formation |
| 14 | Pitching to investors | Investor presentation + Demo Day |
Assessing team work fairly
Three things make team projects gradable. First, a rubric per deliverable that students see before they start, so the grade is about quality rather than whether a box was filled. Second, individual pieces inside the team's work: role pieces and each student's own customer interviews mean a name sits against every part. Third, locked hand-ins with sources attached, so you grade exactly what was submitted and can check where a claim came from.
For the AI question, the policy that works is to treat it as a tutor: students may ask it anything and it should answer with questions and pointers, not finished paragraphs, and any assignment that uses it deliberately should say so. Students sign a short statement on each hand-in that the decisions, writing and research are theirs.
Pitching it to the room
The same plan works from a first course for any major to an MBA seminar if two things change. How technical: intro sections get plain-language prompts, worked examples and one number at a time; upper-level undergraduates do real interviews, set a price and build a 12-month forecast with sources; graduate sections do driver-based forecasts, sensitivity, 13-week cash and a cap table across two rounds. How much time: about two hours a week for the team hand-in alone, four with individual role pieces, six with the memo, earnings calls and a class market.
Velofound Classroom runs this whole structure, from hand-ins, rubrics and role pieces to the gradebook and an optional class venture market, and maps it onto your syllabus for you. See how it works, or read how it compares to a decision simulation.
Common questions
How do you make an entrepreneurship course hands-on without losing the lectures?
Keep the lecture and add one applied hand-in per week: teach the topic on Monday, and by Friday each team applies it to its own company. The lecture supplies the concept; the hand-in makes students use it on a real problem.
Should students work in teams or alone?
Teams of three to five work best for a company-building course, as long as each student owns an individual piece every week. Without individual pieces, a team grade hides who did the work.
Do students need a real business idea to start?
No. Week one is finding a problem real people have. A good problem matters more than a good idea, and the customer interviews in the first weeks usually change the idea anyway.
How many weeks does a hands-on entrepreneurship project need?
Nine weeks takes a team from a problem to an investor presentation. Twelve adds a second product version and deeper finance. Three weeks is enough for one sprint inside a longer course.
How should students use AI in an entrepreneurship course?
As a tutor that asks questions and points to sources, not as a writer. Make any assignment that uses AI on purpose say so, and ask students to sign that the decisions, writing and research are their own.
Send us your syllabus.
We'll send back your course: every week mapped to a module at your level and length, within seven days. No commitment until you approve it.
See Velofound Classroom →