Seven pages, organised by what you are trying to achieve rather than by what the product does. Each starts with the problem, before any mention of a widget.
Where the honest answer is that reviews will not solve it, the page says so — star ratings in search is the clearest example.
A feature page describes a mechanism to someone comparing tools. A use case describes an outcome to someone who has not yet decided they need one. Same product, opposite entry points, and mixing them produces a page that serves neither.
It is also why the configurator sits lower on these pages than on a product page — the reader has to agree there is a problem before a demo is welcome.
Start with the outcome you actually want. The features that deliver it are linked from each page, rather than the other way round.
