Coming soon

A studio is on its way.

I am growing my Webflow practice into QDS, a design and development studio. The new site launches soon. Until then, write to me.

[email protected]

Trusted by

Use cases

When this fits

More people need to edit the site.

Editors work around the layout, or ask the designer for every change.

In Webflow

Editors change content in the Webflow editor, inside components that keep the layout intact.

Pages drift apart as the site grows.

Each new page is designed from scratch, and small differences add up.

In Webflow

Variables and a component library keep type, color and spacing the same everywhere.

Content needs more structure.

Case studies, jobs or resources outgrow the setup they started with.

In Webflow

CMS collections with reference fields, filters and their own templates.

What moves, what changes

Each part of your Framer site has a place in Webflow. We map them before the build, so nothing is left behind.

In Framer

In Webflow

Pages

Pages built from a component library

CMS collections

Webflow CMS collections, field by field

Components and variants

Webflow components with props and variants

Breakpoints

Webflow breakpoints, checked on every screen size

Styles and colors

Variables, set once for every page

Effects and interactions

Webflow interactions, rebuilt and tested

URLs

Kept where possible, redirected where not

SEO titles and descriptions

Page settings and CMS fields, carried over or corrected

Media library

Webflow assets, resized and compressed

Forms

Webflow forms, connected to your tools

What you get

An inventory of pages, content, components and forms, with what moves and what is retired.

The site rebuilt in Webflow, with the current design or a new one.

CMS items imported into CMS collections.

Redirects for every old address that changes.

Titles, descriptions and schema carried over or corrected.

A check in Google Search Console after launch.

Included in every project

A design system.

Colors, type and spacing are set once.

A component library.

New pages from sections that already exist.

Structure for search and AI.

Headings, titles and schema at launch.

A handover.

A walkthrough and a guide to editing.

How it works

Step 01

Call.

We look at your Framer site together and talk about what you want to change.

Step 02

Inventory and proposal.

We list pages, content, components and forms, and send the scope and price.

Step 03

Build and import.

We build the site in Webflow and import your content into the CMS.

Step 04

Redirects and testing.

We map every old address and test the site on a staging link.

Step 05

Launch.

We switch the domain and check that old links land on the right page.

Step 06

Check after launch.

We review Google Search Console and fix what it reports.

FAQ

Questions

01
Can you move our content automatically?

CMS content, yes: we export it from Framer and import it into Webflow. Pages and components are rebuilt, because the two tools store layouts differently.

02
What happens to our effects and interactions?

We rebuild them with Webflow interactions. We match the timing and feel, and check them on touch devices.

03
Will our URLs change?

We keep addresses where possible. Where they change, we set up redirects so old links keep working.

04
Can we keep our current design?

Yes. We can rebuild the current design in Webflow, or design a new one as part of the move.

05
How does our team edit content after the move?

In Webflow, on the page or in the CMS. You get a walkthrough and a guide at launch.

06
When can we cancel Framer?

Once the Webflow site is live and the redirects are tested.

Tell us about your Framer site.