Websites • Website Rebuild • System Implementations
The site did its job three years ago. Now it is costing you deals you do not see losing.
A rebuild is not a redesign. A redesign paints over the same structure. A rebuild replaces the structure itself: the architecture, the funnel logic, the copy, the technical foundation, the measurement. The visible result is a better-looking website. The commercial result is a site that finally matches the company you have become and the buyers you actually want to reach.
Most founders wait too long. The site keeps taking form fills, keeps showing up in search, keeps looking roughly like a website, and so the problem stays invisible until a deal is lost on a sleeker competitor or the sales team starts apologising for the site on every call. By that point, the cost of the delay is already in the pipeline.

Why a rebuild is the right move
You are not redecorating. You are replacing the operating surface of your sales motion.
A weak website does not page you at 2am. It does not crash. It just quietly taxes every other part of the business. Paid spend works harder than it should. Sales repeats itself on every call. Content lands on pages that cannot convert. Champions have nothing worth forwarding internally. You pay the cost in slower cycles, smaller deals, and a team that has to carry the site instead of being carried by it.
The question is not "does my site look dated". The question is "is my site the commercial infrastructure this business needs in its next stage". If the gap is honest and structural, a rebuild is the right move. If it is cosmetic, a refresh is cheaper and faster. The diagnostic call sorts which one you actually need.

The signals a rebuild is overdue
You do not need a full audit to feel most of these.

What a rebuild actually replaces
Seven layers, replaced together, so the new site reads as one commercial system.
How a rebuild does not lose your seo. The most common fear. The most solvable problem, if it is planned from day one.
Every old URL maps to a new one before migration. Every redirect is written in advance, not improvised at launch. Search engines follow those redirects and credit the authority of the old URL to the new one. Internal links are rewritten. Structured data is preserved and upgraded. Sitemaps are re-submitted. Rankings are monitored weekly for the first six weeks post-launch.
Done properly, a rebuild either preserves your organic position or improves it, because the new site is faster, cleaner, and more relevant. Done carelessly, a rebuild can cost years of organic equity inside a single weekend. The difference is process discipline, not luck. Our rebuild process is written to protect organic traffic as a primary constraint, not a secondary concern

How the work moves. Four phases. Rebuild, not rebuild-and-pray.
Phase 1 / Diagnose (weeks 1 to 2)
We audit the current site: analytics, search performance, user flows, CMS health, tech stack, and commercial function. We interview the founder, the sales team, and where relevant, a few customers. We surface the real commercial problem the rebuild needs to solve. Output is a written rebuild brief, a scoping range, and an approved scope of work.
Phase 2 / Frame (weeks 2 to 4)
Positioning is sharpened. Page architecture is drawn. Copy is written. Design direction is locked. A navigable prototype is built in the real design tool so you can click through the site before anything is coded. Stakeholders review in stages, not at the end, so the build never goes sideways late.
Phase 3 / Build (weeks 4 to 7)
The site is built on the chosen platform. Design system, components, page templates, forms, integrations, analytics, and redirects all in parallel. You see progress weekly on a staging URL. We run QA across browsers, devices, and performance targets before any launch date is accepted.
Phase 4 / Launch and handover (week 7 to 8)
Redirects deployed, DNS cut over, site monitored for the first fortnight, rankings watched, forms tested live, analytics validated, team trained on the CMS. Handover is written, not verbal, and your team owns the site after it ships. We stay on standby during the settling window.

How we think about rebuilds. Four non-negotiables on every rebuild, regardless of tier.

What changes inside the first 90 days
Observable shifts, not claims.

Is this the right engagement?
Strong fit if
Your company changed materially in the last two years. The site did not.
Your current site is built on a platform your team cannot operate without external help.
The sales motion depends on forwardability and the site cannot carry it.
Paid and content channels are live but the website is the bottleneck.
You are preparing for a pricing move, a repositioning, a new product, or a fundraise. The site has to be ready.
Probably not right if
You are pre-product-market-fit and the positioning is still moving weekly.
The real problem is brand strategy, not the website. Solve that first at /brand-strategy.
You want a visual refresh only. A refresh is cheaper and faster. Start at /visual-identity.
You want the cheapest possible vendor. We are not that vendor.
FAQ
What is the difference between a rebuild and a redesign?
A redesign keeps the existing structure and changes the surface: colours, type, maybe some new imagery. A rebuild replaces the structure itself: architecture, copy, platform, conversion logic, and measurement. A redesign takes two to four weeks. A rebuild takes seven to ten. A redesign lifts visual quality. A rebuild lifts commercial performance. If the problem is cosmetic, redesign. If the problem is structural, rebuild.
Will we lose our search rankings during the migration?
Not if the rebuild is planned properly. Every old URL gets mapped to a new URL before launch, every redirect is tested, internal links are rewritten, and search engines are pinged on the day. Rankings are monitored weekly for six weeks after launch. In most cases, organic traffic either holds flat or improves because the new site is faster and better targeted. SEO preservation is written into the statement of work as a primary constraint.
Can we keep our domain?
Yes. The domain stays. What gets replaced is the site underneath. Brand authority, backlinks, and search history all stay with the domain. Visitors only notice that the site looks and works better.
Do we have to migrate all our existing content?
No. Part of a rebuild is deciding what carries forward and what is retired. We audit every page of the existing site for traffic, conversion, and strategic value. High-performing pages are upgraded and migrated. Low-value pages are redirected or dropped. Dead weight on a new site still drags performance; we do not carry it forward out of habit.
Who writes the new copy?
We do, as part of the rebuild. Copy carries more of the conversion job than design, and a new site with old copy is a visual upgrade without a commercial one. We interview the founder and the sales team, audit the current site and the competition, and write every page from the new positioning down. Your team reviews, edits, and approves. You never get handed a blank CMS and asked to fill it yourself.
What platform will the new site be on?
Whatever fits your team and your needs best. In practice, most rebuilds land on Framer, Webflow, or WordPress. If the site needs deeper integration or custom logic, we move into a headless setup with a modern front-end framework. Platform is a fit question, not a religion. We recommend the platform at the end of the diagnostic, not before.
How long does a rebuild take?
Most rebuilds take seven to ten weeks end to end. Smaller brochure sites can land inside six. Larger B2B or eCommerce rebuilds with heavy integration can stretch to twelve. We scope honestly after the diagnostic call and hold the date once it is set.
What happens after launch?
We stay on standby for two weeks after launch to monitor rankings, fix any redirect edge cases, and validate form and analytics behaviour in the wild. After that, some clients move to a care plan for ongoing optimisation, some move to a paid or content programme that now has a site worth sending traffic to, and some operate the site on their own team. All three are supported.
Who on your team will actually do the work?
The principal who runs your diagnostic stays on through design and build. You do not get passed to a junior pod once the contract is signed. Continuity is one of the reasons rebuilds ship cleanly and on time.
Who on your team will actually do the work?
The principal who runs your diagnostic stays on through design and build. You do not get passed to a junior pod once the contract is signed. Continuity is one of the reasons rebuilds ship cleanly and on time.
What investment range should we expect?
Most rebuilds sit at our W2 or W3 tier, with W4 reserved for sites requiring custom development, multi-region architecture, or heavy integration work. The diagnostic call produces a real scoping range. No ballparks from the cold.









