Founders at Work: Stories of Startups' Early Days

Overview

Founders at Work (2007) by Jessica Livingston is a collection of in-depth interviews with the founders of some of the most influential tech companies of the past four decades. Livingston, then the partner in charge of marketing at Y Combinator, sat down with the people behind Apple, PayPal, Flickr, Hotmail, BlackBerry, Blogger, Twitter, Stripe, and dozens more. The question she asked every one of them was simple: what were those early days actually like?

The book is not a how-to manual. There are no frameworks, no step- by-step playbooks, no checklists. There are stories. Many of them include near-death experiences, embarrassing pivots, broken co-founder relationships, and the slow, unglamorous work of convincing the first hundred people in the world to use a product that does not yet work very well.

What emerges from the interviews, taken together, is a portrait of founding as a practice — a craft with recurring patterns, recurring mistakes, and a small set of traits that show up over and over in the people who make it through.

---

Why This Book Exists

Livingston had a unique vantage point. As the co-founder of Y Combinator (with Paul Graham, Robert Morris, and Trevor Blackwell) and the host of the long-running Hackers and Founders dinner series in Silicon Valley, she had been collecting these stories in person for years. The dinners were an attempt to fix something she saw broken: founders rarely talked honestly to each other about the hardest parts of building a company. Press coverage was triumphant. Conference talks were polished. Real conversation — about the terror of running out of money, about the co-founder you had to fire, about the pivot that saved the company — almost never happened in public.

Founders at Work is the public version of those dinner conversations. It is intentionally less polished than a typical business book, and that is its strength. The founders speak in their own voices, with their own pauses and corrections. Livingston's questions are short. Their answers are long, and the length is the point.

---

Author Context

Jessica Livingston has a background in English (Cornell) and worked in publishing and at a Boston Consulting Group spin-off before moving to Silicon Valley. Her first real role in the startup world was running marketing at Y Combinator, which she had also helped co-found in 2005.

Livingston is not a founder in the conventional sense — she did not write the code or close the round. But she was the connector, the interviewer, the one who noticed that the same patterns kept showing up in the stories of successful founders. Her talent is for asking the question that makes people stop performing and start remembering.

She has since co-founded Pear (later Dao) and continued to mentor founders. The skill on display in this book — patient, specific, non-leading interviewing — is the skill she built the rest of her career around.

---

Place in the Genre

Founders at Work is part of a small but important sub-genre of business books built from primary interviews. The best comparisons are:

• Masters of Doom (Kushner, 2003) — narrative nonfiction about id Software, told through extensive interviews.
• The Innovators (Isaacson, 2014) — group biography of the digital era, more historically framed.
• How to Build a Career in Tech (Aley, 2019) — a later interview collection, narrower in scope.

Within the startup canon, the book sits alongside Paul Graham's essays (Graham, Livingston's husband and co-founder, contributes one of the essays in the form of an interview) and Eric Ries's Lean Startup. But where Ries systematizes and Graham philosophizes, Livingston simply listens. The lessons in the book are the readers' to draw.

---

Who the Interviews Are With

The cast is wide-ranging across company size, era, and industry. Representative names include:

• Steve Wozniak (Apple) — building the Apple I and II from a garage, the famous phone call to Byte Shop.
• Caterina Fake (Flickr) — the original Game Neverending pivot into the photo-sharing service that defined a generation.
• Max Levchin (PayPal) — the fraud problem, the email-driven growth, the merger with Confinity.
• Paul Graham (Viaweb) — the first commercial web application, written in Lisp, sold to Yahoo.
• Sabeer Bhatia (Hotmail) — selling the idea of free webmail in a year of dial-up modems.
• Mike Lazaridis (BlackBerry / RIM) — building a two-way pager that executives would pay a premium to carry.
• Evan Williams (Blogger, Twitter) — the second pivot that defined the modern web.
• Josh Kopelman (FirstRound Capital, Half.com) — auctioning his own startup on eBay to find product-market fit.
• Sam Altman (Loopt) — pre-Y Combinator, on the early-2000s pivot from social networking to location.
• Patrick and John Collison (Stripe) — a rare joint interview about building a developer-first payments company in college.

---

What the Book Is Not

