From BMC to pitch — QcES journey notes (Spring 2024)

Full article in French — same slug; you can also switch to FR in the header.

At a glance

• The Business Model Canvas (BMC) describes how an organization creates, delivers, and captures value; it answers three questions: desirability, feasibility, and viability.
• You usually start with customer segments and value proposition, then iterate—the model evolves with the market.
• Segmentation makes the market concrete (B2B vs B2C, crisp criteria) instead of vague labels (“doctors”, “parents”).
• Interviews are for discovery: the goal is to learn, not to sell; connect, don’t convince—and stay attached to the problem, not your first idea of the solution.
• Structured feedback (strengths + one growth angle) and a short spoken pitch (no slides) clarify the idea early.
• A product roadmap is a strategic view over time, not a detailed project plan; it aligns vision, audience, horizon, metrics, and resources.
• PoC, prototype, and MVP play different roles: technology check, user interaction learning, then a first market version you can stress-test with real users or buyers.
• Market and value proposition: account for external forces (macro, industry, trends) and express value as offer + customer benefit.
• A solid pitch often follows Hook → Believe → Join: lead with the problem, show credibility and differentiation, then make a specific ask.

This is a personal write-up based on QcES materials (Spring 2024 cohort) and facilitators; it is not an official program document.

Why these pieces fit together

In practice you don’t “finish” the BMC once. You state hypotheses, collect qualitative evidence (interviews, observation), adjust segments and value proposition, then prioritize what goes on a roadmap and into a pitch. The loop below summarizes that motion.

flowchart LR
  hyp[Hypothesis] --> int[Interview]
  int --> ins[Insight]
  ins --> bmc[BMC and segment]
  bmc --> road[Roadmap]
  road --> pit[Pitch]

Business model: the BMC as a shared language

The BMC bundles nine blocks (segments, value proposition, channels, customer relationships, revenue, resources, activities, partners, cost structure). The core idea: every block matters for survival, and the canvas is a living artifact—revisit it when customers or competitors shift.

The coursework stresses sequencing: understand for whom you create value and how you promise it before over-optimizing the rest. The hypothesis–validation loop ties research, interviews, and decisions—you test beliefs about the customer and the problem, not only about technology.

Customer segments: from fuzzy to actionable

It helps to separate consumer, end user, and buyer (who pays isn’t always who uses). An “early” customer often has a problem, awareness, active solution search, sometimes a hacky workaround, and a plausible budget.

B2B segmentation tends to be firmographic (size, location, sector, buying dynamics). B2C uses demographics, geography, psychographics, behavior. The exercise is to replace overly broad buckets with testable segments—people you can actually find, contact, and interview.

Sharing the idea and getting feedback

A ~90 second, slide-free pitch forces clarity: a problem outsiders can follow, who benefits, the solution, and its advantages. You are not expected to cover market size and competition on day one; it is a clarity filter.

To receive feedback: active listening (understand before you rebut), notes, a learning mindset. To give feedback: name a real strength, then one opportunity (“I’d want to hear more about…”, “this would be stronger if…”).

Interviews: discovery is continuous

Interviews are framed as the most direct way to fill gaps in an early BMC. The aim is not to sell or “pitch” your fix during the call, but to learn from someone else’s reality.

People to talk to often extend beyond the “ideal customer”—users of substitutes, experts, suppliers, communities—anyone touched by the problem. And it is not one-and-done: discovery continues through pivots.

Typical hurdles—finding the right people, booking time, running a useful conversation—yield to preparation and humility. The mantra: fall in love with the problem, not the solution; connect rather than convince.

Roadmap and maturity: PoC, prototype, MVP

A roadmap communicates where you are headed (vision, key initiatives) over a chosen horizon for a specific audience (team, investors, partners). It is not the same as an operational project plan. Before filling it in, prompts include vision, readers, timeline, metrics, scope, resources, and an appropriate format.

Proof of concept: the underlying approach can work. Prototype: explore how users interact; often pre-market. MVP: just enough to put in front of real users or buyers to learn fast (including by watching what breaks). Roadmaps change shape with stage—discovery, validation, growth.

Market context and value proposition

Understanding the market is more than counting accounts: it places the venture amid external forces—macro (PESTEL-style), industry dynamics, customer behavior, major trends. Those lenses surface constraints and openings.

Value proposition spans what you deliver (product, service, “vehicle”) and the benefit to the customer. Course slides stress pain points and a hypothesis about why people care—raw material for discovery interviews.

Storytelling and pitch: Hook, Believe, Join

A pitch is a talk that seeks a concrete next step: someone’s time, lab access, intros, funding. Formats vary—from thirty seconds to half an hour, with or without slides.

A structure that showed up repeatedly:

1. Hook — start from the problem and why it matters to an identifiable audience; do not open with the solution.
2. Believe — present the solution, differentiation, and evidence (traction, team, recent wins).
3. Join — a specific ask: type of help, amount, expertise, partnership, etc.

A typical ~90 second scaffold runs: who you are, problem, offer for a target, value proposition, contrast with alternatives, recent milestone, call to action.

Closing thought

QcES connects tools (BMC, segmentation, roadmap) with behaviors (interviews, feedback, pitching). The thread: keep the problem central, make assumptions testable, and communicate clearly enough that others can help—not only cheer.

If you are in a similar program, consistency usually beats polish: a handful of well-run interviews often teaches more than a perfectly decorated canvas.