29-Page Pediatric Dentistry WordPress Build in 389 Days — White-Label Delivery for a US Marketing Agency

29-page pediatric dentistry WordPress build for a 3-location practice — 153 hours across build, 3 refresh cycles, and a 15-page redesign over 389 days.

End client All Kids Pediatric
Sector Healthcare
Engagement White-label delivery for a US marketing agency specialising in local-business websites
Timeline 389 calendar days
153h across 389 days
www.akasmiles.com · desktop
www.akasmiles.com · mobile

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 →

— The brief

Build the URLs across the agency's templates, wire the conversion primitive, then work the QA backlogs to closure.

The Craft of a Build

68 tickets across 389 days for a three-location pediatric dental practice — a 29-page Elementor build in January 2025, three refresh cycles through May, June, and July, and a 15-page redesign in September, all on one Original Design template across WP Engine. The same team sustained the entire span across 153 hours, closing each phase through the agency’s per-ticket QA gate without re-estimation between stages.

Snapshot

Field Value
End-client industry Healthcare — Pediatric Dentistry
End-client All Kids Pediatric (Charlotte, NC — Arrowood · Plaza Midwood · Indian Trail)
Engagement White-label WordPress build for a US marketing agency specialising in local-business websites
Project Type WordPress build with Elementor on WP Engine, followed by refresh and redesign phases
Scope 29 URLs — homepage, meet the doctors, meet the team, 11 service pages (pediatric dentistry, preventive care, exams, fluoride, sealants, common procedures, emergencies, extractions, fillings, sedation, digital x-rays), 3 location pages, appointment request, patient forms, testimonials, pay my bill, plus supporting pages (what sets us apart, environmentally friendly, office visits, office tour, financial information, FAQs, post-appointment survey, refer-a-friend)
Timeline 389 days (9 Jan 2025 – 2 Feb 2026), delivered on schedule across all phases
Effort 153 hours against a 153-hour estimate — no overrun
Team 7 specialists
Templates 1 template — the agency’s Original Design template applied across all 29 pages
Tech Stack WordPress · Elementor · WP Engine · Square Appointments embeds · Site Checker ( QA plugin)
Delivered 29 URLs built, 49-item launch checklist closed, 13/14 Issues Backlog items worked to Completed, three refresh phases + one 15-page redesign delivered
Engagement cadence 13 agency-raised issues · all closed by handoff
Review rounds ≈21 review rounds across the 389-day calendar window
Launch checklist 49 items, signed off before cutover

The Brief

All Kids Pediatric is a pediatric dental practice in Charlotte, North Carolina, with three office locations serving children and families across the metro area. A US marketing agency specialising in local-business websites managed the full engagement: they owned the design, the content strategy, the hosting setup on WP Engine, and the client relationship. Our scope was to build the initial site, then sustain it through refresh cycles and a mid-year redesign. Every touchpoint with All Kids Pediatric stayed on the agency’s side; we worked the build, the refreshes, and the redesign behind that relationship.

The workbook structured the engagement across 29 active URLs mapped to the agency’s Original Design template. We scoped each sitemap row in hours. The aggregate for the initial build came to roughly 17 hours of direct page work, with the remaining hours across project management, QA, the three refresh phases, and the 15-page redesign. The ask: build all pages, wire the appointment-request form, handle meta and H1 per the sitemap, work through the issues backlog, and close the launch checklist before each phase’s handoff. Design, content, SEO strategy, and client communication remained with the agency.

Risk Context — A pediatric practice site has to speak to two audiences at once: parents making scheduling decisions and children who will see the site before their visit. The agency was hiring a dev partner who would keep the parent-facing information (insurance, financials, location details, appointment booking) accurate across all three offices, while preserving the kid-friendly tone the agency’s design specified. The deeper risk was retention: a dev shop that delivers the initial build and then becomes unresponsive when the agency needs a refresh six months later forces the agency to re-onboard a new team. The 389-day span of this engagement — with refresh cycles in May, June, and July and a redesign in September — is the evidence that the agency did not have to. The same retention model introduced a constraint the initial build had not produced: during the May refresh, working directly on the live production environment triggered Elementor style conflicts and visual regressions that had to be resolved within the same sprint, rather than isolated in a separate pipeline.

How We Did It

1. One template, 29 pages, one pipeline — built for a three-location practice. The site’s 29 pages spread across the agency’s Original Design template: homepage, two team pages (meet the doctors, meet the team), 11 service pages covering the full pediatric dentistry service set, three location pages (Arrowood, Plaza Midwood, Indian Trail), an appointment-request page, and a suite of parent-resource pages (patient forms, financial information, FAQs, office tour, testimonials). Each page was mapped to the template from the sitemap row before build began.

2. Three locations kept distinct on a single template. All three locations share the same Original Design template but require distinct address blocks, embedded maps, and local phone routing. The location pages — and the location-specific references in the contact and appointment-request flows — were built so that a parent searching for the Plaza Midwood office lands on the correct page with the correct address and booking path. The Square Appointments embeds were wired per location so that appointment requests route to the right office scheduler.

3. Spec followed line-for-line, within the hours we scoped. We scoped the per-row hours ourselves before the build and held to them. Where a row carried 8 hours for the homepage and 0.2–0.5 for a standard service page, that was our budget for the row, and the aggregate came in at the agreed hours for each phase.

