Skip to content
← Back to Blog

Redesign, Rebuild, or Replatform? What Each Word Actually Means on Your Invoice

A board approves a website redesign, the RFP goes out using that word, and three vendors quote numbers that differ by a factor of six. The vendors are not being inconsistent. They are answering different questions, because the word in the RFP did not tell them which question was being asked.

This is not a semantic exercise. The word you choose sets the budget your board approves, the scope your vendor prices, and the expectations your staff carry into the project. Getting it wrong is the single most common reason association website projects arrive late and over budget, and it happens before anyone writes a line of code.

Why the word on your RFP sets the price you get quoted

A vendor reading your RFP has to infer scope from the language you use. If the document says redesign and describes new page templates and a modernized look, the vendor prices visual and structural work on the platform you already have. If your actual situation is that the content management system is three major versions behind, the member portal no longer authenticates against your association management system, and the URL structure has to change, then you have described a redesign and you require a rebuild. The quote you receive will be honest and wrong, and the gap surfaces in month four as a change order.

The reverse happens too, and it costs you differently. An organization writes "complete rebuild" because the site feels tired, receives quotes in the range a full reconstruction commands, and concludes that a website is unaffordable. What the site actually needed was a refresh at a fraction of the cost.

Refresh: the surface changes, the structure does not

A refresh updates what people see without changing how the site is built. New colors, updated typography, replaced photography, revised copy on the pages that matter most, and perhaps a reworked homepage. The content management system stays. The page templates stay. The information architecture stays. The integrations are untouched.

A refresh is the right answer when the underlying site is sound and the complaint is that it looks dated next to peer organizations. It is the cheapest option on this list by a wide margin, and it is frequently the correct one. If your members can find what they need, your renewal path works, and your staff can publish without calling a developer, the problem may genuinely be cosmetic.

What a refresh cannot fix: a broken member experience, a content structure that no longer matches how the organization works, an unsupported platform, or an integration that has stopped syncing.

Refactor: the structure is sound, specific parts are not

A refactor keeps the existing site in production and repairs identified problems. Performance work, replacing deprecated plugins or modules, rebuilding one broken section, upgrading hosting, fixing mobile behavior. The site continues operating throughout. Members experience no cutover.

Refactoring is surgical rather than comprehensive. It works when the platform is current and adequately hosted, the architecture holds up, and the failures are specific and traceable. It does not work when the problems are systemic, because you end up repairing the same system repeatedly and paying for it each time.

Redesign: the experience changes, the platform stays

A redesign changes how the site works and how it feels, on substantially the same technical foundation. New information architecture, new templates, new navigation, new visual system, content reorganized around how members actually behave rather than how the organization is structured internally. The content management system usually remains, though it may be upgraded within its own major version.

This is the most commonly requested and most commonly misunderstood item on the list. A redesign is genuinely significant work. It is also bounded by a decision that has already been made: you are keeping the platform. That constraint is what separates a redesign from the two items below, and it is the constraint most RFPs fail to state explicitly.

Rebuild: the site is constructed again from the ground up

A rebuild produces a new site. New templates, new architecture, new content model, new code, built alongside the existing site and launched as a cutover. The platform may stay the same in name, but nothing is carried forward except content and, if the work is done properly, search equity.

Rebuilds become unavoidable when technical debt has compounded past the point where repair is cheaper than replacement. Signs include a theme that has been modified so heavily it can no longer be updated, a content model that requires staff to work around it rather than with it, and accumulated customizations nobody remaining at the organization can explain.

The practical difference from a redesign: a rebuild duplicates infrastructure for the duration of the project, requires a migration plan and a cutover, and carries launch risk that a redesign on the existing platform does not.

Replatform: the content management system itself changes

A replatform moves the site from one content management system to another. Drupal to WordPress. WordPress to a headless architecture. A proprietary association platform to something open source. This is the term that almost never appears in association RFPs, and its absence is expensive.

A replatform includes everything a rebuild includes, and then adds content migration between systems that model content differently, integration work rewritten against a new platform's interfaces, staff retraining on an unfamiliar editing experience, and a redirect map that has to be correct on the first day or search visibility built over years disappears.

Associations arrive at replatforming for reasons that are rarely about design. A platform reaches end of life and stops receiving security updates. Institutional knowledge of the current system leaves with a departing staff member or vendor. Licensing costs change. The existing platform cannot support an integration the organization now depends on. In each case the driver is operational, which is exactly why framing the project as a redesign misleads everyone involved.

The distinction most associations miss

Redesign and rebuild are not points on the same scale, and treating them as though they are is the error that generates the change orders. A redesign is a decision about the experience. A rebuild is a decision about the construction. You can rebuild a site and keep the design almost unchanged, which happens routinely when the driver is technical debt rather than appearance. You can redesign a site thoroughly without rebuilding anything underneath it.

The question that separates them is not how different will it look. It is how much of what exists are we keeping.

Why association projects get this wrong more than most

Three conditions make associations particularly exposed to this confusion.

Integrations multiply the stakes. A typical association website connects to an association management system, an event registration platform, an email service, and often a learning management system or community platform. Every one of those connections has to be reconsidered under a rebuild or a replatform, and most of them survive a refresh or a redesign untouched. An organization that scopes a redesign and discovers mid-project that single sign-on has to be rewritten has not experienced scope creep. It has experienced a scoping failure.

Governance delays the decision. Website projects at associations are approved by boards and committees on annual or quarterly cycles. By the time approval arrives, the site has aged further, and the option that was accurate when the conversation started is no longer the option the organization needs. The word in the approved budget outlives its accuracy.

Institutional memory is thin. Staff turnover means the people specifying the project are frequently not the people who commissioned the current site. Nobody in the room knows which customizations exist or why, and the assessment that would reveal a rebuild is necessary has not been done.

How to tell which one you are actually buying

Work through these in order. The first one that produces a yes sets your floor.

Is the content management system unsupported, end of life, or a version you cannot upgrade to? If yes, you are replatforming or rebuilding, whatever the project is called.

Do the integrations have to be rewritten rather than reconnected? If yes, you are at minimum rebuilding.

Does the content model itself need to change, meaning the way information is structured rather than how it is presented? If yes, you are rebuilding.

Does the navigation, the page structure, and the member journey need to change? If yes and the answers above were no, you are redesigning.

Are specific components broken while the rest works? If yes, you are refactoring.

Is everything functional and the complaint is that it looks dated? You are refreshing, and you should be relieved.

What to write in the RFP instead

Do not lead with any of the five words. Lead with the constraints and let vendors tell you which category the work falls into. Name the current platform and its version. List every system the site connects to, and say whether each one is staying. State whether the URL structure can change. Say who will maintain the site afterward and what they are capable of. Give the budget range you have approved.

An RFP written that way receives comparable quotes, because every vendor is pricing the same project. It also surfaces disagreement early: if two vendors read your constraints and reach different conclusions about whether this is a redesign or a rebuild, that difference is the most useful information you will receive during the process, and it costs you nothing to learn it before the work starts.

Where to go deeper

If you have established that the site needs significant change but you are weighing how much, the redesign and refresh comparison walks through seven signals that distinguish them. If you have established that the work is technical and you are weighing repair against replacement, the rebuild and refactor comparison covers the technical debt assessment, the cost framework, and the staged approach that sits between them.

And once the decision is made, the sequence in which the work has to happen matters as much as the choice itself.

83 Creative

We're a web development studio that works exclusively with trade associations, professional societies, and membership organizations.

← Previous Article Drupal Cut Security Support for Each Version to Eight Months. Here Is Your New Update Calendar.