Lean LaunchPad Syllabus Pitch Deck Teardown

A detailed teardown of Steve Blank's Lean LaunchPad syllabus for Berkeley and Columbia, focusing on the methodology of customer development and business.

The Lean LaunchPad syllabus, Revision 7, serves as a foundational manual for the experiential entrepreneurship course led by Steve Blank. Spanning 21 pages, it details a curriculum centered on the Business Model Canvas and the 'get out of the building' philosophy. Unlike a standard pitch deck, this document defines the expectations for student teams: conducting dozens of customer interviews, iterating on business model hypotheses, and presenting 'lessons learned' rather than polished sales pitches. It emphasizes that startups are not smaller versions of large companies but temporary organizat…

Key takeaways

Lean LaunchPad Syllabus: The Methodology of the Search

The document provided is the Revision 7 syllabus for XMBA 296T, 'The Lean LaunchPad,' taught at the University of California at Berkeley and Columbia Business School. Lead instructor Steve Blank, along with co-instructors Jon Feiber and Jim Hornthal, outlines a course that rejects the traditional business plan in favor of evidence-based entrepreneurship. This teardown examines the syllabus as a foundational framework for how early-stage startups should approach the fundraising and development process.

Slide 1: Course Overview and Required Texts

Slide 1 establishes the academic and practical rigor of the course. It lists two primary required texts: Steve Blank's 'Four Steps to the Epiphany' and Alexander Osterwalder's 'Business Model Generation.' These texts define the two pillars of the course: Customer Development and the Business Model Canvas. The slide explicitly states that the class format involves 'tens of hours of work talking to customers' and that the goal is to show 'how startups really get built.' It clarifies that the end result is not a PowerPoint deck for a VC presentation, but a practical experience in the chaos of a startup.

Slide 2: Class Culture and Workload

Slide 2 sets expectations for 'Class Culture.' It warns students that the environment will be 'brusque and impersonal' at times, designed to create immediate action in time-constrained settings. The workload is described as 'phenomenal,' with teams reporting up to 20 hours of work each per week . The core mantra is introduced: 'Getting out of the classroom is what the effort is about.' This slide serves as a filter, discouraging those who cannot commit to the intense customer interaction required.

Slide 3: Team Organization and Deliverables

Slide 3 details the structural requirements. Teams must be self-organized and projects must be approved before the class begins. There are no formal CEOs or VPs; instead, the focus is on constant parsing and allocation of tasks. Deliverables are split by product type: physical products require a costed bill of materials and a prototype , while web products require a functional site with active customer use. A weekly blog is mandatory to measure progress.

Slide 4: Grading Criteria and Feedback

Slide 4 breaks down the Grading Criteria . The largest portion, 40% , is allocated to 'out-of-the-building progress' measured by weekly blog write-ups. Team 'lesson learned' summaries account for 20% , and the final report for 25% . Individual participation is only 15%. This weighting reinforces that the value lies in the process of discovery rather than the final pitch. The slide also prepares students for 'Critical Feedback,' noting that the teaching team will challenge points of view publicly.

Slide 5: The Class Roadmap

Slide 5 provides a visual 'Class Roadmap' utilizing the Business Model Canvas . It lists the nine building blocks: Key Partners, Key Activities, Value Propositions, Customer Relationships, Customer Segments, Key Resources, Channels, Cost Structure, and Revenue Streams. Each block is associated with specific 'Test Hypotheses.' For example, under Customer Segments, teams must test Problem, Customer, User, and Payer hypotheses. The slide quotes: 'Genius is the ability to make the most mistakes in the shortest amount of time.'

Slide 6: Pre-class Preparation

Slide 6 outlines the immediate requirements for students before the first session. This includes reading the first 51 pages of 'Business Model Generation' and the first two chapters of 'Four Steps to the Epiphany.' It reiterates the hard rule: 'NO ONE WILL BE ADMITTED TO THE CLASS WITHOUT BEING PART OF A TEAM AND HAVING AN APPROVED PROJECT.' This ensures the course starts at full speed without administrative delays.

Slide 7: Block 1 - Intro and Business Model

Slide 7 covers the first block, focusing on the definition of a startup and the 9 parts of a business model. It introduces the concept of the Minimum Feature Set (now commonly known as MVP). Teams are tasked with presenting their first canvas hypotheses and determining market size. The reading list includes Steve Blank's blog posts defining a startup as a 'temporary organization' rather than a smaller version of a large company.

Slide 8: Block 1 Continued - Value Prop and Customer Segment

