Positioning Statement

Unless it's written down, the language for describing a product splits by department. Whoever writes the landing page leads with the strength they know best, sales uses the phrase a customer reacted to yesterday, and whoever writes the job posting picks something else again. Nobody said anything false; there was simply no standard. The cost lands on the listener, who has to reconcile three products out of one.

Pagedeck was in that state. The first line of Ravi's landing page said fast document editor, the cover of Sofia's proposal deck said team knowledge platform, and Mia's requirements document called it a collaborative document tool. The three phrases point at the same product, and what a listener pictures from each is different.

The day Grace described the same product three different ways in an investor meeting, they decided to write the sentence. A positioning statement is that standard. Pin down in one sentence who the product is for and what it should be seen as, and every phrase that goes outward starts from there.

Five fields fit inside one sentence. Leave one out and readers fill that space with an assumption.

1. The target — who the product is for, written narrowly. "Everyone who writes documents" produces no phrasing at all; "someone at a 10-to-50-person company who exchanges documents across several departments" produces phrasing.
2. The category — which shelf in the customer's head this lands on. Pick a term already in use rather than inventing one. Say collaborative document tool and a customer can guess what to compare it against; say knowledge operations system and they have to find the comparison themselves, which most people won't do.
3. The problem solved — the discomfort that target lives with now, written as something observed. Not "documents are scattered," but "the same content sits in three places and someone checks which one is current every time."
4. The differentiator — what separates this from the other options in the same category. Exactly one. List two or more and the reader has to choose which to remember, and usually remembers neither. Picking the one is most of the work of writing this sentence.
5. The evidence — the reason to believe the differentiator. A capability, a number, or a structural fact. A differentiator with no evidence is an advertising line; with evidence it becomes something sales can say in the room.

Joined up, the five become one sentence: for someone at a 10-to-50-person company who exchanges documents across several departments, Pagedeck is the one collaborative document tool where a team can confirm together whether each document is current, because every document carries an owner and a review interval. The sentence running long is normal. It isn't written to be read; it's written to judge with. Compression comes later, in the copy drawn from it.

Not one person's document. Marketing, product, and leadership settle it in one room, because each knows something different. Marketing knows which language earns a reaction outside, product knows what can actually be built, and leadership picks which market to go after. Write it with one side absent and it gets rewritten next quarter, usually by whoever was missing from the room.

Four groups read it.

1. Whoever writes outward-facing copy starts here. The value proposition comes out of it, and individual lines hang under that. A value proposition compresses the reason to choose the product, and unlike this sentence it's shown to customers directly.
2. Sales uses it to introduce the product in one line at a first meeting. With category and differentiator settled, the conversation holds even when the customer starts comparing alternatives mid-meeting.
3. Whoever decides the product uses it as a test. Ask whether a proposed feature strengthens this sentence's differentiator, and push it back when it doesn't. The answer is usually clearer than the debate that preceded it.
4. Whoever hires ends up using the same language in postings and interviews. New joiners seeing the same sentence from day one is a side effect worth having, and it costs nothing extra.

It isn't a document that goes outward. Put it on a landing page as written and it's long and stiff enough that nobody reads it. What goes outward is the messaging drawn from it — the system of core phrases that describe the product — and once the phrases multiply, a messaging house organizes them so it's visible which phrase rests on which evidence.

"Before we edit the landing copy, let's settle the positioning statement. Three of us are using different words."

Fix the standard sentence rather than each phrase separately.

"The target says everyone who writes documents. Nothing usable comes out of that."

The target field is wide enough to filter nothing.

"That feature has nothing to do with our differentiator. Push it to next quarter."

Using the sentence as a test for product priority.

Three people at Pagedeck spent half a day writing it. The field they argued over longest was the category: Ravi wanted knowledge management and Sofia pushed for collaborative document tool. They checked what customers actually type into a search box and went with the latter.

Over the following month, the landing page's first line, the proposal cover, and the job posting came to use the same category name. The differentiator field changed twice. The sentence isn't a fixed conclusion — it's the place where each change leaves its reasoning behind.

The most common reading is that this is a slogan. Being asked to describe a product in one sentence calls an advertising line to mind. But a slogan is short and built to be remembered, and this sentence is long and built to be judged against. Treated as a slogan, the target and the evidence drop out first, and what's left reads fine attached to any product. At that point a proposed feature can't be tested against it, and the sentence has stopped doing the only job it had.

The other common belief is that it has to hold every customer. Narrowing the target feels like discarding market. But a wide target produces no phrasing. A ten-person company and a thousand-person company have different problems, and putting both in one sentence yields language that reaches neither. Copy built from a narrow sentence selling to customers outside that category is common; copy built from a wide sentence selling to nobody is more common.