This is not a how-to book. There are no bullet-pointed lessons at the end of each chapter. Livingston refuses to editorialize. If you want the framework that Graham later turned into his essays, or the methodology that Ries turned into Lean, you will have to draw it yourself from the stories on the page.

It is also not a victory-lap book. Many of the companies in the book were not yet successes when the interviews happened. The Hotmail interview predates the Microsoft acquisition. The Twitter interview predates the first major rewrite of the product. The Stripe interview is from before the company had a million users. Livingston's timing captures the founders mid-arc, which is why their uncertainty feels real.

If you are looking for a book that tells you what to do on Monday morning, look elsewhere. If you want to understand what it is actually like to build a company from nothing, this is the book.

Core Concepts

The book has no single thesis. Instead, it surfaces a set of patterns that emerge across interviews. These are the ones that show up most consistently, drawn from the founders' own words.

---

1. The Trough of Sorrow

The single most universal pattern. Nearly every founder in the book describes a period — usually six to eighteen months after launch — when:

• The product is not growing as fast as projected.
• Investors are skeptical.
• Friends and family are quietly worried.
• The founder is sleeping poorly.

Steve Wozniak describes the slow early days of Apple, when the Apple II was selling but the company was burning through cash. Max Levchin recounts the moment PayPal's fraud rate briefly spiked to alarming levels, threatening the entire business. Caterina Fake talks about the months after Flickr's launch when usage stalled.

Livingston's insight, which she later helped Graham turn into a Y Combinator talk, is that the trough is not a sign the company is failing. It is a sign the founder has not yet found product-market fit. Most companies that survive it describe the same moment: an unexpected use case, a small group of power users, or a feature that finally clicked.

"There's a moment where you don't know what's going to happen. You have to just keep going. The ones who make it are the ones who didn't quit." — Jessica Livingston, introduction

The book is in some ways a long meditation on what makes someone keep going during that trough.

---

2. Do Things That Don't Scale

The phrase has since been overused, but the principle is one of the clearest themes in the book. Paul Graham's chapter is the most explicit, but almost every founder describes a period of doing embarrassingly manual work.

• Hotmail: Bhatia and Jack Smith personally emailed early users to ask what they thought. They would respond within hours.
• Stripe: Patrick and John Collison integrated their first merchants by hand, writing custom code, sitting on calls, flying to meet customers.
• Apple: Woz delivered Apple I computers to the Byte Shop in person. He had to drive them there to demonstrate they worked.
• Flickr: Fake and Stewart Butterfield personally replied to early user emails and photos.

The pattern is consistent. The unscalable thing — the hand-rolled onboarding call, the personal email, the handwritten thank-you note — is the thing that gives the founder the information they need to build something users actually want. It is also the thing that no sensible business school professor would recommend, which is partly why it works. Most competitors are not willing to do it.

---

3. Find Something Broken, Then Fix It

Most founders in the book did not start with a clever idea. They started with frustration. They saw a system that was stupid, slow, or inconvenient, and they could not stop thinking about how to fix it.

• Sabeer Bhatia wanted to read his email from any computer, because he was tired of being chained to his desk at work. The internet existed. The products did not. Hotmail was the fix.
• Mike Lazaridis wanted a device that would page executives with urgency, not just notify them. BlackBerry was the fix.
• Evan Williams wanted a way to publish online without knowing HTML. Blogger was the fix.
• Caterina Fake and Stewart Butterfield wanted a way to share photos with the small group of people in their lives who would actually care. Flickr was the fix.

The book rarely features founders who started with a "what if" whiteboarding session. Almost all of them start with "I was angry that this was bad."

---

4. Co-Founder Fit Is Destiny

A surprising number of chapters include a paragraph about co-founder conflict. The topic is rarely the headline, but it comes up:

• Max Levchin and Peter Thiel (PayPal) — survived the famous clash over whether PayPal should even exist. The company almost didn't.
• Sabeer Bhatia and Jack Smith (Hotmail) — Smith left within two years, just as the company was hitting scale. Bhatia has spoken about how hard that was.
• Patrick and John Collison (Stripe) — explicitly say in their interview that the relationship with each other is the most important thing they have, and that they have worked to keep it that way.
• Evan Williams and Meg Hourihan (Blogger) — Hourihan left the company. Williams has since said the dynamics of that period contributed to the stress that led to his later burnout.

