6-Ticket Endodontics Refresh in 83 Days — White-Label Delivery for a US Marketing Agency
A 6-ticket endodontics website refresh delivered in 83 days — homepage redesign built from Figma on staging, pushed live, ~19h across 6 tickets.
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 →
Carry the balance of a live-site refresh — small tickets, agency cadence, no regressions on parts of the site the agency did not ask to touch.
The Craft of a Refresh
Six tickets across 83 days for a US endodontics practice — a homepage redesign built on a WP Engine staging environment where Elementor Pro was available, then promoted to a production site where it was not. The team had to reassemble the header, footer, and homepage from the staging build rather than migrating them directly, working from draft to live on the agency’s sign-off cadence: design in March, execute in May, three micro-fixes in June.
Snapshot
| Field | Value |
|---|---|
| End-client industry | Healthcare — Dental (Endodontics) |
| End-client | Burien Endodontics (US endodontics practice) |
| Engagement | White-label refresh-and-maintain workflow for a US marketing agency specialising in local-business websites |
| Project Type | Live-site refresh — homepage redesign on staging, migration to production, image updates, web fixes, UI change requests |
| Scope | 6 tickets — homepage redesign from Figma, QA pass, web-issue fix, image edit, live-site execution, post-migration fixes |
| Timeline | 83 days (27 Mar – 18 Jun 2025), on the agency’s cadence |
| Effort | ~19 hours across 6 tickets |
| Team | 6 specialists — developer + QA + project lead; no dedicated strategist (none needed for a refresh of this scale) |
| Templates | Homepage built against the agency’s existing dental template system; no net-new templates introduced |
| Tech Stack | WordPress · Elementor · Elementor Pro · Gravity Forms · Rank Math SEO · Redirection · WP Engine · Site Checker (xaverPRO QA plugin) |
| Delivered | Homepage refresh shipped live, 6 tickets closed, footer and navigation verified consistent, site returning HTTP 200 |
| Review rounds | ≈4 review rounds across the 83-day calendar window |
The Brief
A US marketing agency retained by Burien Endodontics — an endodontics practice in the Burien, WA area — needed a development partner to refresh the practice’s homepage and carry a small set of follow-on changes. The homepage redesign was approved in Figma and needed to be built on staging, reviewed, and then promoted to the live site without downtime or patient-facing disruption.
After the homepage went live, the engagement continued as a steady drip of small change requests — a web-issue fix from a client document, a hero-image swap, a doctor-image replacement, and a set of post-migration touch-ups (phone-link correction, menu cleanup, responsive overlap fix, View All link routing). Each change request was raised in Redmine, developed on staging or directly on the live site as appropriate, and closed through the agency’s sign-off.
The ask, expressed simply: work carefully on a live surface — refresh the homepage against the approved Figma, migrate it to production without downtime, and carry the follow-on tickets one at a time without destabilising the site.
Risk Context — homepage-as-gateway refresh on a specialty dental practice
On an endodontics practice site, the homepage is the single highest-traffic page and the primary patient-acquisition surface. It is already indexed for local search, already receiving direct traffic from referral networks, already routing appointment requests. Refreshing the homepage — swapping the hero image, resizing the logo on scroll, restructuring sections — carries a concentrated risk: a broken booking link, a mis-routed phone number, or a responsive overlap at 1280 px means a potential patient bounces before they ever see the refreshed design. The value being sold is not the redesign itself — it is refreshing the highest-stakes page without introducing regressions that the practice would discover from missed appointment calls. The engagement had no workbook or structured spec; each follow-on ticket was scoped from a brief description rather than a pre-agreed backlog, so every change carried the risk of surfacing undocumented requirements at the agency’s response cadence rather than against a fixed sitemap.
Operational Integrity at handoff
Staging QA on the homepage refresh caught a mobile logo animation regression — the shrink-on-scroll behaviour worked at desktop breakpoints but broke at mobile, flagged in the QA pass, which we resolved before clearing the page for production. Post-migration QA surfaced 3 micro-issues, including a navigation menu link correction, before the agency signed off. Pre-ticket-close QA ran through Site Checker — see how we run QA for the categories and the no-fail bar each ticket had to clear. After handoff the agency ran its own QA, surfacing issues into the shared backlog for our fix loop until they signed off on each ticket.
How We Did It
1. Homepage redesign built against Figma on staging. The agency supplied an approved Figma frame for the new homepage. Vladimir Kozlov built the redesign on the WP Engine staging environment — hero section, logo shrink-on-scroll behaviour, refreshed footer, and updated navigation — keeping every element traceable to the Figma spec. The staging site was the only surface touched until the agency signed off. We chose staging-first over live edits because a partially-refreshed homepage visible to search engines mid-build would have served patients an inconsistent brand message across the practice’s primary patient-acquisition surface.
2. QA pass before live promotion. Pavel Sazhin ran QA against the staging homepage — verifying Figma fidelity, responsive behaviour, logo animation, and navigation consistency — before the page was cleared for production migration. The principle: a live-site refresh is never pushed until the agency has reviewed and approved the staging build.
3. Live-site execution and post-migration cleanup. After agency sign-off, we promoted the homepage to the live site. A separate ticket tracked the migration itself — staging → production — with a verification checklist covering header/footer consistency, navigation functionality, and form routing. Post-migration, a set of small fixes closed cleanly: a responsive overlap at 1280 px on the “A Step Above the Rest” section, an incorrect tel: link in the footer, a redundant “Home” menu item, and a View All link routed to the correct endodontics lander.
4. Change requests handled one at a time — 6 tickets across 83 days. Tickets came through Redmine on the agency’s cadence — “Fix Web Issue as Noted in Document”, “Image Edit — Burien Endodontics | Website Refresh”, “Execute Live Website”, “Migrate to Production and Resolve Issues”. Each ticket was scoped, developed, QA’d internally through Site Checker, returned to the agency, and closed on their sign-off. The average ticket consumed roughly 3 hours — the characteristic profile of a small-scale refresh where the homepage redesign carries the bulk of the effort and the follow-ons are surgical.
Working without Elementor Pro on the production site meant the header, footer, and homepage could not migrate directly from staging — the team rebuilt each element by hand against the staging reference rather than import it. That constraint produced a cleaner production build: every element was re-verified against the Figma spec during reassembly, not assumed to have transferred correctly.
Results
| Metric | Outcome |
|---|---|
| Change requests delivered | 6 tickets closed across the 83-day engagement |
| Homepage refresh | Shipped — Figma-implemented homepage promoted from staging to live |
| New images applied | Hero image and doctor image swapped per agency-approved assets |
| Site Checker QA gate | Ran before every individual ticket close — nothing shipped with an open flag |
| Post-migration fixes | 4 items closed: responsive overlap, footer phone link, menu cleanup, View All routing |
| Timeline | 83 days, delivered on the agency’s cadence |
| Effort | ~19 hours total across 6 tickets |
| Site status | Live at https://burienendo.com/. |
Boiled down: we built the agency’s homepage redesign on staging, QA’d it, promoted it to production, and followed with a set of small change requests — all closed individually through Site Checker pre-ticket-close QA and agency sign-off across 83 calendar days.
Process
| Phase | Duration | Outcome |
|---|---|---|
| Initial brief + scoping | ~1 week | Figma reviewed; staging environment confirmed; homepage scope agreed |
| Homepage redesign (staging) | ~2 weeks | Full homepage implemented in Elementor Pro on WP Engine staging |
| QA + agency review | ~1 week | Staging homepage verified against Figma; agency sign-off received |
| Live-site execution | ~1 week | Homepage promoted to production; migration checklist completed |
| Change-request cadence | ~10 weeks | 5 follow-on tickets triaged and closed one at a time; each through Site Checker pre-close QA + agency post-handoff sign-off |
Phases overlap — change requests kept arriving after the homepage went live, and the post-migration fix round ran in parallel with the agency’s own QA review. This overlap is the characteristic shape of refresh work.
Team
Delivery team
- Nikita Tumasevic — developer on image edits and web-issue fixes
- Pavel Sazhin — QA on staging review and post-migration verification
- Anna Polunina — implementation support and QA
- Vladimir Kozlov — developer on homepage redesign and follow-on changes
- Evgeniy Karpov — development support
- Anton Hersun, xaverPRO — project lead (estimation, agency-side communication, sign-off)
Agency-side project management, design approval, and client-facing communication remained with the partner agency throughout. To Burien Endodontics, the refreshed homepage simply arrived from their marketing agency — our developers and QA never appeared in a single thread, call, or sign-off.
For agencies commissioning a white-label WordPress refresh
On an endodontic practice site, a design refresh looks simple until it touches the clinical pages carrying the agency’s rankings. For this practice—single-specialty endodontics with surgical pages; for others—general family dentistry built on routine exams. The quiet risks: colour and typography changes propagate inconsistently—the header looks new, but the surgical treatment pages still carry the old palette. Three small tickets creep into full design work as the visual updates expose gaps in the information architecture.
The real question before committing is not “can you refresh the design?” — it is “how will you contain the scope and cascade the colour changes so no pages get left on the old palette?”
Send us a backlog or the issue tracker for the work you have in mind. We will review the scope against the current site’s taxonomy, flag the tickets that will propagate unevenly or expose deeper gaps, 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 →