Business Model Canvas AI Prompt

Generate a full Business Model Canvas with this AI prompt. Nine blocks covering customers, value, channels, costs, and revenue. Free to copy and use today.

The prompt

ROLE: You are a business model innovation consultant certified in the Strategyzer Business Model Canvas method.

CONTEXT: Company: [COMPANY]. What we sell: [OFFERING]. Who buys: [CUSTOMERS]. How we sell: [SALES_CHANNELS]. Current revenue: [REVENUE].

TASK: Complete a full Business Model Canvas and then suggest one improvement.

FORMAT: Part 1: all 9 canvas blocks (Customer Segments, Value Propositions, Channels, Customer Relationships, Revenue Streams, Key Resources, Key Activities, Key Partnerships, Cost Structure), each with 3-5 concise bullets. Part 2: a section called Model Stress Test with 3 questions that could break this model. Part 3: One Concrete Improvement, a specific change to one block with expected impact.

CONSTRAINTS: Keep bullets under 15 words each. Be specific to my business, no generic filler like leverage synergies. If a block is weak or empty in reality, say so plainly instead of inventing content.
If any variable is unclear or missing, ask up to 3 targeted clarifying questions before producing the output, and clearly mark every assumption you make with [ASSUMPTION].

Variables to fill in

Replace each [variable] in the prompt with your own details:

[COMPANY] [OFFERING] [CUSTOMERS] [SALES_CHANNELS] [REVENUE]

Example input

COMPANY=GreenGrow, OFFERING=organic fertilizer subscription for home gardeners, CUSTOMERS=suburban homeowners aged 30-55, SALES_CHANNELS=Shopify store + garden center retail, REVENUE=$400k/year

How to use this prompt

Run the prompt, then do the Stress Test section with your team: try to honestly break your own model before competitors do.

Tips for the best results

Print the canvas on one large sheet; teams think better when they can see all nine blocks at once.
Revisit the canvas after any major change in pricing, channels, or customer segment.
The improvement suggestion is a starting point: validate it with a small test before committing.