By the end of this article, you will have a short customer promise, a reason someone might believe it and one thing to test. You can write it for an existing product, an early idea or the fictional business below. You do not need a logo or an advertising account.
Begin with the customer's question
When somebody sees a product for the first time, they may ask: “Will this help me do what I need, and can I trust what it promises?” A list of features can leave that question unanswered. A value proposition is a concise promise about the benefit a particular customer can expect from an offer (Gomez Albrecht, Green and Hoffman, 2023). The promise has to match what the business can actually provide.
Here is a small example. Maya's Lunch Box is fictional. It is considering a preorder lunch service for workers near a station. Maya's first line is “Order with our online form.” That describes a feature: a thing the service has or does. A possible benefit is “Know when your lunch should be ready to collect.” The benefit concerns the customer's short break. Maya still needs to test whether customers value collection certainty and whether she can deliver it. She should not claim to save everyone fifteen minutes when nobody has measured that.
A good promise is specific enough to be understood and modest enough to be kept. It is an invitation to test a real offer, not permission to invent results.
Four words that change how you write
A feature is a characteristic of the offer: an online form, washable fabric or a same-day appointment option. A benefit is a useful result or reduced difficulty for someone: planning collection, cleaning the garment more easily or getting a clear time to speak with a professional. The same feature can have different benefits for different people. It may also be irrelevant to some people.
A value proposition connects the offer to a customer's need and the value they might receive. “We use modern technology” tells the reader very little. “See the available lunches and their collection times before you order” describes a possible practical advantage. OpenStax treats value as the benefit the customer receives in relation to what they give up, including costs such as time and money (Gomez Albrecht, Green and Hoffman, 2023).
A unique selling proposition (USP) is a reason to choose one offer over relevant alternatives. Do not write “the only,” “the best,” “the fastest” or “the cheapest” merely because you want to stand out. Those are comparison claims. Check whether they are true, current and meaningful to customers. An honest difference could be a narrower service that fits one group's circumstances particularly well.
An online value proposition (OVP) asks what someone gains from interacting with your business online. It could be clear information, convenient ordering, a useful comparison or accessible help. Having a web page is not itself a customer benefit. The page has to help someone do something.
You may also hear differentiation, meaning a difference customers can notice and care about, and proof, meaning a reason to believe a claim. Proof can be a real demonstration, accurate process details or genuine customer feedback used with permission. A picture of a fictional five-star review is not proof.
Understand the job before describing your solution
The makers of the Value Proposition Canvas suggest thinking about the customer's job, pains and gains before matching a product to them (Strategyzer, no date). You can use those ordinary words without filling in a formal canvas.
A job is what somebody is trying to get done. Maya's possible customer wants lunch during a short break.
A pain is what makes that difficult or unpleasant. The person may be unsure how long a queue will take. This is a hypothesis until Maya asks.
A gain is a result the person wants. Perhaps they would value a predictable collection time. Again, Maya should check rather than assume.
Write these from the customer's side, before mentioning your product. “The customer wants our app” is rarely the underlying job. “The customer wants to know whether a suitable lunch will be ready before their break ends” gets closer to a question Maya can investigate.
If you sell to another business, the same method works. A small shop owner might want to see what stock is available without calling the storeroom. The pain could be uncertainty and repeated checking. The gain might be a dependable view of stock at a particular point in time. An app would be a possible way to help, but the promise must not outrun what that app actually records.
Write a first promise in four pieces
Try this structure. It is a writing aid, not a rule that every public headline must follow word for word:
For [a particular person] trying to [do a job], [our offer] helps with [a believable benefit] because [a feature or process we can really deliver].
Maya could write: “For workers near the station who have a short lunch break, Maya's Lunch Box offers a small preorder menu with a stated collection time, so they can plan when to pick up lunch.” It names a person, a situation, an offer and a possible benefit. Because the service is fictional and untested, this sentence is an illustrative proposal, not evidence that customers want it.
Now compare three versions:
Too vague: “Fresh food with innovative digital solutions.” What does the person get, when and where?
Too certain: “The fastest lunch in town, guaranteed.” Maya has not compared all alternatives or proved the timing.
More useful to test: “Choose from today's available lunches and see a stated collection time before you order.” The customer can understand the proposed process. Maya still needs to check that it works reliably.
A short sentence can sit at the top of a page. Beneath it, answer practical questions: what is included, what it costs, where it is available, how collection works and whom to contact if something goes wrong. Clarity after the headline is part of the promise.
Check that your promise is deliverable
Before publishing a claim, ask:
Can we actually provide this? If Maya can prepare only ten lunches in a time slot, the ordering process must reflect that capacity.
Can the customer understand the conditions? Collection times, availability and price should be visible before someone relies on them.
What would show that the claim is true? A clear process or a limited trial may support a narrow claim. A measured time-saving claim would need an appropriate measurement.
What happens if we cannot keep it? The business needs a realistic way to explain a delay or correct an error.
An offer has value relative to the effort and cost of obtaining it. Maya's customer may care about food quality, dietary information, price, location and time. A quick ordering page cannot compensate for a collection point that is too far away. This is why marketing includes the service experience as well as the words on a page.
For a proof note, Maya could write: “We show what is available for each collection slot.” That is a description she can verify in her own test. She should not invent testimonials, orders or customer satisfaction results. When real evidence becomes available, she can revise the note and keep the date and context of any numbers.
Use the six Cs to improve the online experience
Dave Chaffey's six Cs of online customer motivation, explained by Hanlon (2016), are Content, Customisation, Community, Convenience, Cost Reduction and Choice. They are possibilities to check, not six promises that every new business must make. Maya might reasonably start with just Content and Convenience.
Content — can the customer find the right information?
Content includes clear details about the product or service. Maya might display the current menu, ingredients, price, collection location and an explanation of how to order. A beautiful photograph cannot replace missing price or availability. For another business, helpful content might be an explanation of what a consultation includes.
Customisation — is there an appropriate option for different needs?
This can mean tailoring information or products to a person or group (Hanlon, 2016). Maya might offer a limited, accurate choice of meals that she can actually prepare. Customisation becomes a problem if every variation makes preparation unreliable. Do not claim personalisation simply because you ask people for unnecessary personal details.
Community — would interaction between people help?
A genuine community can help people share tips or support one another. Maya probably does not need to start a forum to sell lunch. If customers mainly want a dependable collection time, a discussion space adds effort without solving the core problem. A different business, such as a hobby service, might find community genuinely useful.
Convenience — can the person do the task with less difficulty?
For Maya, convenience might mean checking the menu and a collection time without a phone call. But if the page is hard to read on a phone, the supposed convenience disappears. Look at the whole journey: finding information, ordering, paying if relevant, collecting and getting help.
Cost Reduction — is there a real saving?
A saving might be in money, time or effort, but a numerical claim needs evidence and a clear comparison. Maya should leave out “save £5” or “save 15 minutes” unless she can support it. She can still explain an ordering process that may reduce uncertainty, without claiming an unmeasured saving.
Choice — are there useful alternatives?
Choice might mean a suitable range, payment method or collection option. A long menu is not automatically helpful. Maya should offer only what she can keep available and describe it accurately. For customers with different needs, a smaller dependable range may be more valuable than many unavailable options.
Figure 1
The six Cs help you ask which part of the online interaction matters for this audience. They do not prove that people want an offer. For Maya, “clear menu + dependable collection information” is a reasonable hypothesis to test. The framework's original purpose is to think about an online value proposition (Hanlon, 2016).
Test the wording without asking for compliments
Write the promise on one card and show it to a few people who resemble the intended audience, where appropriate. Do not begin with “Do you love my idea?” Ask what they understand. For example:
“What do you think you would receive?”
“How would you normally solve this problem?”
“Which detail would you need before deciding?”
“What, if anything, sounds unclear or hard to believe?”
Record their words separately from your interpretation. If someone says “I cannot tell where I collect it,” the observation is about missing information. It does not mean they would definitely buy if you added an address. If three people ask about dietary information, that is a useful clue, not proof that everybody has the same priority. Revise the promise, then check whether the actual service can meet it.
If no one is available to ask yet, do a self-check: hand the card to someone unfamiliar with the business and ask them to describe the offer without your help. That tests clarity, though not market demand.
Try it: write and improve your own promise
Allow fifteen minutes. Use Maya's fictional example if you do not have a product.
Write the customer's job without naming your product.
Write one possible difficulty and one desired gain. Mark both evidence or assumption.
List one feature of your offer and translate it into a possible customer benefit. Add a question mark if the benefit has not been verified.
Complete the four-piece sentence above. Read it aloud. Remove claims you could not explain or deliver.
Choose at most two of the six Cs that matter now. Write one practical improvement for each.
Write one question to ask a potential customer and one check of your own delivery process.
A useful answer for Maya would mention nearby workers, short breaks, preordered lunches and stated collection times. It would label the audience and benefit as assumptions, show a simple way to confirm available slots and ask what information workers need before trying it. It would not invent a “most popular” lunch, a proven time saving or customer feedback.
Common mistakes and a short check
Talking only about features. “AI-powered” or “online form” may matter to the business owner, but the customer needs to know what improves for them.
Promising more than operations can deliver. The clearest sentence in the world will damage confidence if available items, timings or support do not match it. Test the service as well as the wording.
Trying to appeal to everybody. A narrow first audience makes it easier to learn. You can serve others later; the initial promise should be understandable to the people it names.
Calling an untested difference unique. Comparison claims need current evidence. You can say what your service does without claiming nobody else does it.
Check your understanding: “Order through an online form” and “See a collection time before ordering” describe different things. Which is the customer-facing benefit? Suggested answer: seeing the time may help the person plan; the online form is one possible feature enabling that. Whether the benefit matters to this audience remains to be tested.
Optional watching
Beginner writing example:How To Create a Value Proposition (Beginners), HubSpot Marketing. Its description walks through a customer problem, benefits and differentiation. HubSpot is a commercial software provider; any performance claim needs separate evidence.
Framework creator's explanation:Strategyzer's Value Proposition Canvas Explained, Strategyzer. It introduces the customer jobs, pains and gains tool. A framework-owner video explains the method; it does not independently prove that the method guarantees sales.
These are provisional picks from original-page metadata and descriptions checked 27 September 2026. Full content, verified duration, English captions and UK playback remain to check before publication. The written lesson and exercise work without either video.
A beginner-friendly route through 26 short lessons on customers, offers, channels, content and measurement. Start anywhere, with no account or paid tools.