Formatry

Webflow does not import a design; it has its own box model and its own class system, and everything that looks effortless in Figma has to be reconstructed as a structure that holds. Get that wrong and the site looks right on the day and becomes unmaintainable a month later, when the client adds a page and the classes do not carry. On top of that, this buyer is another agency — technical, time-poor, and quick to judge a production partner by the state of their own site.

I rebuilt the Figma file in Webflow with a class structure meant to be extended rather than one that only satisfies the first page, and modelled everything that changes regularly as CMS collections so new service and industry pages are published by the client rather than by a developer. It went through three rounds of revisions with the agency before sign-off, and I connected and published the custom domain in Webflow rather than handing over a staging URL and a set of instructions.

• Design rebuilt in Webflow rather than approximated
• Regularly changing content modelled as CMS collections
• Three rounds of revisions with the agency before sign-off
• Custom domain connected and published from Webflow

Webflow, because a production partner selling capacity should be publishing case pages themselves rather than queuing behind a build step:

• Webflow
• Webflow CMS
• Custom interactions
• Custom domain

New pages ship without a build step, a deploy, or a developer in the loop, on the client’s own domain. For an agency job that means the handover was genuinely finished: no staging link left open, no DNS ticket, nothing waiting on me.