You did the responsible thing. You accepted that the old site was dated, you got quotes, you picked a firm that showed you work you liked, and you spent months in review cycles and content requests. It launched. It looks considerably better. Everyone said so.
And the numbers are the same. Maybe a small bump in the first few weeks that flattened out. The phone rings at roughly the old rate, the form submissions land at roughly the old rate, and the quality of the inquiries has not changed at all. You are now in an uncomfortable position, because the obvious explanation is that you chose badly, and you do not believe that. You looked at the work, you checked references, you asked reasonable questions.
You probably did not choose badly. You bought exactly what was on offer, and what was on offer was a surface. That is the honest answer, and it is more useful than it sounds, because a surface problem and a structural one have very different fixes and only one of them costs another five figures.
Why Do Redesigns Usually Change Nothing?
Because the thing that was broken was almost never the thing that got replaced.
A redesign, as the industry usually sells it, is a visual and technical refresh. New layout, new typography, updated photography, a modern build, better mobile behavior. All real work, and all of it operating on the top layer. Underneath that layer sits everything that actually determines whether a stranger becomes an inquiry: what the site is for, who it is speaking to, what it needs to prove and in what order, and the path a visitor walks from arriving to reaching out. If nobody examined that layer, then the redesign faithfully rebuilt your existing structure in nicer clothes. The result converts about as well as the old one because, functionally, it is the old one.
This is why so many firms redesign every three or four years and each time quietly wonder why it did not take. Each cycle addresses the visible symptom. The cause is one layer down, which is exactly the distinction between a website and digital architecture and the reason the two produce such different outcomes.
Here is the part that is genuinely not your fault. That structural work is invisible in a proposal. Two firms can send you documents describing what sounds like the same project, and the difference between them is entirely in work that produces no images to show you at the pitch stage. You cannot evaluate what you cannot see, and nobody warned you there was something to look for.
How Do I Tell What Actually Broke?
Redesign disappointment almost always traces back to one of four places, and they are distinguishable.
Nobody defined what the site was supposed to accomplish. If the brief was effectively "make it look modern and professional," then the project had no success condition beyond taste, and it met that condition. A site built without a specific job does not fail so much as succeed at nothing in particular.
The structure was inherited rather than designed. If the new site has the same pages in the same order with the same navigation as the old one, the visual work sat on top of a map nobody redrew. The most common tell is a homepage that opens by talking about the firm rather than the visitor's problem, carried over because it was already there.
The path to contact was never examined. Count the steps between a visitor landing on your most-visited page and being able to act. If the next step is not obvious without scrolling or hunting, the redesign did not fix the leak, it repainted the room around it.
The traffic changed, or was never right. Sometimes the site is genuinely improved and the visitors are wrong, or a technical detail of the migration cost you search visibility at launch. This is worth checking early because it produces the same flat numbers from an entirely different cause.
If you want a structural read rather than a self-assessment, see how your architecture scores →. It grades the path a visitor actually walks, which is the layer the redesign most likely never touched.
What If the Website Isn't the Problem at All?
Sometimes it isn't, and any firm unwilling to tell you that is not a firm worth hiring for the diagnosis.
There are cases where the site is fine and the flat numbers are coming from somewhere else entirely. Not enough of the right people are arriving, and no amount of conversion work fixes an audience problem. Or the traffic is fine and the offer itself is not compelling in the current market, which is a business question wearing a marketing costume. Or the inquiries are actually arriving and something downstream, slow response times, a broken form notification, an intake process that loses people, is quietly eating them before you ever see them. That last one is more common than anyone likes to admit, and it is worth ruling out first because it is cheap to check and expensive to ignore.
We are saying this plainly because the incentive runs the other way. A firm that sells rebuilds has every reason to conclude you need a rebuild. If the honest answer for you is that your site is adequate and the problem is upstream or downstream of it, that is a real possible finding, and hearing it saves you far more than another project would have earned us.
Should I Just Redesign Again With Someone Better?
Not yet, and not on the same terms. Commissioning a second redesign without knowing why the first one failed to move anything is how firms end up paying twice for the same result. The variable you would be changing is the vendor. The variable that determined the outcome was the absence of a diagnosis, and that is unchanged.
There is a real question of whether the honest fix is even a rebuild. It frequently is not. If the underlying build is sound and the failure was structural rather than technical, the work can be restructuring what exists: rebuilding the navigation and page hierarchy around a defined path, rewriting the pages that carry the decision, fixing the route to contact. That is a substantially smaller intervention than starting over, and it uses the money you already spent rather than writing it off. Before you consider what a serious rebuild involves, it is worth understanding what that level of work actually costs and why, because the answer should be scoped to a finding rather than quoted from a template.
Isn't This Just Another Firm Telling Me the Last One Was Wrong?
A fair suspicion, and you should hold onto it. You have already sat through one confident pitch that did not deliver, and confidence is the cheapest thing in this industry.
The difference we would point to is not conviction, it is order of operations. The standard sequence is to quote a project and then discover what the problem is while building it. The sequence we hold is to diagnose first, in a bounded piece of paid work, and to let the finding determine the scope, including the findings that are inconvenient for us. If the recommendation you get is smaller than a rebuild, or points away from the website entirely, that is the diagnosis doing its job. Judge that claim the way you would judge any other: by whether the work is bounded, whether the finding is delivered to you in writing regardless of what it says, and whether you remain free to take it elsewhere. Those are checkable. Confidence is not.
What Does It Cost to Find Out What's Wrong?
The lower-commitment starting point is the Blueprint, a standalone paid diagnostic at $3,500. It maps what your site needs to do, examines where the current one breaks down, and tells you the scope of the actual fix. It is deliberately separate from any build, so the finding is not shaped by what would be profitable to recommend. You get the map whether or not you ever hire us for the work, and taking it to your existing developer is a legitimate outcome.
If the finding is that a full rebuild is warranted, that diagnostic work is built into it, and a rebuild for an established firm runs $22,000 to $35,000, scoped against what the diagnosis found rather than a number set in advance. What you are buying at the start is an accurate account of what went wrong. What you are not buying is a promise of a specific increase in inquiries, because anyone offering you that figure before examining your site is doing the same thing that got you here.
What This Looked Like Building Fortaleo
We are a firm with a website, so the honest test is whether we did the thing we are describing. On our own build, the structure came first: what the site had to accomplish, who it had to convince, and the path a visitor walks, all settled before a single visual decision was made. The design served that structure rather than the other way around.
What that produced is measurable and public. Live and fully indexed in about thirty days, through a forty-seven-point quality gate, with schema on every page and indexing achieved within roughly two weeks of launch. Scores of 100 for SEO, 91 on mobile and 99 on desktop for performance, and 2 out of 2 on agentic browsing, the test of whether AI systems can actually read the site.
The discipline mattered most where it was least visible. During our own audit we found evidence that article content might be rendering in a way some crawlers could not read, a failure that every conventional check reported as healthy. It was caught by looking underneath the surface at the raw output, and fixed before launch. That is precisely the class of problem a redesign does not find, because a redesign is not looking there.
The First Step Is Smaller Than It Feels
You are not being asked to spend again or to write off what you already spent. Neither of those is the next step. The next step is far smaller: finding out what actually went wrong, so the decision in front of you narrows from "do I risk another redesign" to "here is the specific gap, and here is the smallest thing that closes it." Sometimes that turns out to be a genuine rebuild. Often it is a fraction of one. Either way, knowing which is the cheapest useful thing you can do right now, and it is the only step that keeps the next decision from being a guess.