26-Page Dental Template Customisation

Client (end user): Floss Lincoln Park — a US dental practice
Engagement: White-label template customisation for a US marketing agency
Delivered: June 2025 · 82 days · 24 hours · 26 URLs · on schedule

The Craft of Template Customisation

26 pages of Floss Lincoln Park built in two acts: a template scaffold deployed first, then a re-estimate when branding and copy arrived 17 days later. Phase 1 set the architecture; Phase 2 integrated content that had been written without reference to the template’s section structure. The 82-day span, 5 templates, and 93 QA items reflect what it takes to reconcile an independently-authored content brief against a live template without drift.

The value is speed with consistency — but only if the customisation is disciplined. A dev team that “interprets” the design, skips QA rounds, or deviates from the template’s design system is worse than starting from scratch.

This case study is a record of a two-phase template customisation: scaffold built before content existed, then re-estimated and populated once branding and copy arrived.

Snapshot

The Brief

A US marketing agency delivered us a template customisation brief for Floss Lincoln Park — a new dental practice starting from scratch. The agency was still working on the client’s branding and logo when development began, and website content would be delivered mid-build. The initial scope was to set up the template scaffold; a second phase would populate pages once content arrived.

The ask was sequential in a way that a fixed-scope rebuild is not. Build the template bones first. Wait for content. Re-estimate. Populate pages. Run QA. The 26-page scope was the entry point; the real work was in preserving template integrity while integrating branding and copy that did not exist when the first commit was made. A limitation of the sitemap-driven estimate was that the design files included sections — such as the blog — that had no row in the initial workbook scope, so their templates fell outside the original per-page budget.

What the agency needed to guard against here was a dev shop that equates “template copied” with “done.” On a templated engagement for a new practice — where the client has no live site to regression-check against and no content baseline to verify against — the build is only complete when every page is accurate, every placeholder is stripped, and every QA item has been reconciled. A team that stops iterating when the template looks roughly right leaves the agency carrying a QA backlog they now own. The 93-item backlog on this project is not a sign of rework — it is the record of discipline.

How We Did It

1. Figma-as-contract, template-as-canvas. The agency’s design direction and branded template were the source of truth. Our job was to reconcile the two page by page — where the template’s default layout matched the design, we kept it; where the design required a deviation, we customised. No design decisions originated on our side.

2. QA cycle at template-customisation scale. A clean template customisation is not “build once, review once”. It is “build, QA, adjust, QA, adjust”. Of the 11 tasks tracked on this project, 3 were QA iterations — individual rounds where the agency flagged design deltas, we reviewed, fixed, and returned the build for another review. Behind those rounds was a much larger reconciliation: the agency tracked 93+ items across two issue-backlog tabs (65 SEO findings and 28 AM findings), all of which were reviewed and addressed through the shared fix loop.

The principle behind this is simple: on a templated build, the QA loop is where the value is delivered. A shorter QA cycle is a weaker match to the design, not a faster delivery.

3. Customisation without drift. Every change we made to the branded template — whether to a page layout, a section component, or a style token — was documented against the design reference. No customisation propagated into the agency’s shared template components, which means this project’s changes did not affect any other site built on the same template.

4. Cross-device verification. Customisations were QA’d against Chrome, Firefox, Safari, and Edge on desktop, tablet, and mobile viewports — the standard agency breakpoint set. Each QA round covered the pages affected by that round’s design deltas, not the whole site, which is how a templated build stays efficient without losing coverage. We scoped the build by the workbook sitemap row budget rather than by the full design-file count — unplanned pages were surfaced as separate tasks because the sitemap was the closed-scope contract between the agency and the build team.

The constraint of content arriving after the scaffold was already built forced a specific sequence: set the template bones to a 4-hour estimate, wait for the agency’s content brief, re-estimate at 11 hours when it arrived. That ordering was the discipline — integrating branding and copy into a live scaffold without drifting the template costs more when the content was written without reference to the template’s section structure.

Operational Integrity at handoff

Three QA findings ran the fix loop on this engagement: duplicate meta-description tags (Rank Math emitting one, an Elementor global setting emitting a second) caught and collapsed to one; four Rank Math sitemaps (pages, blog, services, doctors/FAQ) condensed to the two the agency required; and 404s from mid-project slug cleanup — every page where the -info suffix was stripped got a 301 redirect before go-live. Pre-handoff QA ran through Site Checker — see our QA discipline for the categories and the fail-zero gate. The agency’s own QA layer — their tools, their process — ran post-handoff and surfaced issues into the shared backlog for our fix loop until they signed off.

Customisations stayed in the per-client overrides; the agency’s shared template components were not modified.

Results

The outcome, restated plainly: the agency’s template was customised across 26 pages and 5 templates, over 82 calendar days, inside the 24-hour estimate.

Process

Development and QA ran concurrently — this is characteristic of template-customisation work, where no “QA phase” closes cleanly; the loop runs continuously until the agency signs off.

Team

Delivery team

• Nikita Tumasevic — lead developer (template customisation and content integration)
• Anna Polunina — developer (re-estimation and content-phase support)
• Pavel Sazhin — QA iterations and fixes
• Anton Hersun, xaverPRO — project lead (estimation, agency-side communication, sign-off)

The agency held the end-client relationship throughout. All customisation requests moved through the agency’s shared backlog; Floss Lincoln Park did not interact with our team directly. Each iteration round was released only once the agency-side reviewer confirmed the changes were resolved to spec.

For agencies with a branded template system