Berkeley Columbia Syllabus Pitch Deck Teardown

Introduction to the Lean LaunchPad Syllabus

The document titled 'berkeley columbia syllabus rev 6' is a comprehensive 20-page syllabus for the XMBA 296T course, 'Advanced Entrepreneurship: The Lean LaunchPad.' This course, led by Steve Blank with co-instructors Jon Feiber and Jim Hornthal, represents the academic foundation of the Lean Startup movement. Unlike a traditional pitch deck, this document outlines the rigorous requirements for student teams attempting to build scalable startups within a single semester.

Slide 1: Course Overview and Philosophy

Slide 1 establishes the core tenets of the course. It is described as an 'experiential learning opportunity' that is 'not about how to write a business plan.' The syllabus explicitly states that the end result is not a PowerPoint deck for a VC presentation, but a real-world exercise in customer discovery and agile development. Required texts include Steve Blank’s Four Steps to the Epiphany and Alexander Osterwalder’s Business Model Generation . The prerequisite is a 'passion in discovering how an idea can become a real company' and the ability to 'work insanely hard.'

Slide 2: Workload and Team Organization

Slide 2 sets expectations for the intensity of the program. It warns that teams have reported up to 20 hours of work per week outside of class. Projects must be approved before the class begins, and teams are assigned a mentor—an experienced entrepreneur or VC. The slide emphasizes that there are no formal CEOs or VPs; teams must self-organize. Deliverables include a costed bill of materials for physical products and a live site with users for web products. A weekly blog is mandatory to measure progress.

Slide 3: Grading Criteria

The grading structure on Slide 3 reinforces the methodology. Only 15% of the grade is based on individual participation. The largest portion, 40%, is dedicated to 'out-of-the-building progress' as measured by weekly blog write-ups. These write-ups must include updates to the business model canvas, identification of which team member did which work, and a detailed report of the week's activities. Another 20% is for weekly 'lesson learned' summaries, and 25% is for the final report.

Slide 4: The Class Roadmap

Slide 4 introduces the Business Model Canvas as the central framework for the course. It visualizes the nine building blocks: Key Partners, Key Activities, Value Propositions, Customer Relationships, Customer Segments, Key Resources, Channels, Cost Structure, and Revenue Streams. The slide notes that each class is organized around student presentations of their 'lessons learned' from getting out of the building. It includes a quote: 'Genius is the ability to make the most mistakes in the shortest amount of time.'

Slide 5: Pre-class Preparation

Slide 5 details the requirements before the first day of class. Students must read the first 51 pages of Business Model Generation and the first two chapters of Four Steps to the Epiphany . Teams of four must be formed, and a preliminary product idea must be submitted for approval by August 29th. The slide includes a bold warning in red: 'NO ONE WILL BE ADMITTED TO THE CLASS WITHOUT BEING PART OF A TEAM AND HAVING AN APPROVED PROJECT.'

Slide 6: Block 1 - Intro and Business Model

The first block, scheduled for Sept 1st, begins with 'Speed Dating' to get feedback on initial concepts. The lecture covers the definition of a business model, the 9 parts of the canvas, and the concept of a Minimum Feature Set. Team deliverables for the following day include presenting the first business model canvas hypotheses and a plan for testing market size and each hypothesis. Teams are also required to start their blog/wiki/journal.

Slide 7: Block 1 - Value Proposition and Customer Segment

On Sept 2nd, the focus shifts to testing the Value Proposition and Customer Segment. The lecture asks critical questions: 'What is your product or service? How does it differ from an idea? Why will people want it?' The assignment for the next block requires teams to get out of the building and talk to 10-15 customers face-to-face. Web teams are required to get a low-fidelity website running to test the customer problem.

Slide 8: Block 2 - The Channel and Customer Relationships

Slide 8 covers the sessions on Sept 22nd and 23rd. The 'Channel' lecture discusses direct vs. indirect channels and B2B vs. B2C sales. The 'Customer Relationships' lecture covers demand creation, evangelism, and sales funnels. A specific requirement for web teams is introduced: they must engage in search engine marketing (SEM) and spend $20 as a team to test customer acquisition costs (CAC) using tools like Google Analytics.

Slide 9: Viral Propagation and Non-Web Teams

Slide 9 continues the Block 2 requirements. Teams assuming virality must show viral propagation and calculate their viral coefficient. Non-web teams are required to get a costed bill of materials and a working prototype demo, as well as interview 10-15 people in their channel (salesmen, OEMs, etc.). All teams must update their journals with feedback received and entry barriers identified.

Slide 10: Block 3 - Revenue Model and Key Resources

Scheduled for Oct 13th and 14th, Block 3 focuses on the Revenue Model. The lecture covers revenue streams and multi-sided markets. Teams must test pricing in front of 100 customers on the web or 10-15 customers for non-web projects. The following session covers Key Resources and Activities, requiring teams to assemble an income statement, a diagram of payment flows, and a resources assumptions spreadsheet (including people, hardware, and financing).

Slide 11: Block 4 - Cost Structure and Fund Raising

