Webflow Builds, Figma to Live
Client websites designed in Figma and shipped in Webflow by the same person, with no developer hand-off in between.
- Role
- Design + build
- Where
- Remedo · healthcare & health-tech clients
- Tools
- Figma · Webflow · Webflow CMS · GSAP
sites built from scratch + major redesigns, for 8 clients
No developer hand-off between the Figma file and live production.
The problem
Healthcare and health-tech clients in the UK and USA needed production websites, and a growing platform needed pages for more and more hospital and clinic locations.
The conventional route is a designer handing a Figma file to a developer, with design drift and a maintenance queue as the side effects. For location pages it also means every new location becomes another development ticket.
The approach
Own the whole pipeline: wireframes and high-fidelity design in Figma, then the production build directly in Webflow, with responsive layouts and GSAP animation. There's no separate developer translating the design, so nothing gets lost or reinterpreted along the way. Builds go through both Figma → Webflow and Claude → Webflow workflows.
For the multi-location platform, architected the Webflow CMS collections the location pages run on, spanning 50–100 pages. Each location page is generated from structured CMS data on a shared template, so a new location is a content-entry task rather than a new build.
Impact
- 50–100 location pages on one CMS structure, so location growth is content entry, not repeated development work.