How Trueform built a Framer web design agency that scales

Framer — author avatar

Framer Team

Published

Trueform designer working at a desk in the agency studio

Trueform grew from freelance projects into a Swiss Framer agency shipping large, CMS-heavy websites. The team explains how keeping design and development in one tool helped it move faster, work at Miro scale, and challenge the idea that Framer is only for landing pages.

Trueform designer working at a desk in the agency studio

Trueform built a scalable Framer web design agency by moving from freelance projects to a small team that designs and ships in the same tool. That workflow helped the Swiss studio grow from a two-person Miro project into a large CMS-driven site, while keeping the handoff between design and development short.

In this Framer Creators video, Sam, Dominik, and Cédric explain how traditional agency handoffs shaped their process, why Miro became a turning point, and what they learned about using Framer at scale.

Start with the work you want more of

Cédric had wanted to work for himself for years. He tried launching 20 to 40 side projects over a decade, but none of them worked at first. Freelance projects created a more useful path: each one built experience, relationships, and a clearer view of the kind of work he wanted to pursue.

The next step was not to build a large agency immediately. It was to find more good people. Sam, Dominik, and Cédric had all completed a traditional apprenticeship in Switzerland, so they shared a baseline for how design work was done. They also shared a frustration with the usual production model.

For a small web design agency, that is a useful starting point. The early goal is not maximum headcount. It is a repeatable kind of work, a team that understands the quality bar, and a process that gets better with each project.

Remove the handoff that keeps breaking the work

At traditional agencies, the Trueform team did most of the design work before passing it to developers. The handoff created a gap between the design they approved and the website that shipped. Details changed. Interactions became harder to reproduce. Pixel-level decisions were separated from the code that made them real.

Framer changed the team’s starting point because design and development could happen in the same project. The designers could build the interaction, test it in context, and adjust it without translating the whole idea for another team.

This is more than a tooling preference. A handoff is also a context handoff. Every time a project moves to another team, someone has to explain what matters, what can change, and what must stay exact. A shared canvas reduces that translation work.

Let a small project prove the model

Trueform’s relationship with Miro started with a small landing page. Cédric worked with a few project managers and Miro’s web lead to ship the first iterations in a team of two. The work expanded because the team proved it could deliver a page that matched the design and keep moving.

That sequence matters. The agency did not need to win a huge transformation project before demonstrating value. A small page gave the client a low-risk way to evaluate the workflow. Once the quality and pace were clear, Trueform could take responsibility for more of the site.

The same approach works for agencies today: start with a contained page or campaign, make the production quality visible, and earn the next layer of responsibility through the work itself.

Design and ship in the same tool

The Trueform team describes Framer as first-class for this kind of work. Its development tools feel native to the design environment, which gives the team what it calls the best of both worlds.

For the Miro site, the team says that around 90% of its build happened directly in Framer without code knowledge. The important part is not a percentage that every agency should copy. The important part is that the people responsible for the design could also make the site work in production.

We do designs in Framer. We ship in Framer.

When those are the same step, the team estimates that it can work about twice as fast as a traditional agency.

Speed comes from fewer translations, not from skipping the craft. The team still has to make good decisions, test responsive layouts, review content, and keep the site maintainable. Framer simply keeps those decisions closer together.

Prove that the CMS can handle the site you actually have

The Miro project became a useful test of scale. The Trueform team describes a site with six-figure traffic, a mix of new and legacy CMS data, and perhaps 50 CMS collections. That is far from the small landing page many people associate with a visual web tool.

The project also had to work with existing data. Part of the site still used the old CMS, and information was shared across the system. Trueform could evaluate Framer against that reality rather than a clean demo project with no history.

For an agency, this is the real scalability question: can the tool support the site’s content model, team, migrations, and publishing habits? A large site is not defined only by page count. It is defined by how many relationships, locales, templates, and updates the team needs to manage without losing control.

Challenge the “landing pages only” assumption

The team hears a recurring concern that Framer is only for landing pages. Its experience with Miro gives it a direct answer. A visual tool can support a large site when the CMS, design system, and production workflow are treated as one system.

That does not mean every project should use the same setup. It means the ceiling should be set by the content model and the team’s needs, not by an assumption that visual tools stop working when a site grows.

Trueform’s current site positions the company as a Framer agency for B2B software startups and enterprises, with services that include marketing sites, enterprise sites, CMS migrations, SEO, and performance work. The video explains where that confidence came from: a small team tested the workflow on a real, demanding site and kept expanding the scope.

What a Framer web design agency can learn from Trueform

Trueform’s story offers five practical principles for a small web design agency:

  • Use freelance work as research. Early projects reveal which clients, problems, and deliverables are worth repeating.

  • Make the handoff visible. If design quality drops during development, bring the build closer to the people who made the design.

  • Prove the process with a small page. A contained project can earn trust before a larger engagement.

  • Treat the CMS as part of the design. Scale depends on content structure, not only on visual polish.

  • Measure speed by coordination removed. The fastest workflow is often the one with fewer translations between teams.

Trueform did not scale by adding layers between design and production. It scaled by making the same team responsible for both, then proving that model on a site with real traffic, legacy data, and a large CMS.

Watch the full Trueform story on YouTube, explore Framer for agencies, or learn more about Framer CMS.

Your next idea starts here

GPT 5.6 Terra

Create personal portfolio

Build startup site

Launch landing page

Start company blog

Framer UI showing Pages, Layers and Assets panels titles
Framer UI showing Pages, Layers and Assets panels titles