Current pages and journeys
Map the pages and key visitor journeys that matter to the agreed project question.
Website Development
Make the next version count.
A redesign is more than a visual refresh. SHAMPAIN helps understand what your current site does, what visitors need, what to preserve and what to improve. Content, functionality, migration and launch responsibilities are scoped before build work begins.
Keep what works. Improve with intent.
Understand the current siteKeep useful contentPlan the migrationApprove before release
A considered redesign
Start with evidence about the current experience.
Define the business goal and review what already exists before deciding what should change. The available material and access determine the depth of the assessment.
Useful content and routes
Identify valuable information, page addresses and functions that need to remain available.
Structure and clarity
Plan a clearer way to explain the offer and guide visitors toward a relevant next action.
Design and functionality
Agree the visual direction, responsive behaviour and functions included in the new experience.
Content and dependencies
Plan content transfer, redirects and third-party connections where the project requires them.
Review before launch
Check agreed pages, links and behaviours against the brief; record open issues and responsibilities.
From current state to new release
Make change without losing sight of what matters.
The proposal names the included pages, content, migrations, dependencies, approval points and acceptance checks.
Understand
Agree the goal, audience, current site, available evidence and constraints.
Inventory
List the content, routes, functions and connections that need attention.
Scope
Set the new structure, platform, migration approach, responsibilities, fee and timing.
Review
Check the new experience and agreed migrated content before a production change.
Release
Deploy only after approval, with domain ownership and any rollback responsibilities agreed.
Clear expectations
Protect useful signals and ownership.
Migration and outcome decisions depend on the current site, platform and evidence available for the project.
Plan address changes
Review current URLs and agree redirects where needed. Search platforms decide how and when they update results.
Use available baselines
Record existing measures only where the owner provides suitable data and access. A redesign does not guarantee ranking or conversion gains.
Agree who operates it
Confirm domain, hosting, account access, ongoing maintenance and support responsibilities in the project scope.
If you want an initial view before implementation, consider the Growth Opportunity Review.
Start with the current site
What should stay, change or become easier?
Share your current website, audience and the main reason for a redesign. We’ll check fit, then agree the scope, migration responsibilities and commercial terms for review.