Rebuild a piece at a time, not all at once

The all-at-once rebuild is the default because it is easier to sell and easier to project-manage. It is also the riskiest, and for many businesses a slower, piece-by-piece approach produces more revenue and fewer disasters.

Talk to us about your site

Rebuilding in slices means improving a site page group by page group, keeping addresses and content intact, and measuring each change. It suits sites whose foundation still works, spreads the cost, and avoids the single moment where everything can go wrong. It does not suit sites with genuine technical limits.

Why the big-bang rebuild is the default

It is easier to quote, easier to schedule, and it produces the moment of transformation that everybody enjoys. It also concentrates all the risk into one day and discards whatever was quietly working.

For businesses whose site is structurally sound but tired and thin, the concentration of risk buys nothing that a series of improvements would not have delivered more safely.

What a sliced rebuild looks like

You improve in coherent groups, each one live and measured before the next begins, with addresses and existing content preserved throughout.

  • First: the message on the homepage and the main service pages.
  • Then: evidence, cost information and contact paths on the pages that earn.
  • Then: the missing pages, service by service and area by area.
  • Then: the design refresh, applied across what now exists.
  • Throughout: speed and mobile behaviour improved wherever they are worst.

Order by what pays soonest

Start where the return is fastest, which is almost always the conversion work on the pages that already receive visitors. It funds the later stages and it changes the numbers within weeks rather than months.

Design usually comes late in this sequence, which feels wrong to everybody and is nearly always correct.

Keeping it coherent while it is in transition

The obvious objection is that the site looks inconsistent halfway through. In practice, visitors see one or two pages, not the whole site, so partial inconsistency costs far less than it feels like it should.

You can also reduce it by updating shared elements first, such as the header, footer, buttons and typography, which makes old and new pages look related while the content work continues.

The measurement advantage

This is the real benefit and the one most often overlooked. Changing one group at a time means you learn what worked, because the change was isolated.

After a big-bang rebuild, nobody knows which of a hundred simultaneous changes moved the numbers, so nothing is learned and the next rebuild starts from the same ignorance.

When slices are the wrong answer

Where the foundation genuinely limits you, slicing prolongs the problem. A site that cannot be made fast, cannot be edited, or cannot be read by search engines will resist every improvement you attempt within it.

There is also a practical limit: if the underlying system is unmaintained or insecure, no amount of careful sequencing makes staying on it sensible.

How Licheo works this way

Where the foundation is sound, we improve in slices and measure each one, because it produces returns sooner and teaches you what actually works on your own site.

Where a rebuild is genuinely required, we say so, and the existing addresses and earning content are carried across rather than started again.

Part of a larger guide

This page is one part of Redesign and revenue. The other parts:

Questions people ask

What does rebuilding in slices mean?
Improving a site in coherent groups, each live and measured before the next begins, with addresses and existing content preserved. It spreads cost and risk and lets you learn what worked.
Will my site look inconsistent during the process?
Partially, and it matters less than it feels. Visitors see one or two pages rather than the whole site, and updating shared elements first keeps old and new pages looking related.
What order should the slices come in?
Conversion work on pages that already receive visitors first, since it pays soonest and funds the rest. Missing pages next. Design usually last, which feels wrong and is nearly always right.
What is the main advantage?
You learn what worked, because each change was isolated. After an all-at-once rebuild, nobody can say which of a hundred simultaneous changes moved the numbers.
When is this approach wrong?
When the foundation genuinely limits you: unfixable speed, no ability to edit, content search engines cannot read, or unmaintained technology. Slicing then simply prolongs the underlying problem.

Improve without the big day

Where the foundation is sound, we improve in measured slices so you see returns sooner and learn what works.

Talk to us about your site Read the full guide