From feature list to story: rewriting a SaaS homepage

A walkthrough of how I turn a wall of features into a page that answers one question: why should I care?

Most software homepages I review open with a grid of features. Twelve icons, twelve labels, no story. The visitor has to do the work of figuring out whether any of it matters to them.

The rewrite, step by step

  • Start with the customer’s situation in one sentence — their words, not ours.
  • Show the outcome before the mechanism: what changes after they switch.
  • Group features by the job they do, and cut anything that doesn’t serve a job.
  • End with the smallest possible next step: a demo, a call, a PDF.

The features don’t disappear. They move below the story, where they answer the questions the story raised.

Join the conversation

Your email address will not be published. Required fields are marked *