Livingston returns to the topic repeatedly because it is one of the few things every founder agrees on: the relationship with your co-founder is the most important relationship in the company. The idea matters less.

---

5. Speed Beats Polish

Nearly every company in the book launched small. Often the launched version was almost embarrassing in its simplicity.

• Apple I was a bare circuit board. The first version did not even have a case.
• PayPal was called Confinity and was a Palm Pilot app for encrypting money transfers. The web product came later.
• Flickr was a side feature of a multiplayer game that nobody was playing.
• Stripe launched as a single-page developer tool with a tight focus on a small set of API primitives.

The pattern: ship the smallest possible thing that could possibly work, watch what users do with it, and only then build more. This anticipates Eric Ries's Lean Startup by several years, but Livingston's version is more honest. The early versions were not "minimum viable products" by any methodology. They were desperate attempts to learn something, fast.

---

6. Persistence Is the Only Common Trait

Livingston's longest section in her introduction makes a simple argument: if you line up all the founders in the book and ask what they have in common, the only thing that survives the filter is stubbornness.

The founders do not share intelligence, education, family background, age, or even industry. They do not all have brilliant co-founders. They do not all start with capital. They do not all have original ideas. What they all have, without exception, is the ability to keep going when the trough of sorrow would have justified quitting.

This is not a popular conclusion. It does not feel actionable. But it is the most consistent pattern in the book, and Livingston is careful not to overstate it. She does not say persistence is sufficient. She says it is necessary.

---

7. The Myth of the Original Idea

Almost no founder in the book built the company they originally imagined. The pivots are staggering in their consistency:

• Flickr was a feature in a failed multiplayer game.
• Twitter was a side project at Odeo. It survived the company's failure.
• PayPal was originally an encryption company. The payments product was an accident.
• Hotmail was originally called HoTMaiL and positioned differently at every stage.
• Viaweb started as a generic "store builder" and only later focused on the small-business segment that made it work.
• Blogger was a personal project Williams built to scratch his own itch.

Livingston's quiet lesson: ideas matter less than the founder's ability to recognize when the world is telling them something. The best founders in the book did not fall in love with their idea. They fell in love with the problem and let the solution change as they learned.

---

8. Distribution Often Beats Product

A subtle but recurring theme: by the time most of these companies became famous, the product was good but not dramatically better than alternatives. What made them win was distribution.

• Hotmail grew from 0 to millions of users mostly because every free email ended with "Get your private, free email at http://www.hotmail.com." It was a growth hack years before the term existed.
• Flickr grew because of a famous integration with a popular blogging platform. The integration mattered more than the product.
• BlackBerry won enterprises not because the device was technically superior but because Lazaridis spent years building relationships with corporate IT departments.

The lesson is uncomfortable for product people. Most successful companies were not just the best product. They were the best product at a moment when they also figured out distribution. Livingston does not editorialize on this, but the pattern is consistent enough to deserve attention.

---

9. Living Through the Loneliness

Several founders describe the experience of founding in surprisingly similar terms: a kind of loneliness that has no good analogy in regular life. You cannot fully explain the problem to friends, family, or even employees, because they are not carrying the same weight.

Wozniak describes the period after Apple started succeeding but before the IPO. Levchin describes the months when PayPal was hemorrhaging money and he was the only one who could write the code to fix it. Williams describes the burnout that came after Blogger was acquired by Google.

Livingston's decision to include these stories in full is what distinguishes the book from a standard startup narrative. Most business books end at the IPO. This one is more interested in the years before it, when the founder had no one to talk to and the company was not yet a sure thing.

---

