This is how we approach a restructure when the problem is not the design but the order of information. The pattern is common in B2B SaaS: a site that grew page by page, where every team added what it needed and nobody owned the buyer's path through it.
The usual symptoms: sales calls start with basic questions the site should have answered, the navigation mirrors the org chart, and the same feature is explained three different ways on three different pages.
We start with sales, not the sitemap. We listen to recorded calls, read support tickets and ask the sales team which questions they answer every week. The list is usually shorter than expected, around fifteen to twenty questions.
Each question gets a home. Early questions (what is it, who is it for) belong on the homepage. Evaluation questions (does it integrate, how long is setup) go on product and integration pages. Late questions (security, contracts, pricing) go where buyers look right before they talk to sales.
The sitemap should follow the order buyers ask questions, not the order the company was built.
Pages that answer no buyer question get merged or removed. This is usually the hardest step for the client and the one with the biggest effect. Fewer pages means fewer dead ends and a clearer path to a demo.
We track demo requests by entry page, the questions raised on first calls and how far visitors get through the core pages. If sales stops hearing the basic questions, the restructure worked.
We review your homepage and key pages and send back a prioritised list of fixes.