Redesign the whole website when its foundation blocks work your firm has already defined; repair or stage improvements when the constraint is contained. Everything after that sentence is evidence gathering.
The evidence is specific: which requirement the current site cannot meet, where that limit lives, and what each scope costs in review time, maintenance, and disruption. A dated look, the site's age, or a slow month of inquiries answers none of those questions on its own.
Key Takeaways
- Choose the scope from a demonstrated constraint, not from the site's age or the appeal of a fresh look.
- A contained problem on an editable site calls for a targeted repair before anything larger.
- Staged improvements fit when the existing foundation still supports the pages the firm needs.
- A rebuild earns its place when templates, architecture, or maintenance limits block required work.
- If page URLs will change, plan the mapping, redirects, and monitoring before approving the project.
Define the Constraint Before You Price the Fix
Every useful version of this decision starts with a business requirement stated in plain terms: the service pages should make fit obvious to the right prospect, the contact path should work on a phone, the team should publish and maintain content without a developer for every edit, or the firm needs page types the current setup cannot hold. Write the requirement down before anyone prices a solution.
Then separate observations from assumptions. "Inquiries slowed this quarter" is an observation. "The design is driving prospects away" is an assumption, and a quiet stretch has many possible causes: seasonality, referral mix, search visibility, message fit, or the site itself. Treating an assumption as a diagnosis is how a firm ends up buying the largest available fix for a problem it never located. The same discipline runs the other direction: a quiet stretch does not prove a recent change failed.
Different evidence answers different questions. Search visibility data covers exposure and clicks: how often pages appear in search results, for which queries, and whether searchers choose them. On-page behavior shows what visitors do after they arrive. Saved inquiries come closest to fit because they record what actual prospects asked for. No single source establishes that the people reaching the site are qualified prospects; treat that judgment as supported only when visibility, behavior, and inquiries line up, and provisional even then. Each source has limits: small samples swing, and traffic from your own team can inflate both visits and engagement. If that corroborated evidence says qualified prospects never reach the site at all, treat visibility as the working constraint; that points toward search work for financial advisors before any visual rebuild.
When a Targeted Repair Is Enough
A targeted repair fits when three conditions hold: the constraint sits inside one page or one path, the site can be edited without disproportionate effort, and the rest of the site does its job.
Picture a hypothetical firm whose service page leaves a visitor unsure whether the practice works with business owners, retirees, or both. Or one whose contact form is hard to finish on a phone. Both are contained problems. Rewriting one page, or rebuilding one path, addresses the demonstrated constraint, and the evidence so far has yet to justify replacing anything else.
Contained fixes often have focused guides. If the weak point is the inquiry path, our contact-page improvement guide covers that specific repair. Make the change, compare the next saved inquiries against the requirement you wrote down, and revisit the larger question if the evidence keeps pointing outward.
The honest comparison is scope against scope. A repair avoids re-reviewing pages that already work and keeps attention on the constraint. That is a scope argument, not a promise that the smaller project costs less or ships faster in every case; contained work still takes real review time.
When Staged Improvements Fit Better
Between a single repair and a rebuild sits the staged option: several related problems, one usable foundation. Staging fits when the structure, editing access, and templates can support the firm's requirements, yet more than one thing needs to change.
Group the work by dependency and reviewer. Messaging and service-page copy form one natural stage. Navigation and internal links form another. Template-level changes, such as a shared layout every service page inherits, form a third. Each stage should satisfy a written requirement, state what stays untouched, and name the person who maintains the result after the stage closes.
Staging spreads review effort across weeks the firm can absorb, and it creates honest decision points: after each stage, compare new evidence against the requirement list and continue, adjust, or stop.
When a Rebuild Earns Its Place
A rebuild becomes the serious candidate when the foundation blocks the requirements. The test is concrete and runs on the actual site: the shared template cannot support a page type the firm needs, the content architecture cannot hold the structure the firm has planned, or maintenance depends on a vendor arrangement that makes routine updates slow or risky.
When several of those limits stack, the repair path stops being the smaller one. Working around a blocking template page after page can consume more review time than replacing it once. Compare a scoped rebuild against the complete repair path on the terms the firm will feel: review hours, ongoing maintenance, transition effort, and what each option leaves behind for whoever owns the site next.
What stays out of this decision: a site-age rule, a universal cost crossover, a promised return, or a story about another firm's results. None survive contact with the requirement list. If the constraint is contained, rebuild talk is premature. If the foundation blocks defined needs, another round of repairs is delay dressed as thrift.
If URLs Change, Protect What Already Works
Any option that changes page URLs carries a continuity obligation. Before approving scope, inventory the pages that earn their keep: pages that rank, pages prospects mention, pages the firm references in its own materials. Assign one person to own their survival.
Google's site-move documentation is the right reference at the decision level. It recommends planning changes one after another instead of combining a domain move, a platform change, and a layout overhaul in a single step. When a move changes URLs, it calls for a mapping from current addresses to their new format, redirects from old to new, and monitoring of both.
The same guidance warns that significant site changes can bring ranking fluctuations while Google recrawls and reindexes. Treat it as a possibility to plan around, with monitoring and a calm review point, rather than grounds to promise preserved traffic. No honest scope carries a guaranteed recovery date.
Keep technical scores in their place as well. A strong performance report is one diagnostic input. Google notes there is more to page experience than Core Web Vitals scores alone, and a green report neither makes nor kills the case for a rebuild. Scores describe how pages load and respond; the investment case rests on whether the site can carry the firm's requirements.
Approve a Bounded Scope and a Named Owner
Whichever option survives the evidence, write the decision down: the observed constraint, the option selected, the assets to preserve, the owner, the dependencies, the exclusions, and the review point. Keep the record to one page, and use it: when a new request surfaces mid-project, the team can weigh it against the written purpose and accept, defer, or decline it on stated grounds instead of renegotiating the project from memory.
Choose the smallest scope that satisfies the demonstrated requirements, and keep the rebuild available for the day the foundation blocks them in fact. That order respects the money and review capacity the firm has spent on the current site without turning sunk cost into a trap.
If this decision is on your desk, we can help you frame it. Our website design work for financial advisors covers messaging, page planning, design, responsive development, and an SEO-ready structure, with the final scope agreed before a build begins. If you would rather talk through the constraint list first, start with a strategy conversation. Either way, bring the requirement list; it is the one document every option has to satisfy.
Related RIA Marketing Guides
Ready to turn marketing into a system?
Connect with our team at RIA.Marketing. We help advisory firms build practical, compliance-conscious systems for visibility, follow-up, and qualified inquiries.
Schedule Your Private Strategy Session
