Product pages

The test for a product page is short: could this page describe three of your competitors? If it could, it describes none of them, and the reader has learned only that your category exists.

Most product pages fail this because they lead with benefits. Benefits are the easiest thing to write and the least differentiating, because every product in a category promises the same outcomes — the whole reason they are in the same category.

The operational shape

Trigger. A capability ships, or the positioning behind one changes. The second is easy to miss: the product did not move, but what it is for did.

Reads. How the product works and its limits, from product. Positioning and the unique attributes, from decisions. Cleared numbers, from proof.

Cadence. Per capability, maintained.

Gate. Approve before publish, and the strictest treatment applies to any sentence containing a number or a competitor.

What good looks like

It leads with the mechanism. How the thing actually works, in three or four sentences a reader could repeat back. A benefit is only believable once someone understands what produces it, and the mechanism is the part a competitor cannot copy into their own page by Friday.

It survives being read aloud to someone who has not seen a demo. That is the practical test. Product pages are usually written by people who know the product too well to notice how much the page assumes.

It names what people consistently misunderstand. Every product has one — the thing prospects reliably get wrong on the first call. A page that fixes it up front saves the call, and a page that does not is why the call exists.

It says what the product does not do. Written as decisions rather than apologies. A limit with a reason behind it can be discussed in a deal; a limit without one gets dodged, and the dodge is what a buyer remembers.

Every claim has an owner. A product page is where roadmap quietly becomes present tense. The discipline is mechanical: if something is not shipped, it does not appear in the present tense, and if a number is not cleared, it does not appear at all.

When it goes stale

This is the most commonly broken page on any website, because it is the page furthest from the people who change the product.

Four triggers. The capability changed and the page describes the old behavior. The positioning moved, so the page is accurate and pointed at the wrong buyer — the harder failure to see, because nothing on the page is false. A roadmap item shipped, and the page still hedges about something that now exists. A limit was lifted, and the page still names it, which costs deals silently.

The signal worth watching is not traffic. It is a sales team that has stopped sending the page.

What it feeds

• Sales decks and proposals — the same mechanism, arranged for a conversation
• Comparison pages — the architecture claims a comparison rests on
• Onboarding and in-product copy — the promise a new customer arrives expecting

The dependency runs upward: a product page cannot say more than the product file supports. When a page needs a claim that nothing owns, the gap is in the brain and not in the writing.