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 site was designed in Adobe XD.

Adobe no longer develops XD, and fewer people can work from the file.

In Webflow

We build from the XD file as it is. The design does not need to move to another tool first.

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.

Lists were drawn with Repeat Grid.

Cards, team members or articles exist only as drawings, one by one.

In Webflow

Repeated content becomes a CMS collection your team edits.

What moves, what changes

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

In Adobe XD

In Webflow

Artboards

Pages built from a component library

Components and states

Webflow components with props and variants

Document colors

Webflow variables for color

Stacks and padding

Flexbox and grid, with layout classes

Character styles

Typography classes bound to variables

Auto-Animate

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

Repeat Grid

CMS collections your team edits

What you get

A review of the Adobe XD 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 your team uses to build new pages.

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 Adobe XD 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 we need to move the file to Figma first?

No. We build from the XD file or a shared link.

02
The file is a few years old. Is that a problem?

No. We review it first and tell you what needs an update, such as missing states or old fonts, before we build.

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 you redesign parts of it?

Yes. We can keep the design as it is, or update the pages that need it as part of the project.

Send us your Adobe XD file.