VALUE PROPOSITION WORKSHEET Space Office | https://www.spaceoffice.ai/blog/value-proposition Version: 2026-10-12 An original worksheet for connecting customer evidence to a message you can test. This is not the Strategyzer Value Proposition Canvas. Use one customer situation per worksheet. Mark unknowns instead of inventing facts. 1. CUSTOMER AND SITUATION Customer or user: Buyer or final decision maker, if different: Specific task and the event that makes it important: Current workaround, including doing nothing: Who is outside this draft's scope: 2. NEED AND EVIDENCE Important problem or desired outcome: Why it matters in this situation: What the current alternative does well: What changing tools or services would require: Evidence entry (repeat for each important observation): Source reference and date: Permission or access conditions: Situation and relevant context: Observation or exact approved quote: Type: observed action / customer report / interpretation / hypothesis What this supports: What this does not establish: Contradictory evidence or unanswered question: 3. OFFER AND PROOF Current product or service capability: How that capability helps with the chosen outcome: Source or demonstration that verifies it: Important conditions, requirements, and limits: Person who can verify the claim: Claims we cannot make yet: 4. MESSAGE OPTIONS Drafting prompt: For [customer in a specific situation], [offer] helps you [important outcome] through [verified capability]. You can check this by [evidence]. It applies when [essential condition]. Option A headline: Supporting sentence: Proof to show nearby: Conditions to make visible: Next step offered to the reader: Option B headline: Supporting sentence: Different benefit or emphasis being investigated: Proof to show nearby: Conditions to make visible: 5. CHECK EACH CLAIM Claim: Evidence reference: Capability confirmed by: Wording stronger than the evidence? If yes, revise: Customer data or quotation cleared for public use? If relevant, verify: 6. TEST PLAN Main uncertainty: understanding / relevance / behavior / other Intended audience and recruitment criteria: Exact message version and context participants will see: Neutral questions or tasks: Observed action or outcome to record: Decision rule agreed before interpreting results: Owner and review date: Known sample or measurement limits: Useful questions: - What do you think this offer lets you do? - Who do you think it is for? - Describe the last time you handled this task. - How do you handle it now, and what would you keep about that process? - What information would you need before deciding on the next step? 7. DECISION RECORD What we observed: What remains uncertain: Decision: keep / revise / reject / gather more evidence Reason and source references: Human approver: Publication or testing action separately authorized: Next review trigger: ILLUSTRATIVE FILLED EXAMPLE: REVIEWHARBOR This is a fictional product and hypothesis, not customer research or measured results. Customer: small design studio owner preparing a client-approved design for production. Need: identify the accepted version without reconstructing email and folder history. Offer: keep a design version, comments, and a recorded client decision together. Proof to obtain: demonstration of upload, review, approval, and later version changes. Conditions to check: file types, reviewer account requirements, access to old decisions. Candidate headline: Know which design your client approved. Supporting sentence: Keep each design version, its feedback, and the recorded client decision together before you send work to production. Unknown: whether the problem occurs often enough to justify changing the current process. Do not claim: guaranteed replies, faster completion, fewer revisions, or quantified savings. Next check: verify the product behavior, then investigate understanding and relevance with people who handle this task. A human decides whether to keep or change the message.