Use this business model canvas template to connect the customer promise to the work and resources needed to deliver it. The filled example maps a hypothetical bicycle tune-up service, then compares evening collection with a daytime-only alternative.
Start with one proposed business model
The original fictional example is a service that collects bicycles from apartment buildings, performs routine tune-ups, and returns them. The proposed customer is an apartment resident who has limited repair space and wants collection outside the working day. That customer need is an assumption to investigate, not a finding from interviews or sales.
Strategyzer's Business Model Canvas describes a model through nine blocks covering how value is created, delivered, and captured. The point of putting them together is to examine their relationships. A long list in each box can still conceal an impractical combination.
Here is the complete Model A: evening collection teaching example:
| Block | Proposed content |
|---|---|
| Customer segments | Apartment residents with limited repair space who want collection outside the working day. |
| Value propositions | Routine bicycle servicing with an agreed evening collection window and a clear service-scope confirmation. |
| Channels | Building notices and a booking page explain the service and request a collection slot. |
| Customer relationships | Booking confirmation, service-scope confirmation before work, a return arrangement, and a service checklist. |
| Revenue streams | A service fee for each completed tune-up; price and willingness to pay remain to be investigated. |
| Key resources | Mechanic time, tools, transport capacity, and booking/service records. |
| Key activities | Arrange collection, inspect the bicycle, confirm the work scope, perform the service, and arrange return. |
| Key partners | Proposed building contacts for collection arrangements and an overflow repair shop; no agreement is supplied. |
| Cost structure | Mechanic labor, transport, consumables, and booking administration; amounts are not supplied. |
This is a model for discussion. It contains no verified demand, partner commitment, market price, revenue forecast, or claim that servicing can be delivered at a profit. Keep those questions separate from the fact that all nine blocks contain text.
Follow a promise through the operating blocks
Select Value propositions in the example. Read “evening collection” beside the customer segment, key activities, resources, and costs it affects.
The segment explains why that window might matter. Collection and return make it operational work. Mechanic and transport capacity determine whether the proposed arrangement can be offered. Labor and transport belong in the cost discussion. The booking channel must describe the same window the team intends to deliver.
The revenue stream completes another connection: the service fee has to be considered alongside those delivery costs. Without a supplied price, service volume, time requirement, or cost estimates, this canvas cannot calculate a margin. It can tell you which inputs the next financial model needs.
Write these connections in plain language. “Evening convenience requires evening collection capacity” is more useful in a review than treating Convenience and Logistics as unrelated headings.
Compare an alternative without leaving the old promise in place
Choose Compare daytime-only model. Model B proposes collection only on weekday mornings. It is a different model to investigate, rather than a confirmed improvement to Model A.
| Connected area | Model A: evening collection | Model B: daytime-only proposal |
|---|---|---|
| Customer segment | Residents seeking collection outside the working day. | Residents who can make a bicycle available on weekday mornings; fit with the original segment needs review. |
| Value proposition | Servicing with evening collection. | Servicing with weekday-morning collection; remove the evening promise. |
| Channels and relationships | Notices, booking copy, and confirmations describe the evening window. | Revise the same materials to describe morning availability and agree the actual handoff. |
| Activities and resources | Plan collection work and transport capacity for evenings. | Plan that work and capacity for mornings; confirm who and what is available. |
| Costs and revenue | Delivery costs and service-fee assumptions need estimates and testing. | Re-estimate delivery costs and test the revised offer; no lower cost or retained sales is established. |
Key partners also need to review the changed collection arrangement. The presence of an overflow-shop box does not establish that the shop accepts either operating window.
The comparison helps the team ask a practical question: Can the original customers use the proposed morning handoff, or does the alternative need a different segment or collection arrangement? Answer that before keeping the original customer promise in a model that no longer delivers it.
Decide what to investigate next
For this example, begin with the dependency that could change the offer. Ask prospective customers about their actual collection constraints, and discuss feasible collection arrangements with the people who would deliver them. Record what you learn against the relevant model assumptions.
Keep estimates and observations distinct. An operator's proposed collection capacity is an operating assumption until the relevant work establishes it. A positive response to an idea does not supply a paid booking or a reliable sales forecast.
Date the model when you review it, identify the version, and note which assumptions changed. Retain the earlier version long enough to explain the alternative. The canvas can guide the next conversation while your research, detailed operations plan, and financial model remain in their own working records.
Copy a prompt for the complete canvas and comparison
Create one complete HTML business model canvas review page.
My proposed service/product and model-review question: [PASTE]
Customer segments and value propositions: [PASTE]
Channels, customer relationships and revenue streams: [PASTE]
Key resources, activities, partners and cost structure: [PASTE]
Evidence already available, with references: [PASTE]
Assumptions to test and alternative model, if any: [PASTE]
Actual model version and review date: [FILL IN]
Use my supplied information. Show all nine named blocks and their
connections. Keep facts, estimates and hypotheses distinguishable.
Do not invent customer research, demand, prices, partner agreements,
capacity, revenues, profit or validation. An empty block is an open
model question; a filled block is not proof that the model works.
Include this separate original hypothetical bicycle-service example.
Label the entire example Hypothetical model; no operating business
or customer research is represented. No review date is supplied.
Model A: evening collection.
Customer segments: apartment residents with limited repair space
who want collection outside the working day.
Value propositions: routine bicycle servicing with an agreed
evening collection window and clear service-scope confirmation.
Channels: building notices and a booking page explain the service
and request a collection slot.
Customer relationships: booking confirmation, scope confirmation
before work, return arrangement and a service checklist.
Revenue streams: service fee per completed tune-up; price and
willingness to pay need investigation.
Key resources: mechanic time, tools, transport capacity, and
booking/service records.
Key activities: arrange collection, inspect bicycle, confirm scope,
perform service and arrange return.
Key partners: proposed building contacts for collection arrangements
and an overflow repair shop; no agreements supplied.
Cost structure: mechanic labor, transport, consumables and booking
administration; amounts not supplied.
Provide a Value propositions selection that shows its connected
segment, collection activities, capacity/resources, cost questions
and booking promise. Keep all nine blocks available, with written
labels that explain links without relying on color or arrows alone.
Compare daytime-only model must show Model B beside Model A:
B collection is weekday mornings only. Its segment is residents
who can make a bicycle available in that window; fit with A's
segment needs review. B's offer must say morning, not evening.
Revise notice/booking/confirmation wording and agree the handoff.
Plan morning collection work and transport/mechanic availability.
Revisit building/repair-shop arrangements. Re-estimate costs and
test the revised offer. No lower cost, retained sales or improved
profit is established. Revenue remains a proposed service fee.
Explain each connected change; do not silently modify A.
Add a separate blank nine-block scaffold for my model and a local
area for review questions. Preserve typed questions across model
switches and ask before clearing them. No viability score, market
validation badge, financial forecast, booking or partner contact.
Use at least 16px text, native labeled controls and visible focus.
Make nine blocks readable at 720px; at 360px stack the same labeled
blocks without page overflow. Inline CSS/JavaScript, no external
assets, network, storage or pretend exports. State that typed notes
remain in this open page only. Return the complete HTML.
Check that the generated page keeps the two models separate. Read the customer promise against the activities and resources in each. If a model says evening in one place and morning in another, resolve the inconsistency before discussing its appearance.
Review the connected model with a colleague
Put the HTML in your NOS workspace when you want someone to read the customer offer beside the delivery assumptions. Ask them to follow the collection window from the value proposition through the booking promise and operating work.
You can clarify the static model description or the explanation of a connection in visual editing mode, then save it for your colleague to reopen at the existing link. Check any separately maintained scenario data too; changing an explanation does not recalculate a financial model or update programmed alternative-model text.
Use the review to choose the assumption you will investigate next. Bring the findings back to the canvas and record whether they change the customer, the offer, or the way the business would deliver it.