Slide 8 details the specific assignments for testing the Value Proposition and Customer Segment. Teams must estimate TAM, SAM, and addressable market . The 'out of the building' assignment requires talking to 10-15 customers face-to-face . Web teams are instructed to get a 'low-fidelity web site' running to test the customer problem immediately.

Slide 9: Block 2 - The Channel and Customer Relationships

Slide 9 moves into distribution channels (direct, indirect, OEM) and demand creation. A unique requirement for web teams is to 'actually engage in search engine marketing (SEM) and spend $20 as a team to test customer acquisition cost.' This forces students to move beyond theoretical models into actual paid acquisition testing. They must track Google Analytics and measure the success of their messaging.

Slide 10: Block 2 Continued - Viral Coefficients and Non-Web Teams

Slide 10 addresses virality and non-web specific tasks. Teams assuming virality must show the 'viral propagation' of their product. Non-web teams (physical products) must interview 10-15 people in their channel, such as salesmen or OEMs, and calculate the 'cost' of their channel versus the selling price. All teams must update their blog/wiki with initial feedback and entry barrier analysis.

Slide 11: Block 3 - Revenue Model and Resources

Slide 11 focuses on the Revenue Model . Teams must present their packaging, pricing, and key financial metrics. They are required to test pricing in front of 100 customers (web) or 10-15 customers (non-web). The second half of the slide covers Key Resources and Activities , asking teams to identify what hardware, software, or IP is needed and when they will reach a cash flow break-even point.

Slide 12: Block 4 - Cost Structure and Fund Raising

Slide 12, notably set 'in New York' for this specific revision, covers the Cost Structure . Teams must define their expense models and distinguish between costs and product iteration ramps. The second half introduces Fund Raising , covering friends and family, seed rounds, and Series A. It references Steve Blank's 'Lessons Learned' as a new type of venture capital pitch, focusing on the journey of discovery rather than just the destination.

Slide 13: Block 5 - Final Presentations

Slide 13 outlines the requirements for the final 30-minute 'Lessons Learned' presentation. A critical requirement is the inclusion of at least three Business Model Canvas slides : Version 1 (original idea), Version 2 (after iteration/pivot), and Version 3 (where they ended up). This visual progression is intended to show the evolution of the business based on customer data.

Slide 14: Student and Company Requirements

Slide 14 reiterates that the class must be taken for credit and requires 4 students per team. It defines the 'Company Ideas' suitable for the class, specifically 'high potential, scalable startups with a bold vision.' It contrasts these with 'Small Business Startups,' which provide employment for a family but are not the focus of this curriculum.

Slide 15: Scalable vs. Buyable Startups

Slide 15 provides specific definitions for the types of startups targeted. Scalable Startups are defined as those that can grow to $100s of millions per year and return 10-100x to venture investors. Buyable Startups are those that can grow to $10s of millions and are likely to be acquired for $5M-$25M (a 'flip'). The slide also mentions Social Entrepreneurship and Corporate Disruptive Innovation as valid paths.

Slide 16: Attendance and Participation

Slide 16 covers the administrative 'hard rules.' Missing the first class is grounds for removal. More than one unexcused absence results in a grade penalty. The slide also mentions 'cold calling' and the expectation that students are prepared to discuss their findings at any time. It explicitly forbids browsing the web or reading email during class.

Slide 17: Mentors and Team Dynamics

Slide 17 introduces the Mentor system. Each team is assigned an experienced entrepreneur or VC who has volunteered to guide them. Teams are expected to meet with their mentors at least every three weeks. The slide also addresses team dynamics, advising students to resolve 'pulling weight' issues within a week before involving the teaching team.

Slide 18: Intellectual Property (IP)

Slide 18 is one of the most important for founders to understand. It states that while students own the IP they brought in or developed, the class is an open forum . If a team is working on university-related technology, they must check with the Office of Technology & Licensing (OTL). Crucially, it notes that if a subset of the team decides to start a company later, they do not 'owe' anything to other team members for work done in class.

Slide 19: Transparency and Non-Disclosures

Slide 19 doubles down on the lack of secrecy. It explicitly states: 'NO. This is an open class. There are no non-disclosures.' It warns that all findings will be made public. It frames the class not as an incubator, but as a forum for learning through discovery and execution. It concludes with a warning: 'I'm not comfortable sharing what I learn with others what should I do? Don't take this class.'

Slide 20: Application Form

Slide 20 presents the application form used to select students. It asks for student ID, major, work experience, and 'unique talent.' Crucially, it asks for 'two business ideas you'd like to work on,' forcing applicants to demonstrate they have already thought about potential ventures before the course begins.

Slide 21: Mentor List

Slide 21 is a placeholder for the Mentor List, which was 'TBD' as of July 4th, 2011. This indicates the syllabus was a working document distributed to prospective students before the finalization of the volunteer mentor roster.

