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

Your team designed the site and needs it built.

The design is ready, but the build still has to be planned, quoted and scheduled.

In Webflow

We build from your file. You review each page on a staging link as we go.

The design has no plan for tablet and phone.

Gaps show up late, when the build is almost done.

In Webflow

We review the file first and agree every breakpoint before we build.

Your agency designs, but does not build in Webflow.

Notes get lost between the design and the build.

In Webflow

We work from your agency's files and ask them when something is unclear.

What moves, what changes

Each part of your Figma file has a place in Webflow. We map them before the build, so the site matches the design.

In Figma

In Webflow

Frames

Pages built from a component library

Components and variants

Webflow components with props and variants

Variables

Webflow variables for color, type and spacing

Auto layout

Flexbox and grid, with layout classes

Text styles

Typography classes bound to variables

Prototype interactions

Webflow interactions, rebuilt and tested

Breakpoints

Desktop, tablet and phone, each one checked

Images and icons

Compressed images and SVG icons

Fonts

Web fonts, loaded once for the whole site

Repeated content

CMS collections your team edits

What you get

A review of the Figma file before the build: what needs a decision for tablet, phone and the CMS.

The build in Webflow, matching the design on every screen size.

A component library that follows your Figma components.

Variables for color, type and spacing, so every page stays consistent.

Interactions and animations as specified.

Launch, and a handover to your team.

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

Send the file.

Share the Figma file. We look at the pages, the parts that repeat and the styles.

Step 02

Review and proposal.

We list what needs a decision and send the scope and price.

Step 03

Foundations.

We set up variables, typography and the component library.

Step 04

Build and review.

We build the pages. You review them on a staging link as we go.

Step 05

Launch.

We connect your domain and check every page after launch.

Step 06

Handover.

Your team gets a walkthrough and a guide to editing the site.

FAQ

Questions

01
Do you use a Figma to Webflow plugin?

We build by hand, from your file. A plugin can help with a first pass, but a hand build gives cleaner classes and a site your team can edit.

02
What access do you need to the file?

View access is enough. Dev Mode helps, but it is not required.

03
What if the file has no tablet or phone designs?

We propose those layouts from your desktop design and your components. You approve them before we build.

04
Will the site match the design?

Yes, on every screen size. Where a browser behaves differently from the file, we tell you before we decide.

05
How does our team edit content after launch?

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

06
Can our agency keep doing the design?

Yes. We build from their files and work with them during the build.

Send us your Figma file.