33-Page Vascular Template Customisation

Client (end user): Veinology NJ — a vascular and vein-treatment practice serving northern New Jersey
Engagement: White-label template customisation for a US marketing agency
Delivered: November 2025 – February 2026 · 91 days · 86 hours · 33 URLs · on schedule

The Craft of Template Customisation

33 pages for Veinology NJ mapped onto the Glowing template — a four-location vascular practice in northern New Jersey where the Location and Areas We Serve pages had no template equivalents in the source system. The agency handed us a Figma and ACF-pre-populated pages that had to be migrated to Elementor before customisation could start, pushing the estimate from 17.5 h to 25 h mid-build.

The value is speed with consistency — but only if the customisation is disciplined. A dev team that “interprets” the Figma, 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 template customisation executed to the agency’s Figma across a multi-location vascular practice — where the site had to serve four distinct office locations under one brand, each with its own address, phone routing, and local content, all built from the same template set.

Snapshot

The Brief

A US marketing agency delivered a Figma design for Veinology NJ and access to their branded Kinsta template system. The agency had handled the upstream preparation: client-approved design, hosting configuration, and a Google Sheets sitemap with per-page template assignments and content references. Our task was to take that Figma as the single source of truth, map it onto the template page by page across a four-location vascular practice, and sustain the review cycle for as long as it took to reach sign-off.

The ask was operationally precise. Customise every deviation from the template default to match the Figma exactly — across 11 templates applied 33 times, with no design decisions originating on our side. The practice’s service taxonomy spans vein conditions (spider veins, varicose veins, chronic venous disease, venous insufficiency, deep vein thrombosis, restless leg syndrome, leg swelling, leg pain, leg heaviness) and treatments (radiofrequency ablation, EVLT laser treatment, sclerotherapy, cosmetic sclerotherapy, spider vein removal), all mapped to individual service pages under a location-aware URL structure.

The specific risk the agency was managing against was multi-location drift. On a site with four office locations — Paramus, Ridgewood, Fair Lawn, and Glen Rock — each sharing the same template set but requiring unique address blocks, local phone routing, and location-specific imagery, a team that applies template customisations inconsistently creates a fragmented result where one location’s pages look polished and another’s look like placeholders. In a medical practice where patients choose a provider based on proximity and trust signals, that inconsistency is a conversion problem, not a cosmetic one. The agency hired for the discipline to apply the same customisation standard across all 33 pages uniformly, from the homepage to the deepest condition page.

How We Did It

1. Figma-as-contract, template-as-canvas. The Figma file was the design spec. The branded template was the underlying page structure. Our job was to reconcile the two page by page — where the template’s default layout matched the Figma, we kept it; where the Figma required a deviation (location-specific hero imagery, condition-specific content blocks, doctor-bio card layouts), we customised. No design decisions originated on our side. Several pages had been pre-created in the agency’s ACF-based template structure before the project was handed to us; remapping those into Elementor page-scoped customisations rather than rebuilding from the shared template added an upstream audit pass that the initial estimate did not account for.

2. Multi-location discipline, one template set. Veinology NJ’s four locations each carried its own landing page and its own address block across the shared template. The location pages — Paramus, Ridgewood, Fair Lawn, Glen Rock — were built from the same Location template but with distinct local content: address, phone, embedded map, and office photography. The Areas We Serve page tied the four locations together under a single geographic framework. Keeping the location-specific customisations in the per-page override layer, not in the shared template, meant that a change to one location did not leak into the others.

3. QA cycle at template-customisation scale. A clean template customisation is not “build once, review once”. It is “build, QA, adjust, QA, adjust”. The agency tracked 470 individual issues across two backlog tabs in the shared workspace — 235 SEO findings and 236 CX findings — every one of which was assigned, addressed, and closed only on agency sign-off. This volume is not a sign of instability; it is the discipline that separates a templated site that looks “roughly right” from one that matches the design.

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.

4. 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 Figma reference. Condition-page content blocks, location-address widgets, and doctor-bio card layouts were customised inside the page scope, not in the shared template. We chose page-scoped customisation over shared template overrides because the agency’s template system served multiple client sites; modifying the shared layer for a single vascular practice would have propagated unrelated design changes to the next build on that template. This project’s work did not degrade the template for the next site it would serve.

5. 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.

Several service pages had been pre-built in ACF before the project reached us; remapping them into Elementor page-scoped customisations, not shared template components, added an upstream audit pass the initial estimate did not include. That pass is what kept the multi-location overrides contained — once every page was in Elementor scope, Paramus, Ridgewood, Fair Lawn, and Glen Rock each carried independent address blocks, phone routing, and local imagery without touching the shared layer.

Operational Integrity at handoff

Three QA findings on this engagement: Google Maps on location pages resolved as США (Cyrillic for “USA”) — caught on Fair Lawn and Paramus pages, fixed across all four locations; RankMath site name still read dental-template10 from the source template, updated before launch; and thin-text styling had drifted from the Figma on several condition pages, reconciled in a cross-site pass. 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.

AutoQA gates (Phone-Number / Links / Email / Content-AI / visual) — agency-managed — were configured on this project and ran post-handoff as part of the agency’s sign-off process.

Results

The outcome, restated plainly: the agency’s Figma was implemented against their branded template across 33 pages and 11 templates, over 91 calendar days, inside the 86-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 Figma-to-layout mapping)
• Pavel Sazhin — QA iterations and fixes
• Anna Polunina — template customisation support and QA
• Evgeniy Karpov — development support
• Timur Arbaev — developer support on location-page customisation and later rounds
• Lyudmila Travkina — QA pass and pre-handoff review coordination
• Anton Hersun, xaverPRO — project lead (estimation, agency-side communication, sign-off)

The partner agency retained full ownership of project management, design decisions, and the end-client relationship throughout. The build was invisible to Veinology NJ — every request and sign-off moved through the agency’s shared backlog, and no round was marked closed until their reviewer confirmed it.

For agencies with a branded template system