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 laid out in Illustrator.

The layout looks right on one artboard, but a site needs to work on every screen.

In Webflow

We build it with a fluid layout, and agree tablet and phone before we start.

The brand was made for print first.

Print sizes and colors do not carry over to a screen as they are.

In Webflow

We set type, color and spacing for the web, so the brand reads the same.

Illustrations and icons are part of the design.

Exported as images, they get heavy and blurry.

In Webflow

We export them as clean SVG, light and sharp on every screen.

What moves, what changes

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

In Illustrator

In Webflow

Artboards

Pages built from a component library

Symbols

Webflow components with props

Swatches

Webflow variables for color

Guides and grids

A layout grid that adapts to every screen

Character styles

Typography classes bound to variables

Vector artwork

SVG, light and sharp on every screen

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 Illustrator 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 Illustrator 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
Can you work from an Illustrator file?

Yes. We read the artboards, swatches and type, and export the artwork we need.

02
Our colors are in CMYK. Is that a problem?

No. We convert them for screens and check them with you, so the brand looks the same.

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 design the missing pages?

Yes. If the file covers only some pages, we design the rest from the same system.

Send us your Illustrator file.