← Back to articles 2026-04-30

From Business Model Canvas to product: structure an idea before coding

6 min read

When I launched my first project, I spent three weeks trying to structure my business model. Paid apps, A3-printed canvases, a whiteboard photographed before every meeting. In the end, a simple tool — the Business Model Canvas — unlocked everything. And it sits exactly where the BMAD method places it: the Business phase, before any architecture.

Why a canvas before code

Software almost never fails for technical reasons. It fails because we coded before understanding for whom, to solve what, and how it makes money. The Business Model Canvas forces those answers onto a single page, before investing a euro of development.

Osterwalder's 9 blocks

The canvas breaks a model into nine interconnected blocks:

Customer segments — for whom are we creating value?
Value proposition — what problem do we solve, better than others?
Channels — how do we reach and deliver to those customers?
Customer relationships — acquisition, retention, support.
Revenue streams — subscription, transaction, license, service.
Key resources — human, technical, financial.
Key activities — what we must excel at.
Key partners — who does the rest for us.
Cost structure — what all of this actually costs.

The exercise only has value if the blocks are coherent with one another: a premium value proposition with a low-cost channel is a model that contradicts itself.

From canvas to control panel

I reworked this canvas into a complete tool — a formula-linked file where filling the model automatically recalculates the rest:

The visual canvas with the 9 blocks.
A viability score across 9 dimensions, with a radar chart.
5-year financial projections — net result, margins, SaaS metrics (MRR, churn, LTV).
A competitive analysis with a SWOT matrix.
An action plan with status tracking and KPIs.

The idea: someone starting in Kinshasa, Lyon or Montreal can lay out their model tomorrow morning, with nothing to install.

The link to architecture

A good canvas produces actionable technical constraints. A subscription revenue stream implies recurring billing and subscription-state management. An international segment requires multi-currency and localization. A "response time" key activity becomes an architecture goal (cache, CDN). The business model is not separate from the technology: it drives it.

Conclusion

The Business Model Canvas does not replace execution, but it prevents building the wrong thing, perfectly. It is one hour of honesty before months of development. Got an idea to put on paper before coding it? Let's talk — that is exactly where I start every project.