There is a plain idea underneath this. A sitemap that arrives already costed turns the workbook into the binding agreement, so the developer’s task is to ship inside each row’s allotted hours and leave the per-page pricing settled, not to argue it open again.

4. Three refresh phases and a 15-page redesign, all inside the retained engagement. After the initial build closed in January, the agency returned with refresh work in May (20 hours), June (8 hours), and July (4.3 hours) — content updates, image swaps, and template adjustments. In September, a 15-page redesign phase (18.5 hours including QA) reworked a significant portion of the site against an updated design spec. All phases were tracked in the same Redmine project, worked by the same team, and closed through the same QA loop. When the TrustIndex review widget on the redesigned testimonials page produced a 403 server error on save, we reserved a placeholder area and closed the page build — the widget was re-integrated in a later fix round rather than blocking the full redesign phase.

Working on the live WP Engine environment during the May refresh surfaced Elementor style conflicts that had to be resolved inside the same sprint — elements dropping out, styles overriding each other. The September redesign handled this differently: every page built in drafts, reviewed against the Figma before publishing, so the live site was untouched until the page was agency-cleared. The lesson from May paid for itself in September.

Operational Integrity at handoff

Pre-handoff checks on the 29-URL build covered workbook-to-spec verification across every sitemap row, link integrity (phone tel: markup and PDF paths on patient-forms caught and corrected), trailing-slash parity across all 29 URLs, and Elementor data re-alignment on the seven service pages that had drifted from the shared template during a mid-engagement revision sprint. Pre-handoff QA ran through Site Checker — see how we run QA for the categories and the requirement that nothing ships with an open critical. After handoff the agency reviewed the build on its own tooling, filing findings into the shared backlog for our fix loop to clear before sign-off.

Results

Metric Outcome
URLs built 29 — 1 homepage, 2 team pages, 11 service pages, 3 location pages, 1 appointment request, 1 patient forms, 1 testimonials, 1 pay my bill, and 8 supporting pages
Templates applied 1 / 1 from the agency’s standard library (Original Design applied across all 29 pages)
Launch checklist 49 items signed off across Design / Functionality / Content / SEO
Issues Backlog 13 / 14 closed as Completed
Refresh phases delivered 3 refresh cycles (May, June, July) + 1 15-page redesign (September)
Timeline 389 days across initial build + refresh + redesign phases, delivered on schedule
Effort 153h / 153h estimate — no overrun, no scope creep
Team 7 specialists
Site status Live on WP Engine at https://www.akasmiles.com/ — verified April 2026.

All told: the agency’s 29-URL pediatric dental build shipped on WP Engine, inside the quoted budget, and the same team sustained it through three refresh cycles and a 15-page redesign over the following 11 months — without the agency re-onboarding a new dev partner.

Process

Phase Duration Outcome
Brief & estimation ~1 week Workbook reviewed, staging access confirmed, 29-page scope and 3-location structure agreed
Build phase (pages + templates) ~2 weeks All 29 pages built against the Original Design template; Issues Backlog opened
Post-launch QA and backlog closure ~2 weeks Issues Backlog worked to 13/14 Completed; 49-item launch checklist signed off
Refresh cycles ~3 months (May – Jul) Three refresh phases delivered: content updates, image swaps, template adjustments
15-page redesign ~3 weeks (Sep) Redesign phase scoped, built, and QA’d
Sustained support ongoing through Feb 2026 Fix rounds and minor adjustments as agency requests arrived

Phases overlapped in practice — the refresh cycles were scoped and started without a full re-estimation, which is why the calendar spans 389 days rather than the sum of individual phase estimates.

Team

Delivery team

  • Nikita Tumasevic — build review and QA on initial construction
  • Pavel Sazhin — lead developer across initial build, refresh cycles, and redesign phase
  • Anna Polunina — implementation support and QA
  • Evgeniy Karpov — developer support on refresh and redesign rounds
  • Timur Arbaev — design-vs-build review and pre-handoff QA
  • Natalia Bogatel — QA and project coordination
  • Anton Hersun, — project lead (estimation, agency-side communication, sign-off)

Agency-side project management and client-facing communication remained with the partner agency throughout. All Kids Pediatric dealt with the agency for every approval and revision; our names never reached their inbox. All change requests from the refresh and redesign phases arrived through the same shared backlog channel as the initial build.

For agencies commissioning a white-label WordPress build

On a pediatric dentistry build, the service taxonomy sets the URL architecture and the rankings your team built. For this practice — age-specific recall and treatment tiers; for others — multi-location groups coordinating provider schedules and referral paths. The risks are quiet ones: a new treatment tier added in month six will not fit the URL pattern you approved. Procedure filter pages will drop from the index during content migration. Patient forms will stop wiring data back to the agency’s CRM without triggering an error.

The question to ask a dev partner before committing is not “can you build the pages?” — it is “how exactly will you design the taxonomy so a treatment tier fits without a rebuild?”

Send us a build workbook, a draft sitemap, or your design files. We will walk the URL taxonomy against a realistic practice growth scenario, trace the form and scheduling paths, and return a fixed-hours quote. Free, with a fixed quote in hours.

Request a spec review →

Don't have a spec yet? Send a one-paragraph description — we'll come back with the questions worth asking. Send a description →

Curious if your engagement fits this pattern?

Scroll to Top