What Makes This Syllabus Effective?

The Lean LaunchPad syllabus is effective because it replaces the 'theatre' of entrepreneurship with the 'rigor' of scientific inquiry. By mandating 10-15 customer interviews per week, it forces founders to confront market reality before they spend significant capital. The requirement to show multiple versions of the Business Model Canvas (Slide 13) is a powerful tool for investors and founders alike, as it demonstrates a team's ability to listen to the market and pivot accordingly. The syllabus also sets clear, high-stakes expectations regarding workload and public critique, simulating the high-pressure environment of a real startup.

What is Missing?

While the syllabus is comprehensive for a 10-week course, it lacks depth in two key areas: Unit Economics and Post-Seed Scaling . The focus is almost entirely on the 'search' phase of a startup. While Slide 11 mentions revenue models, it does not require a deep dive into Lifetime Value (LTV) versus Customer Acquisition Cost (CAC) ratios beyond the $20 SEM test. Additionally, the syllabus does not address the legal complexities of equity splits or formal company incorporation, which often become points of failure for teams that decide to continue after the course ends.

What Founders Should Copy

Founders should adopt the 'Lessons Learned' presentation format (Slide 13). Instead of a static pitch deck that claims to have all the answers, a deck that shows the evolution of the business model based on specific customer interviews is far more persuasive to sophisticated investors. Founders should also emulate the rigorous interview quotas (Slide 8). Most early-stage failures stem from building products no one wants; setting a hard goal of 10-15 face-to-face interviews per week is the best insurance against this outcome. Finally, the distinction between Scalable and Buyable startups (Slide 15) is a vital mental model for founders to have before they approach investors, as it dictates the type of capital they should seek.

Frequently asked questions

What is the primary goal of the Lean LaunchPad course?
The goal is to provide an experiential learning opportunity showing how startups are actually built. It focuses on the search for a repeatable and scalable business model through customer discovery rather than writing a static business plan. Students are expected to 'get their hands dirty' by interacting with customers, partners, and competitors to navigate the chaos and uncertainty of early-stage entrepreneurship.
How does the course handle intellectual property (IP)?
The syllabus is very clear that the class is an open forum. There are no non-disclosures, and all presentations, customer discovery notes, and business model canvases will be made public. While students own the IP they bring in or develop, they must be comfortable sharing their findings and 'bouncing' ideas off peers. If a founder is uncomfortable with this transparency, the syllabus suggests they should not take the class.
What are the specific deliverables for the teams?
Deliverables include a weekly blog or wiki documenting progress, weekly in-class presentations of 'lessons learned,' a costed bill of materials for physical products, and a working low-fidelity website for web products. The final deliverable is a 30-minute 'Lessons Learned' presentation that must include at least three different versions of the Business Model Canvas to demonstrate how the team iterated based on customer feedback.
What is the 'Get Out of the Building' requirement?
This is the core requirement of the course. Teams are expected to spend up to 20 hours per week outside the classroom talking to customers. For each block of the Business Model Canvas (e.g., Value Proposition, Channels, Revenue Streams), teams must conduct 10-15 face-to-face interviews to validate or invalidate their hypotheses. The syllabus emphasizes that the end result is not a PowerPoint deck for a VC, but actual market data.
How are teams formed and projects selected?
Teams must self-organize into groups of four before the class begins. Projects must be approved by the teaching team and can be software, physical products, or services. The syllabus suggests choosing subjects where at least one team member is a domain expert. It explicitly prioritizes 'scalable' or 'buyable' startups over small lifestyle businesses, requiring projects to have high potential and a bold vision.

Lean LaunchPad (Berkeley/Columbia Syllabus) pitch deck: the facts

Company
Lean LaunchPad (Berkeley/Columbia Syllabus)
Year
2011
Stage
Academic / Pre-Seed
Slides
21
Sector
Education / Entrepreneurship Methodology
Deck type
Syllabus / Course Outline
Outcome
Standardized curriculum for NSF I-Corps and global accelerators
Headquarters
Berkeley, CA / New York, NY

Lean LaunchPad (Berkeley/Columbia Syllabus) pitch deck PDF

The full Lean LaunchPad (Berkeley/Columbia Syllabus) deck is embedded on this page and can be read slide by slide in the browser — no download or account required. Each slide is covered in the breakdown above.

Related fundraising guides (24)

Decks from the same year (1)

Decks from the same region (1)

Browse companies alphabetically (1)

More pitch deck teardowns (16)

Recently published pitch deck teardowns (12)

Fundraising library · Pitch deck examples · Investor directory · Founder database