Why We Switched Every Client Website to Framer (And Haven't Looked Back)
After years of building on Webflow and WordPress, we moved our entire client workflow to Framer. Here's what changed, what didn't, and why we think it's the most important shift in web design tooling of the last five years.
7 min read
The problem with how most agency websites get built
For years, the standard agency stack looked something like this: design in Figma, hand off to a developer, build in Webflow or WordPress, then spend the next three weeks in a feedback loop trying to make what's live match what was designed. By the time the site launched, something had always been lost in translation.
We accepted this as the cost of doing business. Then we found Framer — and realised the cost was optional.
What Framer actually changes
Framer collapses the gap between design and production. You're not designing a mockup of a website — you're designing the website. What you see in the editor is what goes live, including animations, interactions, and responsive behaviour. For a creative studio that cares obsessively about how things look and move, this is a fundamental shift.
The first project we built fully in Framer took us 40% less time than an equivalent Webflow build. Not because Framer is simpler — it isn't, in many ways it demands more design thinking — but because the iteration cycle is so much faster. You change something and it's changed. No developer relay. No staging environment confusion. No "it looks different in the browser" conversations.
What clients notice
Clients notice the animation quality first. Framer's native motion capabilities are genuinely best-in-class for a no-code tool — scroll-triggered animations, spring physics, gesture interactions — and they're accessible without writing a line of code. The websites we build now move in ways that used to require a dedicated front-end developer and a significantly larger budget.
They also notice the speed. Framer's hosting infrastructure is excellent, and the clean output code means performance scores that would impress any developer. For clients investing in SEO, this matters more than any meta tag optimisation.
The honest limitations
Framer is not the right tool for every project. Complex e-commerce with large product catalogues, custom web applications, or anything requiring deep database logic will need a different stack. Framer's CMS is powerful for content-driven sites but has limits on collection size and field complexity that Webflow handles better at scale.
For the majority of creative agency, portfolio, and marketing site work — which represents most of what studios like ours actually build — Framer is now, without question, our first choice. The quality ceiling is higher, the timeline is shorter, and the final product moves the way good design should.
