Start with what the writing must do.
A team can agree on a catchy line while disagreeing about its customer. Separating these outputs makes that disagreement easier to see. We use the following practical definitions throughout this site; teams may use the terms differently.
| Output | Main job | Typical use |
|---|---|---|
| Positioning statement | Record audience, category, value and difference against an alternative. | Internal alignment |
| Value proposition | Explain a relevant benefit and why it is worth choosing. | Homepage, pitch, sales conversation |
| Tagline | Make one idea easy to remember. | Brand or campaign expression |
A positioning statement can be detailed and functional. Customer-facing copy needs to fit the reader’s moment and level of awareness. A tagline has very little room; the rest of the page must supply context.
One product, three outputs.
Patchwork is a fictional teaching product. Assume it connects customer bug reports to engineering status. We will use those same choices in each output.
1. The positioning statement
Product name: Patchwork Audience: small software teams managing customer-reported bugs Audience need: Give support a reliable answer on what has been fixed. Category: issue tracking software for support-to-engineering handoffs Value promise: Support knows which customers to notify when a bug is fixed. Alternative or competitor: a shared spreadsheet and chat threads Key difference: Each customer report stays linked to its engineering ticket and resolution.
This version lets the team inspect the audience and the shared-spreadsheet alternative. Its value is in making choices explicit. The labelled format is useful for review; a homepage needs a shorter entry point.
2. The value proposition
Know which customers to notify when a bug is fixed. Patchwork connects customer reports to engineering status, so support can follow up with the right people.
The same underlying choices now speak to the reader’s work. A real page could demonstrate a report moving from support to engineering and back. That would show how the product helps someone follow up.
3. A possible tagline
Close the loop.
It is short enough to remember, but says very little about software or customer reports. Used alone, it could describe many unrelated products. Treat it as an optional expression beside a clear explanation, not as the entire message.
Choose the output for the decision in front of you.
- Your team disagrees about who buys: work on positioning and its evidence. A slogan exercise will not settle that.
- A prospect cannot tell what changes for them: improve the value proposition and show the relevant product behavior.
- The offer is understood but the expression is forgettable: explore a tagline that supports the established message.
Keep the chain intact. If you narrow the audience in the statement, check whether the homepage still promises something for everyone. If you change the product’s capabilities, check whether the promised benefit remains true.
Reference and a short exercise
Strategyzer’s Value Proposition Canvas connects a customer’s jobs, pains and gains to the value an offer provides. It is useful for exploring the substance behind a value proposition. Our three-output comparison and Patchwork wording are an editorial teaching exercise. Source checked 1 October 2026.
Write one version of each output for your product. Underline the audience and intended outcome wherever they appear. If they change between versions, decide whether that change is deliberate. Then use the worked walkthrough to plan what to test.
Put the decisions into words.
Use your own inputs to make a working draft. Then test its assumptions with prospective customers.
Open the free builder