Does your product page answer the buyer's question in the first 100 words?
Usually not. Most product pages open with a tagline, a hero image, and a positioning line — then make the buyer scroll to learn what the thing does, who it's for, and what it costs. An answer-first page states the job it does, the buyer it serves, and the outcome in its opening lines, before any persuasion.
Here's the test. Open your own product page. Cover everything below the fold. Can a stranger — or an answer engine — tell what you sell, who it's for, and why it beats the alternative from what's left? If not, the page is working against you.
What is "answer-first" and why does it matter now?
Answer-first means the page leads with a direct answer to the buyer's real question — "what is this and will it solve my problem?" — in plain language, in the first 100 words. Everything else supports that answer. It matters because the reader decides fast, and now a machine reads first.
Two things changed:
- Buyers skim. Operators evaluating software give a page seconds, not minutes. According to Nielsen Norman Group's long-running eye-tracking work, people read a fraction of the words on a typical page and scan in an F-shaped pattern — the top and left get read, the rest gets skipped.
- Answer engines quote. Buyers increasingly ask an AI assistant "what's the best X for a firm like mine?" The engine pulls a sentence or two from pages that state their answer plainly. A page that hides the answer in paragraph four rarely gets cited.
If the first 100 words don't answer the question, you're relying on a scroll that most people never make.
What question is the buyer actually asking?
The buyer is an owner or operator, not a browser. They arrived with a specific problem and one question: will this do the job I need done, for a firm like mine, without creating new risk? Your first 100 words should answer that — not describe your company's mission.
Break the question into its parts and answer each near the top:
- What is it? One sentence, no metaphors. "Vantrow is governed software that stages actions for your team to approve."
- Who is it for? Name the buyer. "For CRE firms, law firms, and accounting shops that run on paperwork and follow-ups."
- What job does it do? The concrete outcome, not the category. "It drafts the intake, the follow-up, the invoice — and waits for a human to send it."
- Why this over the alternative? The defensible difference. For us: propose, never commit — the system stages, a person approves, everything lands on an audit trail.
A buyer who reads those four answers knows whether to keep reading. That's the point. A page that makes them dig for it is asking for work most won't do.
How do you rewrite the first 100 words?
Lead with the answer, then earn attention with proof. Cut the throat-clearing — the "we believe" preamble, the abstract tagline, the hero line that could belong to any company. Replace it with a plain-English capsule: what it is, who it's for, the job, the difference. Positioning comes after the answer, not instead of it.
A workable pattern for the opening block:
- Line 1 — the answer. What the product is and the job it does, in one sentence.
- Line 2 — the buyer. Who it's for, named specifically.
- Line 3 — the difference. The one defensible reason to choose it.
- Line 4 — the proof or next step. A named number, a customer, or a clear action.
Then keep the rest of the page scannable: question-shaped headings, short paragraphs, one idea per section. The goal isn't fewer words overall — it's putting the answer where the reader and the engine both look first.
What does an answer-first opening look like?
Before: "In a world of disconnected tools, [Product] brings your workflows together so your team can do their best work. Built by operators, for operators."
That answers nothing. It names no buyer, no job, no difference.
After: "[Product] is governed software that drafts your firm's routine paperwork — intake, follow-ups, invoices — and stages each one for a human to approve. Built for CRE, legal, and accounting firms that can't afford a wrong send. The system proposes; your team commits; every action lands on an audit trail."
Same product. The second version answers the buyer's question and gives an answer engine something exact to quote. That's the whole difference.