01
Start with the reader's reporting job
Begin by naming who reads the page and what they must produce. A sales manager preparing a weekly review needs different features from an analyst exploring raw data. Write one sentence describing the job, such as showing pipeline movement to a leadership group each Monday. Then list only the features that serve that job. Leave out settings and integrations that do not change the outcome. A reader should finish the opening paragraph knowing whether the tool addresses their situation, and what they could produce within their first hour of use.
02
Show each feature as input, view and result
For every feature, describe what the user puts in, what they see, and what they can do next. For a chart builder, the input is a table of deals, the view is a stacked bar by stage, and the result is a shareable snapshot with notes. This structure keeps the page concrete and prevents vague language such as powerful insights. Use a consistent order so readers can compare features quickly. Add a small caption beneath each example explaining what question the view answers, so non-specialists understand the purpose of the visual.
03
Worked example and a clear next step
Imagine a small online shop with a monthly sales file. The overview shows import, a revenue trend line, a product ranking and a comment layer for the owner. Each feature gets two sentences and one labeled example. The page then ends with a single action, such as opening a sample dashboard built from fictional data. Before publishing, check every statement against what the product actually does, and mark planned features as planned. Review wording with a real user, asking which section they would skip and which question remains unanswered.