Startup Value Proposition

Use this skill when the startup needs a sharp promise, not a feature inventory.

Use when

• The user wants a value proposition or positioning statement.
• A startup has a segment in mind but the promise is still generic.
• Messaging needs to connect tightly to customer pain and alternatives.

Do not use when

• The segment is still too unclear to anchor a value proposition.
• The task is purely financial or operational.
• The user only wants a slogan without strategic grounding.

Value proposition failures to avoid

• describing the product before naming the customer
• saying "all-in-one" instead of explaining the actual progress unlocked
• skipping the current alternative
• confusing outcome claims with evidence
• writing a statement too broad to guide product or GTM choices

Workflow

1. Who

• who the target customer is
• what context or constraint matters most

2. Why

• what core problem or JTBD matters
• why it is painful enough to justify switching

3. What before

• what the customer uses today
• what is frustrating, slow, risky, or expensive

4. How

• what the startup does that changes the situation
• which product capabilities matter most

5. What after

• what life or work looks like when the problem is solved
• what new outcome becomes possible

6. Alternatives

• what other products, workflows, or "do nothing" options exist
• why the startup's approach is better for this segment

7. Distill the statement

Finish with:

• a concise value proposition statement
• a positioning statement
• the proof points still missing

Output format

Return:

1. Target segment

2. Core problem

3. Current state

4. Product mechanism

5. Improved outcome

6. Alternatives and why we win

7. Value proposition statement

8. Positioning statement

9. Weak points or missing proof

Use together with

• startup-founder-problem-framing
• startup-ideal-customer-profile
• startup-go-to-market-strategy