Lean B2B: Build Products Businesses Want

Selling to businesses is a different game than selling to people. A consumer buys because they want the thing. A business buys because of return on investment, and that changes everything around the sale. There is a relationship to maintain, there is usually more than one person involved in saying yes, and the decision has to survive a process rather than a moment of interest. Understanding that the buyer is an organization and not a person is the foundation the rest of the book is built on.

The core idea of Lean B2B is to start with the people and the market before you start with the product. If you begin with a solution you already like, you end up looking for a problem to justify it, and you carry a stack of false assumptions into everything that follows. Starting with the market makes it much less likely that you invent a problem that doesn't exist. This should be applied at the very beginning of an idea, before any real building happens.

Companies buy for three main reasons: to increase revenue, to decrease costs, or to increase customer satisfaction. If what you're building doesn't clearly land in one of those three, it's going to be hard to explain why anyone should pay for it. This is a useful filter to run an idea through early, because a product can be genuinely interesting and still not connect to any of the three.

The money map is a diagram of what a business is currently spending money on. Laying that out shows you where the real problems are, because expense is evidence that something is painful enough to already be getting paid for. It also tells you whether the problem you want to solve has a budget attached to it. This should be applied while you're evaluating which problem to go after, not after you've already picked one.

Early adopters are essential to whether the business survives past the first few customers, so it matters which early adopters you get. The book's point is to look for clout: people with influence and real connections in their space. A customer who can vouch for you to the rest of the industry is worth more than a quiet one, because their willingness to brag about the product is what gets you the next several conversations.

Credibility is a real asset in B2B and you should use whatever you have. If you're already an expert in the space, you start with it. If you aren't, lean on your team, or bring on someone who does have the expertise. Getting a meeting with someone whose time is genuinely expensive is much easier when there's a reason for them to take you seriously, and borrowed credibility counts.

The author's development process runs in four stages: discovery, drilldown, exploration, and confirmation. First you find the problem. Then you drill down into how the problem actually affects the company today. Then you explore possible solutions. Then you confirm that the solution is valuable enough that someone will trade money for it. The order matters, because each step is only worth doing if the one before it held up.

Just like in The Mom Test, you don't learn anything about a customer while you're trying to sell to them. The moment you start pitching, they switch into feedback and support mode, where they stop thinking about their own situation and start thinking about your product and what could be added to it. Their answers stop being about their life and start being about your roadmap. Keep the conversation on their real behavior instead.

The book lays out an interview code of conduct that I found genuinely useful. Have a plan, because a script is what makes it possible to compare one interview against another instead of collecting a pile of unrelated conversations. Follow emotion: whenever you hear it in someone's voice, that's the thread to pull. Encourage complaints, because people are far more specific about what frustrates them than about what they like. And watch for two kinds of bias: response bias, where the interviewee tells you what they think you want to hear, and interviewer bias, where you frame a question in a way that fishes for a particular answer.

A rough interview script goes: greetings, where you introduce yourself again; qualification, where you confirm this person is actually a good fit before spending the conversation on them; open-ended questions, where a lot of the best material comes from letting them wander down side tangents; and closing. The goal at closing is to get a follow-up first, and then to expand your network by asking the prospect for five other people who probably deal with the same problem.

Ask questions in levels rather than all at once. The book's example is looking into social media recruitment. You start broad with something like 'tell me how you deal with recruitment.' Then you go a level deeper with the who, what, where, when, and with questions. Then you go one level deeper again with 'what do you mean by that' or 'can you explain a little further.' Each level gets you past a layer of summary and closer to what actually happens.

After you've interviewed enough prospects, you have data on what hurts, where it hurts, and what kind of budget exists, and the next job is deciding which problem to attack. Frequency, meaning how often a problem comes up across interviews, is mostly useful for estimating market size; it tells you nothing about how deep the problem runs, and with a small sample it may not reflect real market trends anyway. Intensity is a better signal: if someone keeps circling back to the same problem and gets worked up about it, that problem is real. But budget is the best signal of all. You can find an intense, widespread pain point and still be dead in the water if nobody has money allocated to solving it.

Before you show anyone your MVP, ask them what they're picturing. This is something I want to actually use, because once you put the product in front of someone their brain switches over to reacting to what you built instead of telling you what they needed. Asking first gives you a benchmark: you find out what they expected, which features they assumed would be there, and how they'd rank them. This is Kano analysis, which sorts features into the ones that are simply expected and get you nothing for having them, the ones that genuinely delight people, and the ones nobody cares about either way. Missing a must-have kills you, and adding a delighter nobody asked for is where a lot of build time goes to die.

Pricing inside an organization is stranger than I expected. Companies have signature thresholds, and crossing one changes who has to be involved. A manager might be able to sign off on a $1,000 purchase on their own, but at $1,001 it suddenly needs a higher-level signature. The number barely moved and the deal is now a completely different deal, with new people reviewing it, new questions, and a much longer timeline. It's worth knowing where those thresholds sit for your customer, because pricing just under one can be the difference between closing in a week and closing in a quarter.

Pilots are a great way to prove the value your solution actually provides, but the contract matters. Put an agreement in writing that they pay if the metrics are hit. Otherwise you've just committed to a free trial with extra steps, and there's nothing forcing a decision at the end of it. Defining the success metric up front also forces the customer to say out loud what a win would look like, which is useful on its own.

Long sales cycles are brutal for young entrepreneurs, and this was the part that stuck with me most. A typical B2B sale takes 8 to 10 contacts, and if you're selling to C-level executives it can take 12 to 14. That's not 12 to 14 days, that's 12 to 14 touches, each one with its own delay waiting on a reply. If you're early and running on your own money, the cycle can outlast your runway before you ever find out whether the product was any good. It makes a real argument for starting with smaller companies where fewer people have to say yes.

Be where the customer already is. The book gives a case study on Spotfire, a data visualization startup that moved its headquarters into the same building as a restaurant that executives from Exxon Mobil, BP, and Shell regularly went to. That proximity turned into constant informal interaction, which turned into deals, and the company was eventually acquired for $195 million. It's an extreme version of the idea, but the underlying point is that access is a strategy. Putting yourself physically or socially in the path of the people you're trying to sell to beats trying to reach them cold from the outside.