Recently, I've been noticing more website redesign RFPs — particularly ones involving overhauling an existing CMS. Municipalities, utilities, counties. And it's bringing me back to something I've learned over years of overhauling applications — migrating platforms, swapping out languages, restructuring databases, moving infrastructure.

There's a pattern that holds true whether you're modernizing a legacy ColdFusion app or redesigning a county website on Wix. And most teams miss it.

They treat a website redesign as one project.

It's not. And that assumption is where most redesign projects start failing — before a single line of code is written.

The Problem Nobody Names

A website redesign isn't one project. It's three. And most teams — vendors and clients alike — don't recognize that until they're halfway through and things are falling apart.

Here's what I mean. Every website redesign involves three distinct layers of work:

The public-facing layer — what your residents, customers, or constituents actually see. The design, the navigation, the visual identity. This is what most people think of when they hear "redesign." It matters. Design isn't decoration — it's communication. Someone visiting your website is usually alone, often frustrated, trying to accomplish something specific. The design has to hold their hand.

The business logic layer — how your organization actually operates through the website. Content types, editorial workflows, role-based permissions, departmental content management. This is the layer that determines whether your staff can actually maintain what gets built. Most RFPs barely mention it. Most vendors configure a default CMS and move on.

The migration and infrastructure layer — the heavy lift. Content extraction from your legacy platform, restructuring to fit the new architecture, URL redirects for every existing page, accessibility remediation, media migration, and validation. This is the unglamorous work that determines whether the project actually succeeds. If this layer fails, the pretty design and smart CMS configuration don't matter.

Why This Matters

These three layers aren't independent. They inform each other.

The migration plan reveals what your content actually looks like — which tells you what content types your CMS needs to support. The CMS configuration determines what templates the design system needs. The design's information architecture determines how legacy content gets restructured during migration.

When you don't recognize these as distinct workstreams, you plan them as one. And when you plan them as one, you discover the dependencies too late. The design is approved but the CMS can't support it. The CMS is configured but the migrated content doesn't fit the content types. The migration is scoped but nobody accounted for the 200 PDFs that need accessibility remediation.

I've seen this play out across government, utility, and nonprofit projects — organizations with real budgets, real timelines, and real consequences when a website doesn't work.

A Better Way to Think About It

At WAM DevTech, we call this the Three-Layer Methodology™. It's not complicated. It starts with recognizing that these three layers exist, then planning them together from day one so they inform each other instead of colliding later.

Think of it like an orchestra. Every section rehearses independently — strings, brass, percussion. Each sounds fine on its own. But without a conductor who understands the full score and brings them together with precise timing, you don't get a symphony. You get noise.

The conductor's job isn't to play every instrument. It's to see the whole picture and make sure every part lands together. That's what a good redesign partner does — not just design pages or configure a CMS or migrate content, but orchestrate all three so the final result actually works.

"Without a conductor who understands the full score, you don't get a symphony. You get noise."

The Question to Ask Your Next Vendor

If you're evaluating proposals for a website redesign, ask this: "Show me how you plan design, CMS configuration, and migration as interdependent workstreams."

If they look at you like that's a strange question, you have your answer.

About WAM DevTech's Three-Layer Methodology™

Most website redesigns treat design, CMS, and migration as one deliverable. We treat them as three interdependent workstreams — planned together from day one, orchestrated by senior architects, and accelerated by AI tooling. The result: fewer surprises, faster delivery, and a website that actually works for the people who have to use it and the staff who have to maintain it.

Learn more about our CMS Modernization approach →