LFW

Capabilities · Projects

Rebuilds & replatforms, with the terms in writing first.

Full rebuilds and migrations quoted with fixed scope, timeline, and price — agreed in writing before work begins.

No hourly meter running, no scope that quietly grows, and no discovery phase that bills for deciding what you already told us you needed.

Fixed before work begins
ScopeWritten down page by page, feature by feature. Anything new is a change order you approve, not a surprise on the invoice.
TimelineDated milestones you can hold us to, including the launch window and what has to be ready from your side.
PriceOne number for the agreed scope, quoted for the size of your site. No hourly meter, no overage clause.

All three are in the agreement before anyone writes a line of code — and the agreement itself is published on this site.

When this is right

The platform is out of road

End-of-life, unsupported, or no longer safe to keep patching. Every month it stays up is a month of accepted risk.

A redesign is due anyway

And the content structure needs rethinking with it — not just a new coat of paint over the same broken navigation.

There’s a standard to meet

The site has to reach an accessibility standard it was never built for, and retrofitting costs more than rebuilding.

You’re leaving a walled garden

A proprietary platform holds your site, and you want to own what comes next — content, code, and credentials. We rebuild on open platforms: WordPress, Drupal, or a static build, chosen for what you actually need to run.

How a project runs
01

Content migrates completely

Everything comes across and gets checked — not the top forty pages with the rest marked “archive.” That holds whether you’re moving between WordPress and Drupal, off a proprietary platform, or onto a static build.

The parts nobody has looked at in five years are exactly where the board minutes and the records requests live.

02

Accessibility is built in

Verified as it’s built, not audited in at the end. Contrast, keyboard access, focus order, and labels are decisions made once, correctly.

Retrofitting a finished site is the expensive way to arrive at the same place. See accessibility & 508.

03

Redirects are mapped

Every old URL points somewhere deliberate, so nothing that ranked in search or sat in someone’s bookmarks goes dark on launch day.

This is the step most rebuilds skip, and it is why traffic falls off a cliff the week after a relaunch.

04

You own the result

The site, its content, its records, and the credentials — held in your accounts, not ours. A rebuild here isn’t a way in to a dependency.

Most projects move into ongoing management because it’s useful, not because leaving is hard. Handover is written into the agreement either way.

Know the scope, the date, and the price before you commit.

Book a call to talk through the rebuild — or run the free audit first and bring what it finds to the conversation.

Prefer to write?

Tell us what needs to work better.

Slow, fragile, hard to edit, missing a workflow — say it plainly. You'll get a straight answer, not a ticket number.

You'll get a straight answer, usually the same day.