Positioning statements die in the first landing page test

Most positioning statements are never tested. They’re workshopped, approved in a slide, and shipped straight to the homepage — where the first real test is a stranger deciding, in four seconds, whether to keep reading.

What a positioning statement actually has to survive

Every positioning statement lives two lives. The first is internal: the sentence a team argues over until everyone can sign it. It has to be precise enough to settle arguments about what to build, who to sell to and what to turn down. That version is allowed to be long, because it’s read by people who already know the category, the competitors and the story of the last three pivots.

The second life starts the day the sentence reaches the homepage. There, it has to be compressed into something a stranger can carry away after one read. No context, no deck, no founder in the room to explain what was meant. Whatever the visitor repeats to a colleague afterward is the positioning now, whether or not it matches the slide.

Most statements are only ever tested in the first life. Workshops check that the sentence is true and that everyone agrees with it. Nobody checks whether it survives compression. That’s why the landing page is the real test — not because the page is special, but because it’s the first place the sentence meets someone with no reason to be generous.

What Vela Systems’ first version got wrong

Vela Systems’ first statement was accurate. It described a scheduling and dispatch platform for field service operations, named the kinds of jobs it handled and listed the tools it connected to. Internally, nobody could fault a word of it.

The problem was the reader it assumed. It took for granted that a first-time visitor already knew what field service software was, what dispatch meant in that context and why schedules break. The people Vela actually needed — operations leads at mid-sized service companies — often didn’t use that vocabulary at all. They had technicians arriving late and jobs booked twice. They didn’t have a category name for the fix.

So the statement read as jargon. Session recordings showed visitors skimming past the headline toward the first screenshot, as if looking for the explanation the sentence hadn’t given them. The words were correct. They just described the product in the language of people who already owned it.

The fix wasn’t a simpler product description. It was a different starting point. Instead of opening with what Vela was, the rewrite opened with what an operations lead was already trying to stop: the late arrival, the double booking, the Monday spent re-planning the week by phone. The category name moved down a line, where it confirmed what the reader had already understood instead of standing between them and it.

If a sentence needs a glossary, it was written for the people who already understood it.

The test to run before you ship it

Catching this doesn’t take a research budget. It takes three questions, asked of someone outside the company, before the sentence goes live:

• Would a stranger repeat it back correctly? Read it to someone who doesn’t work in your category, then ask what you do. If their answer needs correcting, so does the sentence.

• Does it say who it isn’t for? A statement that could describe anyone gives a visitor no reason to recognize themselves in it.

• Does the first sentence work without scrolling? If the meaning depends on the paragraph, the screenshot or the video below it, the headline isn’t doing its job yet.

Run it on three or four people, not one, and write down exactly what each of them says back. The gaps between their answers are the parts of the sentence doing no work. If two people describe you as a different kind of company, you haven’t positioned yourself yet — you’ve described yourself.

Vela’s rewrite passed all three by doing less. It named the problem the way an operations lead would describe it in their own words, and left the category label for the second line, where it could be read as confirmation instead of a barrier.

Test the sentence the way you’d test the page: with someone who has never seen either.