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 Photoshop.

Each page is a fixed image, and 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 same parts are drawn again on every page.

Small differences add up, and the site drifts from page to page.

In Webflow

We find the parts that repeat and build them once, as components.

The design relies on large images.

Images exported at full size make pages slow on a phone.

In Webflow

Images are resized and compressed, so pages load fast.

What moves, what changes

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

In Photoshop

In Webflow

Artboards

Pages built from a component library

Smart objects

Webflow components with props

Swatches

Webflow variables for color

Layer groups

Sections and layout classes

Character styles

Typography classes bound to variables

Layer styles and effects

CSS, where a browser can draw it

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 Photoshop 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 Photoshop 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 a PSD?

Yes. We read the layers, type and colors, and export the images we need.

02
Do you need every page designed?

No. If the file covers the main pages, we build the rest from the same components.

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
Will effects like shadows and blends look the same?

Most can be drawn by the browser. Where one cannot, we export it as an image or propose a close match.

Send us your Photoshop file.