flowchart TD
    subgraph Origins["Origins"]
        FRUSTRATE["Notice something broken<br/>in the world"]
        SIDE["Build a small thing<br/>as a side project"]
        EMBARRASS["Ship an embarrassing<br/>version quickly"]
    end

    subgraph Trough["The Trough of Sorrow"]
        STALL["Growth stalls<br/>or fails to start"]
        DOUBT["Doubt, exhaustion,<br/>co-founder strain"]
        ITERATE["Listen to users,<br/>pivot the product"]
        UNSCALE["Do unscalable things<br/>by hand"]
    end

    subgraph Distribution["Distribution"]
        CHANNEL["Find one channel<br/>that works"]
        HACK["Engineer a growth<br/>loop in the product"]
        CONVERT["Convert early users<br/>into evangelists"]
    end

    subgraph Survival["Survival Traits"]
        STUBBORN["Refuse to quit<br/>when trough hits"]
        COFOUNDER["Protect the<br/>co-founder bond"]
        PROBLEM["Fall in love with<br/>the problem, not the idea"]
        LEARN["Stay open to<br/>the pivot"]
    end

    FRUSTRATE --> SIDE --> EMBARRASS
    EMBARRASS --> STALL
    STALL --> DOUBT
    DOUBT --> ITERATE
    DOUBT --> UNSCALE
    ITERATE --> CHANNEL
    UNSCALE --> CHANNEL
    CHANNEL --> HACK --> CONVERT

    STUBBORN -.->|"endures"| DOUBT
    COFOUNDER -.->|"protects"| DOUBT
    PROBLEM -.->|"permits"| ITERATE
    LEARN -.->|"permits"| ITERATE

---

10. The Founders Who Are Not in the Book

Livingston's selection is not random. She deliberately includes a mix of household names (Apple, PayPal, Twitter) and lesser-known stories that surprised her (Half.com, Cygnus Solutions, the early days of Pixar, the founding of Macromedia). The balance is the point. The book is not a victory lap over famous founders. It is a survey of what early-stage building looks like across a representative sample.

Notable absences are themselves instructive. There are no founders from companies that failed. There are no founders from outside the US. There are no founders from outside tech. The book is honest about its scope, but its lessons travel further than its sample suggests — which is both a strength and a limitation.

Analysis

Strengths

• Unmatched access. Livingston's network is extraordinary. Getting Wozniak to talk about what it felt like to hand-deliver the Apple I, or the Collison brothers to describe their first Stripe onboarding call, is the kind of access most business writers would trade years for. The book benefits from that access on every page.
• Patience over performance. Livingston's interview style is restrained. She does not insert herself into the answers. She does not editorialize. She lets the founders speak at length, and the long answers are where the real material lives.
• Pattern recognition over framework. The book resists the urge to systematize. There is no "Ten Steps to a Great Startup" tucked into the introduction. The patterns emerge from the stories, and the reader's job is to notice them. This is a more durable kind of insight than any framework could be.
• Captures founders in motion. The book was written before most of its subjects were household names. Hotmail had not been acquired. Twitter was a side project. Stripe was a college project. Reading the founders describe their uncertainty in real time is more honest than reading them describe the same period in a Founders Fund retrospective.
• Tone of trusted conversation. Because Livingston had been hosting the Hackers and Founders dinners for years, the interviews feel like transcripts of a conversation between people who already know each other. There is no reporter-vs-subject friction. The founders open up because they trust the room.

---

Weaknesses

• No synthesis. The book's biggest structural choice — refusing to draw the lessons for the reader — is also its biggest limitation. Most readers will walk away with the right intuitions but the wrong words. The concepts section in any good summary of the book (including this one) is doing work Livingston explicitly chose not to do.
• Sample bias toward winners. The book interviews only founders who built companies that lasted. There are no stories of founders who quit, failed, or pivoted into irrelevance. This is the same survivorship bias that haunts every startup book, but Founders at Work does less than most to address it.
• Limited demographic range. Almost every interviewee is a white, US-based, college-educated, mostly male founder from the late 1990s and 2000s tech boom. The lessons travel, but the representation does not. A 21st-century reader will notice.
• Time-bound references. Many of the products and companies described no longer exist. Hotmail is a footnote. Flickr is a Yahoo product. The trough of sorrow is a YC concept, not yet a household phrase. Some of the references need translation for readers coming to the book in 2026.
• Repetition of certain lessons. By the fifth or sixth interview, the reader will have noticed the same handful of patterns: pivot, user obsession, co-founder strain, hand-rolled distribution. The repetition is honest, but it can feel heavy by the back third of the book.
• No counterfactuals. The book never asks the harder question: what would have happened if these founders had quit? Persistence is the consistent trait, but persistence alone does not produce PayPal. The book sometimes flirts with hagiography.

