Hey Quinn, I’m glad to have a chance to help you in a small way after you and Beyang did me a _huge_ favor from back in your SOMA apartment days.
I think Andy’s teaching style, when distilled, tends to come across as quite trite and simplistic. In class and the following lunches, that manifests as more nuanced as students challenge his theses for appearing that way. To give you a sense, try reading this Medium summary of the class: https://medium.com/parsa-vc/7-lessons-from-andy-rachleff-on-...
It doesn’t come across as particularly profound.
The best notes from the class that I’ve found are actually from Andy himself. He’s posted what I can only imagine are proto-class notes on the Wealthfront blog which over the years have come to encompass many of the main points from his coursework. Here are some selections that I recall echoing points he made in class:
I think what is enlightening for the class is Andy’s framework for evaluating and structuring a startup. If I had to distill it from memory, it is something like:
Technology companies are special. Unlike market driven companies, technologists can often invent something new and be confident that a market exists that can take advantage of this innovation. After hearing constant denigration of the “build it and they will come approach”, one may find this unintuitive. However, finding a customer who can’t live without your technology is possible and can be done in a structured manner. Once you do find such a customer, it is also possible to grow use cases until you have not just an essential business but also a large one. Success to Andy is $100m in ARR.
The first step in this process is identifying a compelling technological opportunity. How does one go about doing this? In particular, do you find good ideas or do good ideas come to you? Andy believes that the right answer here is expertise in a technology and authenticity to a market/use case.
Once you have identified a technological opportunity, hypothesize who may find it useful. Go lean startup and build an MVP to see if they do. Remember that product market fit means that a customer will be dying to use a subpar product. MVP, at the same time, means different things in different circumstances: Qualcomm’s MVP might require a lot more investment than Airbnb’s. As customers use your product, improve what’s working; don’t focus on fixing what’s broken. If your initial hypothesis fails, try to think of new customers. This is called a pivot (as opposed to when you change the underlying technology, which is more of a restart). In this phase, keep cash burn low so you can test as many value hypotheses as possible. Don’t outsource engineering, it is better to optimize rate of iteration than cost per.
Once you have found a customer, you enter the growth phase. Here it is all about analyzing the types of customers in the market (large incumbents, other startups, etc.) and sequencing how you sell to them. You have to have the right sales org composition for each step of the sequence. In this phase, you need to prove as quickly as possible that there is a path to growth with positive economics. This part of the course focused a lot on types of businesses markets, ways to structure partnerships, and how to understand growth models. The Facebook network effects case is important. In this growth phase, you may need to fire your initial adopters.
This is all from memory and I will try to build on the comment as I have a chance to access my notes. Hope that’s an interesting start...
(And hi, Ben!! Your awesome holiday card is still up on our fridge. :)