Context
We record the current state, objective, constraints, access and the definition of done.
Scope
I separate the required release from optional work and identify dependencies before changes begin.
Implementation
Work happens locally or on staging, with a practical way to compare and roll back risky changes.
When is this service useful?
A redesign is justified when visual and structural problems block users and a series of cosmetic patches no longer addresses the cause.
- The offer changed but navigation and pages still reflect the old business model.
- The mobile experience is difficult, important actions are hidden and components behave inconsistently.
- The site is hard to maintain, but its useful content and URLs must be preserved.
What is included?
Audit first
I record pages, content, conversion journeys, analytics and technical constraints before designing.
New structure
I change hierarchy only where it helps users and avoids duplicate search intent.
Design system
I update components and responsive states as a system rather than a collection of unrelated screens.
Migration plan
I prepare old-to-new URL mapping, redirects, canonicals, sitemap updates and post-launch checks.
How the work proceeds
- Context. We record the current state, objective, constraints, access and the definition of done.
- Scope. I separate the required release from optional work and identify dependencies before changes begin.
- Implementation. Work happens locally or on staging, with a practical way to compare and roll back risky changes.
- Verification. I test priority pages, mobile widths, links and the complete user journey that the work affects.
What is controlled before release?
- Removing pages without analysis can discard search demand and external links.
- The new interface must preserve working forms, analytics events and important content.
- Launch should use a checklist and a practical rollback route for critical errors.
Relevant real projects
Only real Montana WebStudio portfolio projects are referenced — no invented case studies or performance claims.
Frequently asked questions
Do I have to change the CMS?
No. If the current platform supports the requirements, the redesign can stay on it.
Will Google rankings be preserved?
Rankings cannot be guaranteed, but preserving URLs, content, redirects and technical checks reduces controllable risk.
Can the redesign be released in phases?
Yes, when the design system and dependencies allow phased releases without two incompatible navigation models.
Does the website need a redesign?
Send the URL and main problems so we can first identify what should stay and what genuinely needs to change.