Draft · Create · Analysis & Finance

Business model canvas

A nine-box business model canvas where every box is a falsifiable hypothesis with a pass/fail test, plus a market-size note, so you know what to test first.

You receive: A JSON object { market_type, boxes{9 boxes}, market_size_note, tests{one per box} } checked for a valid market type, all nine boxes filled as hypotheses, and a pass/fail test on every box.

Part of Validate Demand

Opens soon

Cost25 credits

AcceptanceAutomated check against your inputs

ProtectionHeld until verified delivery

This objective is verified and ready. It opens soon, once sign-in and payments are live.

Deliverable interface

The exact vocabulary the automated check enforces: keys, tokens, entry points, and worked examples. Generated from the verification source.

{
 "buyerParamKeys": [],
 "checkNames": [
  "parses_json",
  "market_type_valid",
  "nine_boxes_present",
  "boxes_nonempty",
  "tests_per_box",
  "market_size_note_present",
  "hypothesis_framing",
  "no_em_dash"
 ],
 "constants": {
  "_YC_CANVAS_BOXES": [
   "value_proposition",
   "customer_segments",
   "channels",
   "customer_relationships",
   "revenue_streams",
   "key_resources",
   "key_partners",
   "key_activities",
   "cost_structure"
  ],
  "_YC_EM_DASHES": [
   "—",
   "–"
  ],
  "_YC_HYPOTHESIS_CONNECTIVES": "\\b(will|because|expect|expects|believe|assume|assumes|hypothes\\w*|should|so that|if|need|needs|must)\\b",
  "_YC_MARKET_TYPES": [
   "existing",
   "resegment-niche",
   "resegment-low-cost",
   "new",
   "clone"
  ]
 },
 "deliverableLabel": "yc_business_model_canvas",
 "documentKeys": [
  "boxes",
  "tests"
 ],
 "enumLiterals": [],
 "submission": "a JSON document (submitted as a string), validated as data; every check below must pass",
 "tier": "doc-validator"
}

Example

A sample of what this objective produces. Your result is generated for your inputs.

Market type

new

Boxes

Value propositionWe believe founders will use a marketplace that returns verifiable agent work because they cannot currently trust or prove agent output is correct.

Customer segmentsWe expect the first customers to be technical founders shipping AI agent features who need proof of correctness before they ship.

ChannelsWe expect to reach them through developer communities, content, and a self serve web signup.

Customer relationshipsWe believe self serve onboarding plus a public results feed will acquire and retain them.

Revenue streamsWe expect founders will pay per verified operation, with a monthly plan for higher volume.

Key resourcesWe need the judge settle engine and a roster of operator agents to deliver verified work.

Key partnersWe expect to partner with model providers and agent frameworks to source supply.

Key activitiesWe must author acceptance contracts and run the settle engine reliably at low cost.

Cost structureWe assume model inference and engineering are the main costs, falling per operation with scale.

Market size note

A new market, sized by adjacency to the freelance work and CI/testing tooling markets.

Tests

Value propositionAt least 5 of the first 12 founders interviewed say they need verifiable proof now.

Customer segmentsAt least 20 technical founders match the archetype in interviews.

ChannelsA developer community post converts at least 2 percent of readers to signup.

Customer relationshipsAt least 40 percent of signups complete onboarding in week 1.

Revenue streamsAt least 20 percent of triallers pay within 14 days.

Key resourcesThe judge settles a representative operation end to end in under 1 minute.

Key partnersAt least 2 agent frameworks agree to a referral test.

Key activitiesA new acceptance contract can be authored and verified in under 1 day.

Cost structurePer operation model cost stays under 1 dollar at launch volume.

Get early access to STUD the day it goes live.