You wrote four paragraphs about your product. They are good paragraphs. The fourth one has the best line on the page, the one about cutting onboarding time in half. Nobody has ever seen it.
This is not a comment on your writing. It is a comment on how people use the web. They do not read a landing page. They scan it, the way you scan a menu when the server is already standing there.
What scanning actually looks like
Eye tracking research has said the same thing for about twenty years. People read the headline. They read the first few words of the next line or two. Then their eyes slide down the left edge of the page, catching on anything big, bold, or shaped like a number.
On a phone it is more brutal. A five line paragraph on your monitor is a twelve line slab on a small screen. The thumb is moving before the brain decides if the slab is worth it. The slab loses.
So the working assumption for every section should be this: the visitor reads the heading, maybe one line under it, and nothing else. If the page still makes sense under that assumption, you are fine. If the page only works when someone reads everything in order, you have written an essay, and the back button is right there.
The skim test
Open your page. Read only the headings, top to bottom, out loud. Skip everything else.
If what you just said sounds like a pitch, good. Something like: cut invoice chasing to zero, connects to your accounting tool in two minutes, used by 900 agencies, free for the first 50 invoices. A person could buy from that.
If what you said was Features, How it works, Why us, Testimonials, you have labels, not claims. Labels tell the visitor what kind of content sits below. Claims tell them why to care. Scanners only get the headings, so the headings have to carry the argument.
Claim plus two lines
The structure we push in almost every roast: each section gets one claim as the heading, then at most two lines of support. Not two paragraphs. Two lines.
- The claim is a full thought with an outcome in it. Not Reporting. Try: See which campaign paid for itself by Friday.
- Line one says how. The mechanism, in plain words.
- Line two gives the proof or the detail that makes it believable. A number, a name, a limit.
- Anything that does not fit goes to a docs page, a FAQ, or the bin.
Our platform was designed from the ground up with collaboration in mind. Teams of all sizes can work together across projects, leaving comments, assigning tasks, and tracking progress in real time, which means fewer meetings and less time lost to status updates, so everyone can focus on the work that matters most to the business.
Kill the Monday status meeting. Everyone sees who is doing what, live, on one board. Teams on Relay cut recurring meetings by a third in the first month.
Same section. The second version is half the length, and the visitor gets the point from the first five words. In the first version the point sits in a clause near the end, which is another way of saying it is nowhere.
Proof goes next to the ask
The other casualty of the long page is proof. Most pages stack it in one place: a logo strip near the top, a testimonial block near the bottom. Then the signup button sits alone, with nothing near it to answer the question in the visitor's head: is this going to waste my time?
Doubt peaks at the moment of the click. So that is where proof should live. Directly beside or under the CTA, put one small, specific thing. One, not all three:
- A number with a unit. 4,200 teams. 11 minute average setup.
- One short quote from a named person with a real job title.
- A risk remover. No card. Cancel in two clicks. Export your data any time.
What to do with the good stuff in paragraph four
Promote it. If your best line is buried, it is not a supporting detail, it is a heading that got lost. Go through your long paragraphs and pull out every sentence that contains a number, a named customer, or a concrete outcome. Those are your claims. The sentences around them were scaffolding.
If a sentence would survive as a heading, make it one. If it would not, ask why it is on the page.
You will end up with a page that is shorter, louder, and a little uncomfortable, because there is nowhere to hide. Good. A scanner can now get your whole argument in the eight seconds they were going to give you anyway.
Paragraph four had a good run. Nobody was there to see it.