The bedrock of success

We live in an age where the barrier to entry for digital products has effectively vanished. Fifteen years ago, building a global software platform required a massive investment in servers, a heavy sales force, and complex distribution channels. Today, as Sam Altman (CEO of OpenAI, former President of Y Combinator) and Reid Hoffman (co-founder of LinkedIn) point out, anyone with a laptop can launch an app.

This ease of entry has created a crowded market. For every successful product, there are thousands of alternatives competing for the same user. In this environment, survival is not about who has the most features — it is about who delivers the most customer value.

This lesson covers three things: how to measure if you have made something people actually want, why retention is the only metric that matters in the early stages, and what makes a product "remarkable" enough to grow on its own.

Y Combinator's motto is simple: "Make something people want." But how do you know if you have done that?

Many founders look at "Total Registered Users" or "Daily Active Users (DAU)." These are often vanity metrics. They go up as long as you spend money on marketing, but they hide the truth about whether users are actually deriving value.

A cohort is a group of people who started using your product during the same time period — for example, all users who signed up in January. Instead of looking at your entire user base as one mass, you track these specific groups over time.

When you plot the percentage of users from a cohort who return to the product over weeks or months, you get a retention curve. Its shape tells you where you stand:

If your curve does not flatten, you are on a treadmill:

• Every month you must acquire more users just to replace the ones who left
• The cost of acquisition (CAC) keeps rising as you exhaust the easiest channels
• Eventually, the cost of replacing users exceeds the value you can extract — and the company collapses

You might ask: "Why not just fix the onboarding to make the curve higher?" Onboarding helps, but it cannot fix a product that lacks a "core event." If users do not see value after 30 days, the product usually does not solve a recurring problem.

Once you have identified that a segment of users is staying — a flat curve — the next question is: how do you make that behavior habitual?

Nir Eyal, author of Hooked, defines a habit as a behavior done with little or no conscious thought.

A Hook is an experience that connects a user's problem to your solution with enough frequency to form a lasting mental association.

The Hook is a loop with four stages: a trigger (the itch that starts the behavior), an action (the simplest thing the user can do), a variable reward (satisfaction plus an element of surprise), and an investment (something the user puts back into the product that makes leaving harder).

We will break down each stage in detail in Lesson 3. For now, the key insight is this: retention proves that users can stay. The Hook Model explains how to make staying automatic.

A habit-forming product does not need to remind users to come back. But even a habit-forming product needs to be discovered. The next question: how do you stand out in a crowded market?

If your product is just "good," it is invisible. In the Industrial Age, you could win by being "average" and buying a lot of TV ads. In the Digital Age, advertising is an "interruption" that people pay to avoid.

Seth Godin's concept of the Purple Cow suggests that you must build something "remarkable" — literally, something worth making a remark about.

A common mistake is trying to appeal to everyone. This leads to a generic product. Instead, identify the people who are most desperate for your solution.

"Don't find customers for your products; find products for your customers."

• Identify the "otaku" — the obsessed. If you build a tool for professional photographers that is so good they tell their peers, you win. If you build a camera app for "everyone," you get lost in the App Store.

A remarkable product attracts traction. But traction without alignment creates a new problem: every team starts pulling in a different direction, each optimizing for their own definition of "success."

As a product starts to gain traction, the organization often enters a phase of "chaos":

• Marketing is chasing any engagement
• Sales is chasing any revenue
• Engineering is building whatever feature the loudest customer asked for

On the surface, everyone is busy. Underneath, the teams are pulling in different directions. Each department has its own definition of "winning" — and those definitions often contradict each other.

The solution is a North Star Metric — a single number that captures the core value your product delivers to customers. It aligns every team around a shared definition of success and predicts future revenue before the financial reports catch up.

How to find the right metric, how to break it down into actionable inputs, and how to avoid the most common traps — that is the subject of the next lesson.

Ronny Kohavi (former VP at Microsoft, Chief Scientist at Airbnb) puts it directly: in mature products like Bing or Google, 80% of ideas fail to move the target metric. Even in early-stage startups, the failure rate is high.

This means that without controlled experiments, you are likely shipping code that is flat or harmful 70-80% of the time. Building a trustworthy experimentation system — with the right metrics, the right sample sizes, and the discipline not to peek at results — is the subject of Lesson 4.

Before you can experiment at scale, you need to reach scale. The next section covers what happens when you are ready to grow — fast.

If you have product-market fit, a habit-forming hook, and a scientific way to improve — you are ready for Blitzscaling: the practice of prioritizing speed over efficiency to win a "winner-take-most" market.

Reid Hoffman describes five stages of organizational growth — from Family (1–9 people, doing everything yourself) to Nation (10,000+, managing ecosystems). At each stage, the founder's role changes completely. What made you successful in the previous stage will not work in the next.

We will explore each stage in detail in Lesson 5 — along with the viral loops that fuel hypergrowth and the critical transitions founders must survive.

Before you can scale, you must understand what success looks like at the individual level. That means doing things that do not scale.

Paul Graham (YC) famously advised: "Do things that don't scale." Before you can automate growth, you must understand the manual work required to satisfy a customer.

In the early days, the founders of Airbnb realized that listings in New York were failing because the photos were terrible. They didn't build a "Photo Enhancement Tool." Instead, they rented a camera, flew to New York, and took the photos themselves.

• Result: bookings doubled
• Learning: this manual effort taught them exactly what "quality" looked like, which they later scaled through a professional photographer network

Before you can build systems, you need to understand what success looks like at the individual level. The template comes after the truth.

Growth is not a single "hack." It is a reinforcing system:

• Retention proves you solved a problem
• Habits ensure users come back without you paying for them
• North Star Metrics keep your team aligned
• Blitzscaling allows you to capture the market before competitors do

In the next lesson, we will go deep into the North Star Framework — how to build a "constellation of metrics" that allows every squad in your company to see how their daily work impacts the overall vision.