A clearer approach to business model design.
Explore business model design, with practical workflows, a working example and checks for common mistakes.
Explore the guide ↗Business Model Workshop is a focused resource for founders and business designers, exploring business model design through the work people actually need to perform. For this topic, the workflow is to connect audience to value, describe delivery requirements, and examine operating trade-offs. This guide uses a value and revenue model map to hold the decisions together and examines customer needs, cost drivers and delivery dependencies as distinct quality concerns.
The example involves a founder comparing project work with an ongoing service; it is an illustrative exercise for this subject, rather than a reported client result. A revenue model has to connect value creation with delivery capacity. Examine who pays, what they receive and what must happen repeatedly, rather than treating a pricing mechanism as a complete business model.
Ideas into action
BUSINESS / 10 SECTIONSThe purpose of business model design
Start by describing the task that makes business model design relevant now. Use the situation of a founder comparing project work with an ongoing service to identify the practical question before choosing a method. A concern involving customer needs may require different evidence from a concern involving cost drivers.
Keep those questions visible in a value and revenue model map, alongside the intended outcome. The scope of business model design becomes easier to discuss when an agreed requirement is clearly distinguished from an idea that still needs investigation. Before proceeding with business model design, decide whether the current state of delivery dependencies creates a dependency that needs another person's input.
A value and revenue model map
Use a value and revenue model map as a shared reference for this piece of business model design. The record is especially useful when founders and business designers need to explain why a particular route was chosen. Connect the entry about customer needs to the relevant evidence for business model design, rather than copying information without its source context.
Review a value and revenue model map after a meaningful change; an abandoned reference can mislead the next person working on business model design.
The first working stage is to connect audience to value. In the example involving a founder comparing project work with an ongoing service, identify which input is needed before this action can produce a dependable result. Consider how questions about customer needs affect the starting conditions for the action to connect audience to value, including information that has not been confirmed.
Record the outcome in a value and revenue model map and explain any limitation before asking somebody to describe delivery requirements. This creates a traceable starting point for business model design, making an incomplete input easier to recognise before it influences the rest of the work.
Describe delivery requirements
04 / 10Continue by deciding how to describe delivery requirements under the agreed conditions. The handoff from the first stage of business model design should contain the information this action actually requires. Before you describe delivery requirements, inspect cost drivers and identify any assumption that has become doubtful.
If the situation involving a founder comparing project work with an ongoing service reveals a different requirement, update a value and revenue model map before expanding the work. A visible change decision keeps business model design coherent and helps the next participant understand whether the original scope still applies.
Examine operating trade-offs
The third stage is to examine operating trade-offs, bringing the current piece of business model design to an understandable state. Check delivery dependencies against the agreed purpose of business model design, not merely against a list of completed activities. Use a value and revenue model map to identify follow-up responsibilities and relevant limits.
In the example of a founder comparing project work with an ongoing service, ask what the receiving person would need before relying on the output. Closing this stage of business model design clearly prevents an unfinished dependency from being mistaken for an accepted result.
Avoid designing revenue without a credible delivery model
A specific failure pattern in business model design is designing revenue without a credible delivery model. It can create a gap between the appearance of progress and the actual outcome needed by founders and business designers. Check whether customer needs was understood before the action began and whether cost drivers was examined by somebody with the relevant context.
Capture the correction in a value and revenue model map, including its effect on delivery dependencies. The aim is to reduce the opportunity for designing revenue without a credible delivery model to recur, while keeping the process proportionate to the work.
Work through a realistic situation
Consider a founder comparing project work with an ongoing service as a small rehearsal of business model design. Write down the request and expected result, then identify who performs the action to connect audience to value. Before moving to the instruction to describe delivery requirements, ask which information the next participant needs.
Use a value and revenue model map to preserve any question the example exposes, especially where customer needs is uncertain. Then decide how to examine operating trade-offs without hiding a concern about delivery dependencies.
Check cost drivers
08 / 10The review criteria for this guide are customer needs, cost drivers and delivery dependencies. Examine each criterion separately in the context of business model design, because a positive finding in one area does not settle the other questions. For founders and business designers, a useful review records what was examined and how the finding affects the next action.
Connect the evidence to a value and revenue model map, including any limitation in the material available. In the situation involving a founder comparing project work with an ongoing service, identify which finding would prevent a responsible handover. This approach makes the review of business model design explainable, rather than treating an unexplained approval label as evidence that the task is ready.
Keep the guidance useful after the first pass
Maintenance of business model design should respond to changes in the task, its inputs and its responsible people. Assign an owner to a value and revenue model map and explain which events should trigger another review. A changed assumption about customer needs may affect the earlier decision to connect audience to value; a concern about delivery dependencies may require a new closing check.
Remove obsolete directions from a value and revenue model map deliberately so that earlier versions do not compete with approved guidance. When cost drivers changes, explain whether the instruction to describe delivery requirements needs different inputs or a revised decision.
Choose a practical next step
Begin with one bounded task involving business model design rather than a complete redesign of the surrounding operation. Prepare a value and revenue model map, work through the three actions and inspect the result using the criteria for customer needs, cost drivers and delivery dependencies. Ask someone from the intended audience of founders and business designers to identify a point that still needs clarification.
Compare that observation with the example of a founder comparing project work with an ongoing service, then choose a specific change worth testing.