Your approved design, applied verbatim
to the existing live site.

A Refresh re-dresses an existing live site in a new design, preserving every URL, every piece of content, and the navigation structure. The agency supplies the approved Figma; we implement it on staging — template by template, with per-page exceptions where the design calls for them — verify parity with the live site, and promote on cutover. The primary deliverable is the design itself; modification tickets after the swap are an optional follow-on engagement, not part of the core scope.

A Redesign typically changes more than visuals — page structure may shift, templates may be added or removed, content can be reorganised; the brief is "rethink this site." A Refresh's brief is narrower: keep everything the same, change how it looks. URLs, sitemap, copy, and navigation come through the engagement unchanged; the agency-supplied design is applied verbatim. If you need structural changes, that's a Redesign engagement — we'll re-scope at intake rather than discover the mismatch mid-build.

Materially safer — by construction, nothing on the indexable surface changes. URLs stay the same, page titles and meta descriptions stay verbatim unless the new design explicitly changes copy on a page. We run a Screaming Frog crawl before and after the design swap to confirm zero structural drift. The ranking outcome remains yours to own and measure, but a Refresh removes the migration-related categories of risk that a full Rebuild carries (redirect-map errors, broken internal links, accidental noindex, content drift).

By template count, primarily. A site with 100 pages built on 10 templates is a 10-template Refresh; we re-dress each template once, and the visual change propagates to every page using it. Per-page work happens only where the new design includes page-specific elements — a hero variant, a custom block on the About page, a calculator component on a single landing page. We quote on the template count plus identified per-page exceptions, not on raw URL count.

Yes, as an optional follow-on engagement. Once the design swap is complete and signed off, modification tickets — copy changes, new sections, small layout tweaks, content updates — can be processed against the live site one at a time. Each ticket gets an hours estimate before work starts; the payer (agency manager or end client) decides which to proceed with; Site Checker runs before each close. There's no fixed retainer cadence — tickets land when the agency sends them, and the running total matches what's invoiced.