Legal Homepage Redesign — Figma-to-Elementor Pro, White-Label for a US Marketing Agency
A personal-injury law firm homepage redesign built in draft before live launch — Figma-to-Elementor Pro, 2 QA rounds plus principal review, 31 days.
Screenshots captured by automated tooling — some elements may not have loaded fully or may layer on top of each other. For the most accurate view, visit the live site →
Build the new homepage against the agency Figma. Deliver as a draft. Accept one principal post-review round. Launch only after sign-off.
The Craft of a Homepage Redesign
A Figma-to-Elementor Pro homepage redesign on a WPBakery site — built in draft, not pushed live until the agency principal signed off. The brief was explicit: Elementor Pro, develop in the draft. The friction emerged when the new Elementor header and footer were applied site-wide: Elementor suppressed WPBakery styles, briefly taking the site down. We restored a backup, resolved the conflict, and propagated the global header and footer before the agency reviewed.
Snapshot
| Field | Value |
|---|---|
| End-client industry | Legal — Personal Injury |
| End-client | The Stein Law Group (NY metro area personal-injury practice) |
| Engagement | White-label homepage redesign for a US marketing agency specialising in local-business websites |
| Project Type | Figma-to-Elementor Pro homepage redesign — built in draft, released after agency-principal post-review |
| Scope | 1 homepage — full redesign to agency Figma, built in WordPress draft, launched after a principal post-review round |
| Timeline | 31 days (20 Nov – 20 Dec 2025), on schedule |
| Effort | ~15 hours — ~7.7h development · ~7.7h QA across 2 rounds · balance on post-review implementation |
| Team | 4 specialists (dev + QA + project lead) |
| Design handoff | Figma design (agency-owned; design URL withheld) — approved brief explicitly required Elementor Pro and draft-first delivery |
| Tech Stack | WordPress · Elementor Pro · existing agency WordPress hosting · Site Checker (xaverPRO QA plugin) |
| Build mode | Draft-first — new homepage built as WordPress draft in parallel to live site, no mid-build live exposure |
| Delivered | Homepage redesign shipped to spec, one post-review comment from the agency principal implemented and launched, site live at thesteinlawgroup.com |
| Review rounds | ≈3 review rounds across the 31-day calendar window |
The Brief
A US marketing agency retained by The Stein Law Group — a personal-injury legal practice serving the NY metro — handed us a new homepage design in Figma with two explicit constraints: the implementation had to be in Elementor Pro (already installed on the client site), and the build had to be completed in draft rather than live on the production homepage.
The rationale was straightforward. Law firms are unusually sensitive to live-site changes — unintentional shifts to claims, case-result framing, or legal disclaimers can create compliance and reputational risk that a dental practice does not face. The agency wanted the design built in parallel to the live site, reviewed internally, and then reviewed again by the agency principal before any live cutover.
The ask was concise: match the Figma in Elementor Pro; ship a draft; accept a post-review round for any final comments from the agency principal; launch the page only after her sign-off. The law firm spoke only to the agency; we never appeared on a call or an email with them.
Risk Context. On a legal-industry homepage, the stakes per pixel are unusually high. Every claim on screen — case-result framing, jurisdiction language, attorney-advertising disclaimers — carries compliance weight. The redesign was never pushed live until the agency principal had reviewed and signed off; at every moment during the build, the live homepage was either the unchanged original or the fully-reviewed new version, never a half-finished hybrid. Draft-first delivery is not a process nicety on this engagement type — it is the contract-relevant gate that protects the agency from a live-site incident on a retained legal client.
How We Did It
1. Figma-to-Elementor Pro, draft-first. The homepage was built entirely in Elementor Pro against the approved Figma frames — hero, service sections, testimonials, contact callout, footer. Because Elementor Pro was already installed on the site, the build slotted into the existing theme and global style system without introducing a new page-builder dependency.
2. Built in draft, not live. The new homepage was staged as a WordPress draft in parallel to the existing live homepage. Every QA pass ran against the draft until launch. This is the operational safeguard specifically requested by the agency on this project type and this client industry — a legal practice cannot afford a half-shipped homepage going live mid-QA.
The principle behind this is simple: on a redesign of a legal-industry homepage, the dev team’s default must be draft-first. A dental or restaurant site tolerates optimistic shipping; a law firm does not.
3. Two internal QA rounds before agency handoff. QA passed three developers — Pavel, Timur, and Anton — against desktop and mobile viewports, catching the usual residue of any Figma-to-Elementor translation (Elementor Pro renders some padding behaviour differently from Figma’s auto-layout; link targets needed verification; the form block needed Gravity Forms wiring).
4. Post-review round — principal comments, then launch. After agency-side review the principal raised a discrete set of comments on the draft. We implemented those comments in a tracked follow-on issue and published the page live behind the agency’s final sign-off. A further round of QA across three developers verified the live-launch state.
The real tension was the page-builder conflict: applying the new Elementor Pro global header and footer site-wide suppressed WPBakery styles and briefly took the live site down. We restored a backup immediately, resolved the conflict in isolation, and ran propagation again — cleanly. Because the new homepage was never in draft limbo on a half-up site, the incident resolved before the agency saw it.
Operational Integrity at handoff
QA before handoff caught that the new homepage draft had been accidentally published — against the explicit brief requirement to keep the page in WordPress draft and closed to indexing — so we immediately reverted the page to draft status before the agency review. The Trustindex reviews widget had also broken the page layout during build, which we fixed in the same QA pass. Pre-handoff QA ran through Site Checker — see our QA approach for the categories and the zero-open-issues bar before handoff. After handoff the agency ran its own QA. We closed what it surfaced before sign-off.
Results
| Metric | Outcome |
|---|---|
| Homepage redesign | Shipped — Figma implemented in Elementor Pro, replacing the previous live homepage |
| Build mode | Draft-first — new homepage built as WordPress draft in parallel to live site, no mid-build live exposure |
| QA rounds | 2 internal + 1 post-launch — Pavel, Timur, and Anton each passed desktop + mobile on each round |
| Post-review | 1 round — principal comments implemented, then launched behind agency sign-off |
| Timeline | 31 days (20 Nov – 20 Dec 2025), delivered on schedule |
| Effort | ~15 hours — roughly half development, half QA, consistent with the typical single-page redesign profile |
| Team | 4 specialists — no dedicated strategist, no design lead (agency-owned), no SEO lead (no migration scope) |
| Site status | Live at https://thesteinlawgroup.com/ — verified April 2026. |
In the end: we implemented the agency’s Figma in Elementor Pro on a draft, reviewed it twice internally, iterated once against the agency principal’s comments, and launched it live — all inside 31 calendar days and about 15 hours of effort.
Process
| Phase | Duration | Outcome |
|---|---|---|
| Brief & estimation | ~2 days | Figma reviewed, Elementor Pro confirmed, draft-first delivery model agreed |
| Homepage build (draft) | ~1 week | Full homepage implemented in Elementor Pro in a WordPress draft |
| Internal QA round 1 | ~2 days | Pavel + Timur + Anton against desktop + mobile; residue logged |
| Post-review — principal comments | ~1 week | Agency-principal comments captured; implementation ticket opened and resolved |
| Launch + QA round 2 | ~1 week | Page published live; post-launch QA across 3 developers closed |
Phases overlap — QA began before the draft was feature-complete, and the post-review round was triaged on the same day the initial internal QA closed. This is characteristic of small-scope redesigns where the QA loop runs continuously rather than in a distinct phase.
Team
Delivery team
- Nikita Tumasevic — homepage build in Elementor Pro against Figma
- Pavel Sazhin — QA across both rounds and post-review implementation support
- Timur Arbaev — QA across both rounds and post-review implementation support
- Anton Hersun, xaverPRO — project lead (estimation, agency-side communication, post-review coordination, sign-off)
Agency-side project management, design, and client communication remained with the partner agency throughout. The Stein Law Group knew the agency as the firm doing the redesign; our names never reached them. The agency principal’s post-review comments were routed through us, implemented, and returned for her sign-off.
For agencies commissioning a white-label WordPress redesign
On a personal-injury redesign, the real agency risk is a draft page with unapproved case language reaching the live URL. For this firm — a single-attorney practice with local case pages; for others — a multi-attorney group with a pooled settlement library. The quiet failures are specific: a draft page escapes the staging environment unapproved. Visual tokens update the header but leave practice-area archives on the old palette. New card layouts assume copy that does not match the client’s actual disclaimers, so the page breaks at runtime.
The question to ask a dev partner before committing is not “can you execute a visual overhaul?” — it is “how exactly will you gate every page transition so no unapproved draft hits the public URL?”
Send us your current design files and a URL inventory. We will map the new layouts against the pages that actually rank, identify where the redesign assumptions break against the published content, and return a fixed-hours quote. Free, with a fixed quote in hours.
Don't have a spec yet? Send a one-paragraph description — we'll come back with the questions worth asking. Send a description →
draft page
This case is single-page. The same discipline scales to multi-page.
Homepage Redesign and Multi-Page Redesign share the same core methodology — Figma-led, tool-ecosystem-matched, draft-first. Scale differs; discipline does not.