← Insights

Guide · 3 min read

The Five-Line Homepage Test: Category, ICP, Pain, Proof, Alternative

Vantrow · Jul 6, 2026

Quick answer

A homepage should state five things a stranger can repeat back: your category (what kind of thing it is), your ICP (who it's for), the pain you remove, the proof you can be believed, and the alternative you replace. Miss one and the reader guesses — or leaves.

What should a homepage actually say?

A homepage should state five things a stranger can repeat back in ten seconds: your category (what kind of thing this is), your ICP (who it's for), the pain you remove, the proof you can be believed, and the alternative you replace. Miss one and the reader guesses — or leaves.

Most operator sites fail this quietly. They read fluent and say nothing. Below is the test, line by line, with what "good" looks like for a firm that sells to other operators.

Does your homepage name a category?

Your first job is to place the product in a mental shelf. Category is the noun a reader files you under — "governed intake software," not "a platform." Without it, every other claim floats. According to the Nielsen Norman Group, users leave a page within 10–20 seconds unless it communicates value fast; a missing category burns that window.

  • Weak: "The operating system for modern teams."
  • Better: "Case-intake software for law firms."

Pick a noun your buyer already uses. If you invented the category, anchor it to a familiar one first, then differentiate.

Does it name the ICP — and only the ICP?

ICP — ideal customer profile — is the specific operator you serve: a 12-attorney firm, a CRE shop with four analysts, a regional accounting practice. Naming them narrows the room, and narrowing is the point. A page that speaks to "businesses" speaks to no one.

  • Name the role and the firm type in the first screen.
  • Reflect their words back: "chasing intake forms," not "workflow inefficiency."
  • Let unqualified visitors self-select out. That's a feature.

When the reader thinks "that's me," the rest of the page gets the benefit of the doubt.

Does it state the pain in the reader's words?

State the pain — the concrete, recurring problem — the way the operator would say it out loud. Owners don't talk about "operational friction." They talk about paperwork that piles up, follow-ups that slip, invoices that go out late. Match that register exactly.

Good pain lines are specific and testable:

  1. "Intake forms sit in inboxes for days."
  2. "Nobody knows which follow-up got sent."
  3. "Month-end close eats a full week."

If your pain line could belong to any vendor in any market, it isn't pain — it's filler. Cut it.

What counts as proof on a homepage?

Proof is evidence a skeptic accepts: named customers, real numbers with sources, a specific result, an audit trail. Vague reassurance ("trusted by teams everywhere") is not proof. According to Nielsen Norman Group research on trust, users discount generic claims and weight concrete, verifiable detail far more heavily.

  • Name the firm, or describe it specifically enough to be credible.
  • Use one real number, sourced, over three rounded ones.
  • Show the mechanism: what the software does, and where a human approves it.

This is where Vantrow's spine — propose, never commit: the software stages an action, a human approves it, and everything lands on an audit trail — becomes proof, not slogan. Governed beats magical when a buyer is deciding whether to trust you.

Does it name the alternative you replace?

Every buyer already solves this problem somehow — a spreadsheet, an assistant, a legacy tool, doing nothing. Name that alternative so the reader can locate you against it. Positioning without a reference point is just adjectives.

  • "Instead of a shared spreadsheet nobody trusts."
  • "Instead of an autonomous agent you can't audit."
  • "Instead of hiring a third coordinator."

Naming the alternative also frames your price. A reader who knows what you replace can judge whether the trade is worth it — which is the decision you actually want them making.

How to run the test in ten minutes

Read your homepage's first screen aloud and answer five questions. If any answer is "unclear," that's the line to fix first.

  1. Category: What kind of thing is this?
  2. ICP: Who, exactly, is it for?
  3. Pain: What specific problem does it remove?
  4. Proof: Why should I believe you?
  5. Alternative: What am I using instead today?

Hand the page to someone outside your company. If they can repeat all five back, the page works. If they hesitate on one, you found your rewrite — no redesign required.

FAQ

See structured Q&As below.

Put this thinking to work at your firm.

This is how we build governed software. The fastest way to test it is your own work — bring one workflow, and we'll map the first useful build.