Using the Business Model Navigator in Practice
The Business Model Navigator by Osterwalder and Pigneur is essentially a catalog of 55 business model patterns you can mix and match when redesigning how a company makes money. Most people treat it like a reference book they pull off the shelf occasionally. That is a waste. The real value comes from treating it as a puzzle set. You take your current model apart, lay out the pieces, and then experiment by swapping in patterns from the book until something actually fits. I used this method when a client of mine was running a mid-market SaaS company that had plateaued at roughly eight million dollars in annual recurring revenue. Their model was pure subscription with no upsell path and zero cross-sell. We pulled their canvas, identified that they were basically a one-trick vendor, and started walking through the pattern catalog looking for adjacent plays. We landed on a usage-based tier combined with a marketplace add-on. Not ground-breaking, but it pushed them into a completely different growth phase within eighteen months. The actual process works like this. First, map your current business model on a standard canvas or a whiteboard. Get the five building blocks down: customer segments, value propositions, channels, customer relationships, revenue streams, key resources, key activities, key partnerships, and cost structure. Do not skip any section. People always skip the cost part and then wonder why their revenue projections look like fantasy.
Once you have that, go through each of the 55 patterns in the book. Read the description. Look at the visual example they give. Note which ones feel even remotely applicable to your situation. You do not need to adopt them all. In my experience, three to five patterns will actually resonate with what you are working with. The rest are noise. The next step is what most people mess up. You combine patterns deliberately. Pick one primary model that your business already runs on and then layer a secondary pattern on top of it. For example, a subscription model paired with an advertising model. Or a freemium approach layered with a brokerage structure. The combinations are where the interesting territory lives. The individual patterns themselves are mostly obvious once you read them. There is a specific edge case that tripped me up for about two weeks on a project. I was working with a logistics company that wanted to apply the "long tail" pattern from the navigator. The problem was that their product range was already narrow. They moved three SKUs across twelve regional warehouses. Applying a long tail strategy made zero sense here because there was no tail to speak of. What I ended up doing instead was mapping their operations to the "modular business model" pattern, which broke their service into interchangeable components that could be recombined per client. It was a cleaner fit and actually implementable. The long tail entry in the book did not account for low SKU environments, which is a gap in the material.
Another thing the book does not emphasize enough is the time dimension. Business models are not static diagrams. They evolve. A pattern that works at fifty employees does not necessarily work at five hundred. I learned this the hard way with a client who licensed a platform model successfully at scale but then tried to run the same structure when they were still a twenty person startup. The governance overhead alone would have killed them. Sometimes the best answer is to deliberately pick a simpler, more constrained model and grow into a more complex one later. You should also be aware of the limitations. The navigator categorizes models in a way that forces them into neat boxes. Real companies rarely fit neatly into any single pattern. A company can be subscription on one product line, transactional on another, and franchised in yet another geography. The book underplays this kind of hybrid reality. I usually recommend pairing the navigator with a revenue architecture framework so you are not pretending your business operates from a single model. If you want to get the actual book, it is available on Amazon and through most major book retailers. There is also a companion website with some of the canvas templates and pattern illustrations. The patterns themselves are also referenced in Osterwalder's earlier work, Business Model Generation, so if you already own that, you may find some overlap.
Get the Full Details
Here is a quick rundown of the patterns that tend to show up most often in practice when I use this method. Subscription models remain the most common starting point, especially in software. Franchise models apply well to service businesses that have a replicable operating system. Platform or marketplace models work when you have two distinct customer groups that create value for each other. Razor and blade models are still relevant in hardware and consumable goods. Freemium models dominate consumer applications but are harder to pull off in enterprise contexts. Pay-per-use models fit industries where usage varies dramatically between customers. Brokerage models are straightforward when matching buyers and sellers is the core function. When you are evaluating which patterns to combine, look at your existing customer pain points first. A pattern that ignores the actual problem your customers are paying to solve is just a gimmick. I once saw a company try to apply a bundling model to a service they already sold individually. The bundling created confusion in the sales cycle, not revenue. They spent three months untangling it. The navigator is not a replacement for customer interviews or market research. It is a tool for structured thinking about revenue and value creation. Use it alongside actual data from your market. Run small experiments before committing to a full model shift. A pilot with a single customer segment can tell you in a few weeks whether a new pattern will work or whether you are chasing a trend.
I do not recommend using this book if your goal is simply to copy a competitor's model. The patterns are generic by design. The advantage comes from adapting them to your specific constraints and capabilities. A pattern that generated forty percent margin for another company in a different industry might destroy your unit economics. Always run the numbers before you restructure anything. The process is iterative. Map. Select patterns. Combine. Test. Iterate. Repeat. Most teams I work with go through at least two or three rounds before landing on something stable. The first round is usually too optimistic. The second round gets realistic. The third round is where the actual strategy emerges.
