How to write the first paragraph of a product story
A practical way to open a product story so a reader knows what it is, who it is for, and why it is on the page before they scroll.
What should the first paragraph of a product story do?
Name the product, say what it does, and say who it is for — in that order, in plain sentences. A reader who stops after the first paragraph should still be able to explain the product to someone else. The rest of the page can add proof, limits, and a place to explore it.
Start with a person, not a category
Most product openings fail because they start with a market. “In the crowded world of team chat” tells a reader nothing they can use. The person who landed on the page already knows the category exists. They came to find out whether this particular product is for them.
Write the first sentence as if you were introducing the product to one colleague. “Fieldnote is a daily log for support leads who need yesterday’s incidents in one place before standup.” That sentence has a name, a job, and a person. It is enough to keep reading or to leave. Both outcomes are useful.
Put the job before the feature list
Features are how a product works. The job is why someone would open it on a Tuesday. A first paragraph that lists “AI summaries, Slack integration, and custom roles” is a settings page written as prose. A first paragraph that says the support lead can see which tickets slipped overnight is a story.
You can name one mechanism if it is the reason the job gets done. “It pulls the last 24 hours from the help desk and writes a six-line brief.” That is a feature in service of the job. Three more features can wait for a later section, where a reader who already cares will look for them.
Say who it is not for
A useful opening draws a boundary. If Fieldnote is built for a support lead with a queue, it is a poor fit for a founder who wants a public changelog. Saying that in the first paragraph saves the wrong reader and makes the right reader trust the page.
The boundary should be specific. “Not for everyone” is a slogan. “Not for teams that already live in a single inbox and do not need a morning brief” is a decision. Readers who recognize themselves in the exclusion will often recognize themselves in the fit, too.
Keep the opening short enough to remember
Forty to eighty words is a workable budget for the first paragraph of a product story on a daily edition. That is long enough for a name, a job, a person, and a limit. It is short enough that a reader can repeat it. If the opening needs a second paragraph to become clear, the first paragraph is still doing too many jobs.
Read it aloud. If you run out of breath, cut a clause. If you cannot remember the product’s job after you look away, the sentence is decorating the product instead of introducing it. The Lede grader on this site counts the words and flags openings that stall on “we” or on filler.
One link, after the reader knows what it is
The product link belongs in a sentence the reader already understands. “Support leads can open Fieldnote and read the brief before standup” is a sentence that can carry the link. “Click here” is not. The link is how a reader explores the product. It is not a substitute for the introduction.
Do not put a second URL in the opening. A pricing page, a docs page, and a Twitter profile in the first paragraph turn the story into a directory row with extra words. One destination is enough until the reader has decided the product is relevant.
What to cut from a draft opening
Cut the launch date unless the date is the story. Cut the funding round. Cut “excited to announce.” Cut adjectives that a competitor could paste onto their own page: powerful, seamless, next-generation. None of those help a reader decide.
Keep any concrete noun you would be willing to be wrong about: the person, the hour of the day they use it, the object they stop using. Those details are what make a product story different from a tagline. A daily edition is a stack of those stories. The opening is the only part many readers will give you.
Questions
How long should the first paragraph be?
Aim for 40 to 80 words. Long enough to name the product, the job, and the person. Short enough to repeat from memory.
Should the product name be in the first sentence?
Yes. A reader who arrives from a homepage index needs the name immediately. Burying it after a scene-setting clause makes the page harder to scan and harder to cite.
Can the opening be a question?
Only if the next sentence answers it with the product’s name and job. A question alone is a stall. “Tired of messy handoffs?” does not tell anyone what the product is.
Where should the product link go?
In a sentence that already says what the reader will find. One link in the opening is enough. Other URLs can wait until a later section, or they can stay off the page.