The existing site, made right. Draft-first. Signed off before it goes live.
When your client’s site needs a visual overhaul — not a full rebuild — we deliver Figma-faithful redesigns behind a QA gate. Single page or multi-page; Elementor Pro or block editor; always built in draft, never pushed live until you say so.
Send us a briefA redesign is not a smaller rebuild.
A homepage redesign touches the highest-stakes page on a retained client's site — the entry point for organic search, paid traffic, and direct bookings. The scope is tighter than a full rebuild: one page, sometimes two or three. The Figma is the brief; the page builder is the delivery vehicle. No migration, no redirect work, no DNS cutover.
We cover both shapes. A single-page redesign — the most common form — brings a new homepage to life in Elementor Pro against the agency's Figma, built as a WordPress draft in parallel to the live page. A multi-page redesign extends that discipline across a defined set of pages when the client's refresh goes further than the homepage. Either way, the live site is never half-finished. The redesigned page replaces the original only once the agency has reviewed and signed off.
This is the right engagement when your client's site works but the design is stale, off-brand, or no longer conversion-ready — and a full rebuild would be overkill.
Figma in. Live page out. Nothing goes live until you say so.
-
01
Figma → Elementor Pro or block editor. We implement against your approved design frames, not a paraphrase of them. Global styles, responsive breakpoints, and reusable section patterns — pixel-faithful, editable by your team after handoff.
-
02
Built in draft, not live. The redesigned page is staged as a WordPress draft alongside the live page. No mid-build exposure. At every moment, the live homepage is either the unchanged original or the fully reviewed new version — never a half-finished hybrid.
-
03
Internal QA before handoff. Site Checker — our pre-handoff QA plugin — runs across core settings, content and SEO surface, URL structure, and multi-resolution screenshot capture. Fail-zero gate before you see it. Your QA layer runs post-handoff; we own the fix loop.
-
04
Post-review round built in. Principal comment rounds are part of the plan, not afterthoughts. For Legal and other claims-sensitive practices where the homepage is a contract-relevant surface, the post-review round is a structural gate, not a courtesy.
Tool ecosystem: Elementor Pro — Gravity Forms — Kadence / Astra parent themes — WP Engine / Kinsta staging. See our full services overview →
Redesigns we’ve shipped
Frequently asked, plainly answered.
Specific to this engagement shape — what we mean by it, what we own, what changes the hours.
-
Draft-first delivery. The live homepage is either the existing version (untouched) or the signed-off new version. Never a half-finished hybrid. We build the redesign in staging, you review, you sign off, only then is the cutover scheduled. There's no preview link that's secretly live; there's no "soft launch" while review is in progress.
-
On a single-page Figma-first redesign, workbook absence is normal — the contract is the Figma file plus the Redmine issue list. On larger multi-page redesigns, an agency-side workbook may still be in use; we work to either input. The live URL is the externally verifiable deliverable, and we run a fresh production crawl post-launch as the closing record.
-
Part of the process. On draft-first single-page redesigns, the post-first-cut review round is tracked as a named Redmine issue — not an optional extra. The draft-first model assumes a structured review pass after the first version; we plan and quote against it from day one. On larger multi-page engagements, the same review pass is tracked through the agency's existing review cycle.
-
Same playbook, proportional effort. A single-page draft-first redesign typically runs 15–20 hours. A multi-page Figma-faithful redesign (10+ templates, 100+ pages) runs 60–80 hours and adds template-system effort proportional to page count. Same draft-first discipline, same review round, same QA gate before launch.
-
Yes. For regulated practice areas — Legal and healthcare with claims sensitivity, where attorney-advertising rules or medical-claims compliance carry real exposure — draft-first is risk insurance for the agency, not just a quality safeguard. We treat it as the substantive deliverable: the client never sees an unsigned-off page, and the agency always has an authoritative signed-off version on file before cutover.
-
The brief is what differs. A Refresh keeps everything the same except how the site looks — same URLs, same content, same navigation, same templates re-skinned in the new design. A Redesign goes further: structure may shift, templates may be added or removed, content can be reorganised, sections can be re-ordered, navigation can be re-hung. If your brief reads "make this site look new," that's a Refresh — cheaper, lower risk, faster. If your brief reads "rethink how this site is organised, what's on the homepage, how users move through it," that's a Redesign. When a brief crosses the boundary either way, we re-scope the engagement type at intake rather than discover the mismatch mid-build.
Have a retained client ready for a visual overhaul?
Send the Figma and the site URL. We'll come back with a fixed-hours estimate, a draft schedule, and a clear post-review plan. No live-site exposure during the build — at any moment the live page is either the unchanged original or the signed-off new version. (If the brief is to re-skin the existing site without changing structure, see Refresh instead.)