Web page redesign plan before any edits

You are a product designer planning a page redesign. Do not produce final code or copy yet; produce a plan I can approve. Inputs: - Page purpose and main action you want visitors to take: {{page_goal}} - Audience: {{audience}} - Current page content or description (paste text, or describe sections in order): {{current_page}} - Constraints (brand rules, tools, things that must not change): {{constraints}} Steps: 1. Read the current page as a first-time visitor and note what you would do and where you would hesitate. 2. Name the problems in order of impact. Tie each to evidence from the content provided, not to general taste. 3. If brand, style or the goal of the page is unclear, ask at most 3 clarifying questions before the plan. Otherwise proceed with stated assumptions. 4. Propose the new structure. Output format: - Current-state audit: a table with issue, where it appears, why it hurts, severity (high, medium, low). - Proposed page structure: sections in order, the job of each section, and what visitors should feel or decide there. - Section notes: content to keep, change or remove; visual hierarchy; one primary and at most one secondary call to action. - Trust and proof: what evidence to show (reviews, numbers, guarantees) that I must supply, never invented. - Mobile considerations. - Risks and what to measure after launch. - Order of work: three steps from quick wins to larger changes. Quality bar: stay inside the constraints, keep one idea per section, do not invent testimonials or figures, and keep the plan under 700 words.

You are a product designer planning a page redesign. Do not produce final code or copy yet; produce a plan I can approve. Inputs: - Page purpose and main action you want visitors to take: {{page_goal}} - Audience: {{audience}} - Current page content or description (paste text, or describe sections in order): {{current_page}} - Constraints (brand rules, tools, things that must not change): {{constraints}} Steps: 1. Read the current page as a first-time visitor and note what you would do and where you would hesitate. 2. Name the problems in order of impact. Tie each to evidence from the content provided, not to general taste. 3. If brand, style or the goal of the page is unclear, ask at most 3 clarifying questions before the plan. Otherwise proceed with stated assumptions. 4. Propose the new structure. Output format: - Current-state audit: a table with issue, where it appears, why it hurts, severity (high, medium, low). - Proposed page structure: sections in order, the job of each section, and what visitors should feel or decide there. - Section notes: content to keep, change or remove; visual hierarchy; one primary and at most one secondary call to action. - Trust and proof: what evidence to show (reviews, numbers, guarantees) that I must supply, never invented. - Mobile considerations. - Risks and what to measure after launch. - Order of work: three steps from quick wins to larger changes. Quality bar: stay inside the constraints, keep one idea per section, do not invent testimonials or figures, and keep the plan under 700 words.

Audit (excerpt): | Issue | Where | Why it hurts | Severity | | Three equal-weight buttons in the hero | Top section | Visitors cannot tell the main action | High | | Pricing hidden below testimonials | Section 5 | Buyers leave before seeing cost | High | Proposed structure: 1) Hero: one sentence on the outcome, one primary button (Book a demo). 2) Proof strip: 3 customer logos or quotes (you supply). 3) How it works in three steps ... Order of work: 1) Reduce hero to one action. 2) Move pricing up. 3) Rewrite section headings around outcomes.