How to write a product headline that names the reader
A headline pattern that says who the product is for, what it is, and what changes — without a clickbait clause.
What should a product headline say?
Name the reader, the product, and the job in one line. A stranger who only sees the headline should know whether the page is for them. Cleverness that hides any of those three is a headline you still have to explain.
The reader is the first noun that matters
“Introducing Fieldnote” is a headline about the company. “A morning brief for support leads” is a headline about a person. The second one can be scanned in a list. The first one asks the reader to care before they know why.
Put the reader where the eye lands: the start of the line, or immediately after the product name. Support leads, billing managers, solo editors — a role is enough. “Teams” is only enough if you then say which teams. A role without a job is still a category.
Say the job in verbs a person does
“Platform,” “solution,” and “suite” do not describe a Tuesday. “See which tickets slipped overnight” does. If the headline cannot hold a verb, the deck under it will have to, and many readers never reach the deck.
One job. A headline that promises a brief, a CRM, and a status page is three products. Pick the job that makes someone open the page. The other jobs can live in the story, after the reader has agreed the first one is theirs.
The product name is identification, not the pitch
People who already know the name need it in the headline so they can find the page again. People who do not know the name need the job beside it so the name means something. “Fieldnote — a morning brief for support leads” does both.
Do not make the name do the describing. If the name is a pun, the headline still needs the job in ordinary words. A pun plus “reimagined” is two ways of not saying what the product does.
Cut the words that fit any product
Ultimate, seamless, powerful, next-gen, all-in-one. Any competitor can claim them. They also cost characters you needed for the reader and the job. A headline bench should flag them the way a copy editor would.
Also cut “you won’t believe” and “the secret.” Those phrases tell a reader the page is hiding the point. On a product story the point is the product. Hiding it is the opposite of a hed.
Length is a constraint, not a style
A line that runs past about 70 characters will be cut in a sidebar, a pin, and many search snippets. That is not a law of prose. It is a reason to put the reader and the job before the clause you can lose.
If you need a second beat — a limit, a contrast — use a deck, not a longer headline. “Without a Monday meeting” can live under the line. The headline stays the part a person can repeat.
Test it the way a list tests it
Read the headline next to four others, with no logo and no paragraph. If you cannot tell who it is for, it is not finished. If you can tell, and you would not be embarrassed to have the wrong reader skip it, it is doing its job.
Hed Press stories open on that line. The paragraph after it should confirm the headline, not replace it. If the first paragraph has to correct the headline, rewrite the headline. The hed is the promise the page has to keep.
Questions
Should a headline ask a question?
Only when the page answers it in the next line with a product and a person. “Tired of messy handoffs?” is not a headline yet. It is a pause.
Where does the product name go?
First, or right after a short label, with the job in the same line. A name alone is an identifier. A job alone is a category. You want both.
How many adjectives are too many?
One, if it is specific. Zero is often better. “Fast” needs a comparison. “Before standup” is more useful than “fast.”
Can the same headline work as the page title?
Yes. A headline that only works inside a designed card will fail in a search result, a pin, and a category list. Write the line that survives those cuts.