Summary
The Lean B2B is a practical guide to applying lean startup principles specifically to the business-to-business context. Étienne Garbugli wrote it after conducting hundreds of interviews with founders and early employees at B2B startups, and the book reflects what actually works in selling to companies rather than to consumers — a context where the customer, the buyer, and the user are often different people, purchasing decisions involve politics and procurement, and a single contract can represent months of revenue.
The book's central argument is that B2B customer development is fundamentally different from consumer customer development in ways that most lean startup frameworks ignore. B2B sales involve longer cycles, multiple stakeholders, and problems embedded in organizational workflows that are hard to see from the outside. Getting to the truth requires more preparation, more targeted access, and more honest conversation than most founders bring to early discovery. Garbugli is direct about the common failure mode: founders who interview potential customers but ask the wrong questions, validate too early on weak signals, and build before they've confirmed they're solving a problem that someone is actively paying to solve.
The practical core of the book covers how to identify a beachhead market, how to find and access early adopters in B2B contexts, how to run discovery interviews that surface real pain rather than polite interest, and how to move from early signals to the kind of evidence that justifies building. There is particular attention to the concept of the problem-solution fit in B2B: the customer must have a problem they acknowledge, that's causing real pain, and for which they have budget and authority to solve. All three conditions must hold, and most early-stage B2B founders are missing at least one.
The book is brief and direct. It is best read alongside The Mom Test for interview technique and The Lean Startup for broader context. By itself it won't transform a novice into a skilled operator, but it prevents several expensive mistakes that B2B founders commonly make in the first year.
Key takeaways
- 1.
B2B customer development differs from consumer development in critical ways: multiple stakeholders, longer cycles, budget processes, and organizational politics all affect what founders should be testing and when.
- 2.
The early adopter in B2B is not just someone who likes new products — it's someone with a problem they acknowledge, real pain, budget, authority to act, and urgency. All five conditions matter.
- 3.
Problem-solution fit in B2B requires confirming the customer has a problem worth paying to solve before building anything. Most founders validate too early on weak signals.
- 4.
Access is the first problem in B2B customer development. Getting to the right person in the right role requires more preparation and more creative outreach than most founders expect.
- 5.
The buying process and the using process are often separate in B2B. The person who feels the pain is frequently not the person who controls the budget. Understanding who holds what authority is essential before building.
- 6.
A small number of design partners, chosen carefully and engaged deeply, produces better product intelligence than a large number of shallow interviews.
- 7.
Founders should be wary of interest that doesn't convert to willingness to pay, provide access, or make introductions. Polite enthusiasm is not a signal that an opportunity is real.
- 8.
Beachhead market selection in B2B should optimize for density of the problem, not size of the market. A tight segment with high pain is easier to enter than a broad market with diffuse pain.
Discussion questions
Use these on your own, with a book club, or as chat starters in Superbook.
- 1.
Garbugli argues that B2B customer development requires different techniques than consumer customer development. In what specific ways does selling to companies change what you should be testing and how?
- 2.
Think of a B2B product you've evaluated or bought. Who was the user, who was the buyer, and who had budget authority? Were they the same person?
- 3.
His early adopter definition requires acknowledging a problem, real pain, budget, authority, and urgency. Which of those conditions is hardest to confirm, and why?
- 4.
What's the difference between polite interest from a potential customer and a genuine signal that they'd pay for your solution? How would you test the difference?
- 5.
He emphasizes design partners over broad surveys. What are the risks of relying too heavily on a small number of early partners in shaping your product direction?
- 6.
Beachhead market selection should prioritize density of the problem over size of the market. Can you think of a B2B startup that got this wrong and what happened?
- 7.
What questions should you be asking in a B2B discovery interview that most founders forget to ask?
- 8.
Garbugli wrote this in 2014. How has the B2B software landscape changed since then, and which of his principles feel most dated versus most durable?
- 9.
The book assumes you're an early-stage founder doing customer development. How useful are the same principles for a product manager at a larger company evaluating new markets?
- 10.
He argues that most founders validate too early on insufficient evidence. What does sufficient evidence for B2B problem-solution fit actually look like in practice?
- 11.
If you were designing a customer development process for a B2B product in your industry, what would the first five conversations look like, and what specifically would you be trying to learn?
Themes
Frequently asked questions
-
What is The Lean B2B about?
It's a guide to applying lean startup principles specifically to the business-to-business context, with practical advice on finding early adopters, running discovery interviews, and validating that a problem is worth solving before building a product.
-
How is it different from The Lean Startup?
The Lean Startup is a general framework for startups. The Lean B2B adapts those principles specifically to B2B contexts — multiple stakeholders, procurement processes, design partners, and the separation between the person who uses a product and the person who buys it.
-
Is this book still relevant?
Largely yes, though the B2B software landscape has changed since 2014. The core principles about customer development, beachhead market selection, and early adopter criteria remain applicable. Some tactical advice on outreach and tools is dated.
-
Who should read The Lean B2B?
Founders and early-stage product managers building software for businesses, particularly those new to B2B sales cycles and customer development. It's a compact book that prevents several expensive early mistakes.
-
What's the most important idea in the book?
The early adopter definition: a genuine early adopter in B2B has a problem they acknowledge, is experiencing real pain, has budget, has authority to act, and has urgency. Founders who confuse polite interest with all five conditions tend to build products that stall after the first few sales.
