Value Proposition

Product descriptions used to be feature lists. Put real-time collaboration, unlimited storage, and permission management on the first screen and the introduction was considered done. A reader gets through all three lines without learning what improves for them. Feature names are the builder's language; what the reader wants to know is how their day changes. Nothing in the list is untrue, and none of it answers the question being asked.

Sales conversations made it sharper. Twelve features explained over fifteen minutes, and then the customer asks what exactly gets better for their team. The reason that question stalls isn't an unprepared answer — it's that the answer differed depending on who inside the company you asked. The founder said cost savings, the engineer said speed, the designer said ease of use.

Several answers is the same as no answer. When the ad, the homepage, and the sales deck each make a different promise, the customer has no idea what to expect. A value proposition exists to fix that answer in one place, and once it's fixed it becomes the source every other piece of copy is cut from.

It packs whose problem, which problem, and what changes into one sentence. Five fields to fill.

1. Narrow the audience. "Teams" is not an audience. "The person responsible for internal documentation at a company of 20 to 100 people" is. Narrowing looks like it reduces reach; what it actually does is increase the number of people who read it as being about them.
2. State the problem in the customer's words. Viewing demand through the job a customer hires a product to finish is jobs to be done (JTBD), and writing this field needs that lens. "There's no search" is our language; "we held the same meeting twice because nobody could find last week's notes" is theirs.
3. State the outcome, not the feature. Not better search but the time spent finding a document dropping from twenty minutes a day to two.
4. Name what they're coping with today. The comparison is often not a competing product. A spreadsheet, or doing nothing, is the real rival, and the improvement has to be stated against that for a reader to find a reason to switch. Nobody abandons a spreadsheet because a product is good; they abandon it because staying costs more.
5. Attach one piece of evidence. A claim on its own reads as advertising. A customer count, one line from a real user, or a measured number will do.

Then test it. Show the sentence alone to ten prospective customers and ask them to say what the product does. If seven can't, rewrite. Putting two versions on the first screen and comparing sign-up rates works too.

Keep it under two sentences. Someone landing on a homepage decides whether to stay or leave inside about five seconds, so a sentence that doesn't land in that window doesn't land at all, however accurate it is.

One settled sentence becomes the source for several places at once. The large type on the first screen, the opening five minutes of a sales meeting, ad copy, the company blurb in a job posting, the first slide of an investor deck — all of them are this sentence shortened or expanded. Without a source, five places carry five different promises, which is the thing customers notice first and trust least.

It sits at the top when a messaging system gets built. A messaging house arranges the core message and its supporting evidence in the shape of a house; the value proposition goes in the roof and the evidence goes in the pillars underneath. An empty roof leaves three pillars pointing in different directions.

It also connects to what you charge. Pricing decides the number, and the justification is not cost but the size of what the customer stops losing. A product that gives back six hours a month makes the value of those six hours the logic behind the price.

Two audiences means two sentences. An individual user and an enterprise buyer have different problems, so merging them blurs both. The usual answers are splitting the homepage in two, or naming one audience as primary and giving the other its own page.

"There are three feature names in this sentence. Let's rewrite them as outcomes."

It's written in the builder's language and needs to move to the customer's.

"Our competitor isn't that product, it's a spreadsheet."

The comparison is aimed wrong, so the size of the improvement isn't landing.

"Only three of ten could say what the product does. Rewrite."

The test came back below the bar.

Pagedeck rewrote this sentence twice. The first version led with real-time collaboration and search, and three of ten people could say what the product was. Ravi went back through customer messages to find the problem-side sentence. The line that came up most was holding the same meeting twice for want of last week's notes.

The second version used that line directly. Sofia started opening sales meetings with it and Grace put it on the first slide of the investor deck, and once the same words were going out from three places, customers asked for clarification less often. Nothing about the product had changed between the two versions.

The most common mistake is treating this as the job of writing a good line. A short sentence with rhythm sticks, so that feels like the goal. But sticking and being understood are different things. Something like "work, flowing" fits anywhere without sounding wrong and identifies no company at all — show it to ten people and none of them can say what the product is. A slogan is what you get by shortening this sentence after it exists; reverse the order and you're choosing between sounds with no source to shorten. The order matters more than the craft.

The other frequent view is that once set, it's set. It states something fundamental about the company, so changing it often feels wrong. Not changing it casually is correct, but three conditions do force a rewrite: the primary audience shifting from individuals to companies, the real rival changing from a spreadsheet to another product, and what the product relieves changing outright. Keep the old sentence after one of those and a new audience won't read it as being about them. Teams in that position tend to spend a year adjusting channel copy instead.