Assemble · Create · Analysis & Finance

Enhanced business model canvas

A business model canvas assembled from your existing canvases instead of written from scratch: the value proposition canvas fills the Value Propositions box, the customer profile fills Customer Segments, and the operating model canvas fills the back stage (Key Partners, Key Activities, Key Resources, Cost Structure), with every carried item machine checked against the upstream deliverable it came from.

You receive: A JSON object { market_type, boxes{9 boxes} } where each derived box carries a summary, its carried items, and a source label naming the upstream canvas section, and the native boxes (Channels, Customer Relationships, Revenue Streams) carry a summary plus your intake selections.

Part of Get First Users

What's verified: STUD verifies the deliverable parses as a JSON object, that each of your three pasted upstream deliverables parses as JSON with its play's exact shape (the value proposition canvas arrays productsAndServices, painRelievers, gainCreators; the customer profile arrays customerJobs, customerPains, customerGains; the six operating-model element arrays), that market_type equals your intake selection and is one of the five published values, that all nine boxes are present as objects with a summary of at least 12 characters, that every derived box carries its exact published source label, and that derivation is element-level: every item in the Value Propositions sub-lists appears verbatim (ignoring case and surrounding spaces) in the corresponding value proposition canvas array, every Customer Segments entry appears in the customer profile, every Key Partner appears in the operating model suppliers, every Key Activity in the value delivery chain or management system, every Key Resource in locations, organization, or information, and every Cost Structure item names a driver drawn from the operating model elements; Channels and Revenue Streams must echo your intake selections, and no em or en dash may appear anywhere. Selecting a subset of upstream items is allowed; an item absent from the upstream inputs fails. STUD does NOT verify that the pasted upstream deliverables match any particular past run (they freeze into this contract exactly as submitted), and does NOT judge the quality of the summaries beyond the length floor.