The series 'Silicon Valley' is not just an entertaining comedy about startups and programmers. It contains a wealth of useful information for startup development, presented in a simple and accessible language. I always recommend that all aspiring entrepreneurs watch this series. For those who don't think it's necessary to waste time on series, I've prepared a brief selection of the most useful episodes that are definitely worth watching. After reading this article, you might want to check out this show.
The series follows the fate of Richard Hendricks β an American programmer who invented a new, revolutionary data compression algorithm and, along with his friends, decided to start a company based on his invention. His friends had no business experience prior to this, so they face all sorts of obstacles and challenges.
Episode 1 β 17:40 β 18:40
Richard doesn't understand the potential of his invention, but more experienced players Gavin Belson (head of Hooli) and Peter Gregory (investor) see it clearly and offer Richard two possible paths. Gavin offers to buy Richard's web service along with the rights to the code and algorithm, while Peter proposes an investment in Richard's future company.
This episode showcases one way to determine investment conditions. One of the challenging aspects of early-stage investing is valuing a startup. Gavin's offer to purchase provides Peter with the simplest method of appraisal. If there's a buyer for the entire startup, it becomes clear how much the investor's share will be worth. The dialogue is also interesting because as Gavin's offer increases, Peter reduces both the investment amount and his share, staying within a comfortable range for the investor's investment.
Episode 2 β 5:30 β 9:50
Richard meets with Peter Gregory to discuss the project and investments. The first question Peter is interested in is the project team's composition and who holds what shares. Next, Peter inquires about the business plan, market entry strategy, budget, and other documents that reflect the future business vision. He explains that as an investor, he is interested in the company, not its product. The investor buys a stake in the company. For the investor, the product is the company, not its output. The investor makes a profit primarily when selling his stake in the company after its value increases. This principle applies to both venture capital investments and the ordinary purchase of shares in a public company or a stake in an LLC. Peter Gregory also expresses the idea, "I pay $200,000 for 5%, while you gave someone 10% for what?" In other words, it is expected that the person receiving 10% should bring at least $400,000 worth of value.
Episode 2 β 12:30 β 16:40
Richard and Jared interview Richard's friends to determine their skills and roles in the future company, as well as the value they can bring. The idea is raised that simply being friends or fun guys does not merit getting a stake in the company. Friendship is one thing, but shares in the company should reflect the founders' usefulness for business development and their contributions to the collective effort.
Episode 3 β 0:10 β 1:10
As it turned out at the end of episode 2, Gavin Belson (the head of Hooli) whom Richard turned down for a deal, has assembled a team for reverse engineering Richard's algorithm based on the existing site and fragments of frontend code. Meanwhile, Gavin launched video ads announcing his software platform Nucleus for data compression. Richard's friends discuss why he is doing this when he has nothing yet. Dinesh, a programmer from Richard's team, remarks, "The one who gets out first wins, even with lower quality." He is both right and wrong at the same time.
It seems that the first person to enter the market with a fundamentally new product can capture it without competitive struggle. Moreover, the product may even become a household name β like Xerox and Polaroid.
However, when introducing a fundamentally new product, there is usually no clearly established need, and itβs necessary to explain to people how good and convenient the new product is, and how it improves the lives of consumers. This is exactly the direction Gavin Belson took with his advertisement. Moreover, the lack of direct competitors does not mean it will be easy. Consumers who do have a need have already found some way to satisfy it and are accustomed to the existing state of affairs. You will still need to explain why your product is better. When tractors were invented, people had been plowing with bulls and horses for thousands of years. Therefore, the transition to mechanization in agriculture took decades β there was a familiar alternative with its own merits.
Entering a market that already has pioneers gives a startup a huge advantage β it can study the shortcomings of existing competitors, the needs of current users, and offer them a better solution tailored to the specific tasks of a certain segment of clients. A startup cannot afford to spread itself too thin across products for everyone. Startups need to focus on a small target audience with a clearly defined need for their launch.
Episode 3 β 1:35 β 3:00
Peter Gregory (investor) wrote a check in the name of Pied Piper Inc, not personally to Richard, and in order to deposit the funds, the company needs to be registered. This was revealed at the end of episode 2. Now Richard faces a problem β there is already a company in California with that name, and he needs to either negotiate a buyout of the name or change the name and ask Peter to rewrite the check (in real life, there are more options, but this is a work of fiction). Richard decides to meet with the owner of Pied Piper Inc to negotiate a buyout of the name, if possible. This leads to several comedic situations.
This episode teaches us a lesson β before getting attached to the name of a future company or product, one should check its legality (I will share a funny and sad story from Russian practice in the comments) and conflicts with existing brands and trademarks.
Episode 4 β 1:20 β 2:30
Richard visits the lawyer (Ron) to sign the charter documents as the head of the new company Pied Piper Inc. (literally 'colorful piper'; in the show's dubbing it is referred to as 'rat catcher' or 'spotted piper').
While talking to Richard, Ron accidentally mentions that 'rat catcher' is yet another data compression project (and there are either 6 or 8 of them) in the portfolio of investor Peter Gregory.
When Richard asks why fund so many projects, Ron replies, 'Turtles give birth to a ton of offspring because most of them die before reaching the water. Peter wants his money to reach...'. Then Ron adds, 'Successful businesses need both halves of the brain.' During the conversation, Richard realizes he has no clear vision of the future product concept. He came up with an algorithm that provides advantages, which can be the basis for technology, but what will the product of the company be? Clearly, no one has even started thinking about monetization. This situation is quite typical, as startups often have a strong technical aspect of a solution but lack a clear understanding of who needs it and how much it should be sold for.
Episode 5 β 18:30 β 21:00
Jared (who is actually Donald) suggests starting to work with SCRUM to enhance team efficiency. A personal pet project can be developed without any methodology or task tracking, but when a team begins working on a project, success cannot be achieved without effective teamwork tools. The use of SCRUM is briefly shown, along with the emerging competition among team members over who works faster, closes more tasks, and generally who is cooler. Formalizing tasks provided a means to measure team members' effectiveness.
Episode 6 β 17:30 β 21:00
The "Rat Catcher" team is registered as a participant in the startup battle and is struggling to complete their cloud storage platform. Individual modules for processing files in different formats are ready, but the cloud architecture is missing, as no one on the team has the necessary skills. Investor Peter Gregory suggested using an external expert to develop the code for the missing components of the system. The expert, nicknamed "The Cutter," turned out to be a very young individual and demonstrated high skill in the tasks assigned to him. The Cutter works for a fixed fee for 2 days. Since he managed to complete his work ahead of the agreed deadline, Richard agreed to give him more tasks from another area, as it wouldn't increase the cost of services. However, since The Cutter worked almost around the clock and under "substances," eventually a glitch occurred in his brain, and he ruined many of the already completed modules. The situation is comical and perhaps not very realistic, but it gives us the following conclusions:
- one should not be greedy and trust temporary employees with more than what was agreed upon and in areas they truly understand.
- one should not grant employees more access and authority than necessary to perform their tasks, especially to temporary employees.
Additionally, this episode seems to illustrate the fragility of software systems and warns against risky changes just before major events. Itβs better to demonstrate less functionality that is reliable and tested than to aim for more with a high risk of failure and embarrassment.
Episode 7 β 23:30 β 24:10
The "Rat Catcher" team is heading to the TechCrunch Disrupt startup battle, where they encounter several comical personal situations. In this episode, a pitch for another project β Human Heater β is shown. The judges ask questions and provide comments β "this is unsafe, no one will buy this." The presenter starts to argue with the judges and offers a justification for his point β "I've been working on this for 15 years."
From this episode, we can derive at least 2 recommendations:
- when preparing for a public presentation, itβs important to do practice runs in front of people unfamiliar with the project, to hear questions and objections in order to prepare for them;
- The response to objections must be convincing, the arguments should be factual, and the manner of responding should be polite and respectful.
Episode 8 β 4:20 β 7:00
Jared tells the 'Rat Catcher' team about the pivot β a change in the business model or product. His subsequent behavior is comical and illustrates how not to do it. Essentially, he is trying to conduct problematic interviews, but he does it all wrong. This is the first episode in the series where someone from the 'Rat Catcher' team attempts to communicate with potential users.
In the following seasons, there are more interesting episodes on the topic of communication with clients, and the most important one, in my opinion, is in season 3, episode 9. I initially planned to cover only the episodes from season 1 in this article, but I will mention this episode from season 3 because, in my view, it is the most instructive episode of the entire series.
Season 3 β Episode 9 β 5:30 β 14:00
The cloud platform 'Rat Catcher' has launched, there are mobile applications, and more than 500,000 users have registered, but the number of users constantly utilizing the platform does not exceed 20,000. Richard confesses this to Monica β the assistant to the head of the investment fund. Monica decides to look into the problem and organizes focus groups to study users' reactions to the product. Since the product is supposedly for everyone and doesn't require special knowledge, the focus groups include people from various professions (not from IT). Richard is invited to observe the discussion of his company's product by the focus group of potential users.
It turns out that users are 'completely confused' and 'blown away', 'feeling stupid'. Essentially, they just don't understand what is happening. Richard claims that the group may have been poorly selected, but he is informed that this is already the 5th group and it has the least hostile reaction.
It was revealed that earlier the platform was shown and tested by IT specialists, while the target audience for the product is 'ordinary people', who had not been shown the platform before and whose opinions were not solicited.
This episode illustrates a very typical mistake made by startup founders: gathering feedback on their idea and product from the wrong target audience for which the product is intended. As a result, the product turns out well and receives positive reviews, but not from the people who should be buying it. Consequently, the product exists and is good, developed with user feedback in mind, but planned sales will be nonexistent, the actual metrics will be entirely different, and the economics will likely not add up.
Source: habr.com