Block 4 takes place in New York on Nov 11th and 12th. The 'Cost Structure' lecture focuses on the expense model and the relationship between costs and product iteration. The 'Fund Raising' lecture covers the spectrum from friends and family to Series A rounds. The deliverable for the final session is a 30-minute 'Team Lessons Learned Presentation,' with required reading from Steve Blank on the new type of VC pitch.

Slide 12: Block 5 - Final Presentations

Slide 12 outlines the format for the final 'Lessons Learned' presentations on Dec 1st and 2nd. The presentation must include at least three versions of the Business Model Canvas to show how the business evolved. Slides must cover the initial idea, what the team did to 'get out of the building,' what reality they found, and how they iterated or pivoted. The final slide must address whether the team thinks this is a viable business and if they want to pursue it after the class.

Slide 13: Student Requirements and Company Ideas

Slide 13 reiterates that the class must be taken for credit and cannot be audited. Each team must have four Berkeley/Columbia students. It defines the types of startups acceptable for the class: 'high potential, scalable startups with a bold vision.' It lists categories including Small Business Startups, Scalable Startups, Buyable Startups, Social Entrepreneurship, and Corporate Disruptive Innovation.

Slide 14: Defining Scalable vs. Buyable Startups

Slide 14 provides specific financial definitions. 'Scalable Startups' are defined as those that can grow to $100s of millions in revenue, require $10M+ in venture funding, and return 10-100x investment. 'Buyable Startups' are typically web/mobile apps funded by angels with $100s of thousands, aiming for a flip to companies like Facebook or Google for $2M-$10M. The class only accepts teams doing scalable or buyable startups.

Slide 15: Attendance and Participation Rules

Slide 15 covers the 'house rules.' Attendance at the first class is mandatory. The instructors use 'cold calling' but allow students to opt-out if they are unprepared and notify the instructors beforehand. Habitual lateness is penalized, and students are expected to use name cards during every session.

Slide 16: Mentors and Team Dynamics

Slide 16 explains the role of mentors, who are volunteers expected to meet with teams at least every three weeks face-to-face. It also addresses team dynamics, noting that every team member is part of the 'customer development team.' If a teammate is not 'pulling his/her weight' for longer than a week, the teaching team should be notified, as this will reflect in individual grades.

Slide 17: Grading and Intellectual Property

Slide 17 repeats the grading percentages from Slide 3 and adds a section on Intellectual Property (IP). It states that students own the IP they brought to class and the IP they develop during the class. However, if a team uses Berkeley or Columbia-related technology, they must check with the Office of Technology Licensing (OTL). If a subset of the team starts a company later, they do not 'owe' anything to other team members for work done in class.

Slide 18: Public Nature of the Class

Slide 18 contains a critical warning: 'There are no non-disclosures.' Because the class is a forum for peer feedback, all presentations, notes, and blogs will be made public. The slide states that this is not an incubator and that successful companies are often less about the original idea and more about the learning and execution. Students uncomfortable with sharing their ideas are told, 'Don't take this class.'

Slide 19: Application Form

Slide 19 outlines the application process. It asks for student backgrounds, current work experience, and 'what unique talent or expertise' they bring. It requires two business ideas and a justification for why the specific student should be chosen if only one spot were left in the class.

Slide 20: Mentor List

Slide 20 is a placeholder for the Mentor List, which is stated as 'TBD' (To Be Determined) as of July 4th, 2011.

What Works in This Syllabus

Extreme Clarity on Workload: By explicitly stating the 20-hour weekly commitment and the requirement for 10-15 customer interviews per week, the syllabus filters for only the most committed students. · Process Over Outcome: The grading rubric (Slide 3) correctly identifies that in an educational setting, the ability to follow a rigorous validation process is more important than the accidental success of a lucky idea. · Iterative Documentation: Requiring at least three versions of the Business Model Canvas in the final presentation (Slide 12) forces students to visualize their pivots, which is the core of the Lean methodology. · Financial Realism: Defining 'Scalable' vs. 'Buyable' startups (Slide 14) provides students with a clear understanding of the venture capital landscape and what kind of exit they are actually building toward.

What Is Missing

Specific Mentor List: Slide 20 is empty, leaving students without knowledge of the specific industry expertise available to them at the time of the syllabus revision. · Legal Templates: While the syllabus discusses IP (Slide 17), it does not provide or mention templates for founder agreements, which are often a source of friction for teams that continue after the course. · Budget for Physical Prototypes: While web teams are told to spend $20 on SEM (Slide 8), there is no mention of a budget or resource pool for physical product teams to build their prototypes.

What Founders Should Copy

The 'Lessons Learned' Format: Instead of pitching a static vision, founders should present their journey: 'Here was our hypothesis, here is what we did to test it, here is the data we found, and here is how we changed.' · The 10-15 Interview Rule: The requirement for 10-15 face-to-face interviews per week is a gold standard for early-stage validation that most founders fail to meet. · Hypothesis-Driven Development: Every block of the business model should be treated as a testable hypothesis rather than a fact. · Public Accountability: The use of a weekly blog to document progress creates a trail of evidence that is highly attractive to sophisticated investors who value execution over secrecy.