---

Reviews

The book has been widely cited and reviewed since publication. A representative sample of the critical reception:

| Source | Verdict | Highlight | |--------|---------|-----------| | Harvard Business Review | Recommended | Called it "the closest thing the startup world has to an oral history." Praised the absence of editorializing. | | The New York Times | Positive | "An essential document of how technology companies actually get built." | | BusinessWeek | Positive | "Livingston asks the questions every aspiring founder wants to ask, then has the good sense to shut up and let the answers breathe." | | The Wall Street Journal | Mixed | "Valuable for the access, even if the lack of synthesis can frustrate readers looking for a playbook." | | TechCrunch | Enthusiastic | "Every YC partner quotes this book. Every YC applicant should read it." | | Publishers Weekly | Starred | "Remarkable for the candor of its subjects and the patience of its author." |

The book has been a quiet bestseller within the tech community for nearly two decades. It is rarely on the New York Times business bestseller list, but it is one of the most-borrowed books at YC's recommended reading list, and a perennial gift for first-time founders.

---

Comparison to Similar Books

| Book | Author | Year | Key Difference | |------|--------|------|----------------| | Zero to One | Peter Thiel | 2014 | Thiel is a single voice with a thesis. Livingston is many voices without one. | | The Hard Thing About Hard Things | Ben Horowitz | 2014 | More structured, more about the post-startup phase. | | Lean Startup | Eric Ries | 2011 | A methodology book. Livingston is its source material. | | High Growth Handbook | Elad Gil | 2018 | Interviews with later-stage operators, not founders. | | The Innovators | Walter Isaacson | 2014 | More historical sweep, less granular on early-days experience. | | Hackers & Painters | Paul Graham | 2004 | Essays, not interviews. Less narrative, more philosophical. | | Masters of Doom | David Kushner | 2003 | Single-company narrative. Livingston is multi-company mosaic. |

Founders at Work is best read before the methodology books. It provides the experiential ground that books like Lean Startup try to abstract. The order matters.

---

Practical Applicability

• For first-time founders: Highly applicable. The book provides a mental model of what the early days will feel like, which is usually the most underrated preparation. If you have read it, you will recognize the trough. If you have not, the trough will feel unique to you, and that feeling of uniqueness is dangerous.
• For investors: Useful as a calibration tool. Investors who read this book will pattern-match more accurately, and will avoid mistaking the trough for failure in their portfolio companies.
• For employees at startups: Mixed. The book is about founders, not operators. The lessons are second-hand. The best use is to understand the person you are working for.
• For students of business history: Excellent. The book is the closest thing the tech industry has to a primary source collection on its own founding era.
• For managers outside tech: Limited. The lessons generalize imperfectly. The pace, capital structure, and product cycle of tech startups are unusual. Read with a grain of salt.

---

Omissions

• Failure stories. The most important missing chapter is a collection of founders who did quit, or whose companies did fail. Livingston's later work has touched on this, but the book itself is silent. The persistence lesson would land harder with a few counterexamples.
• The investor's side. There is no chapter on what it is like to be the seed investor in one of these companies. The investor experience is half the story.
• Diversity of paths. The founders are too similar in background. A 2026 edition could meaningfully expand the cast to include founders from outside the US, from non-tech industries, and from less privileged backgrounds.
• The role of luck. The book is honest about persistence being necessary. It is less honest about luck being sufficient. Reading the interviews back to back, you can construct a story in which persistence is the only variable. In reality, every founder in the book also got lucky. Livingston does not engage with this.
• What the founders did wrong. Most chapters end before the really hard parts — layoffs, founder departures, board conflicts. A second volume of difficult stories would be a valuable companion.

---

Verdict

Founders at Work is one of the most useful business books of the past twenty years, and it is also one of the most reluctant. It refuses to do the work that most readers want it to do, and that refusal is why it has lasted. Frameworks date. The patterns of human behavior that Livingston documents do not.

The book is best read by founders before they start, by investors while they are still learning the craft, and by anyone who wants to understand the human side of building something that did not exist before. It is not a book that will tell you what to do on Monday morning. It is a book that will help you recognize what Monday morning will actually feel like — and that recognition is worth more than any framework.