Ask a designer who has made the move from "design it and hand it over" to "design it and build it" whether they would go back, and you will get a fairly consistent answer.
It is worth understanding why, because it says something useful about how websites get made now — and about what to look for when you are hiring someone to make yours.
The handoff was always where things got lost
A design file is a description of intent. A website is a set of behaviours. Somewhere between the two, decisions get made that the designer never sees until the site is built.
How does this section reflow at 840px? What happens on hover when there is no hover? Does that heading still work at three lines? A developer answers those questions dozens of times in a build, sensibly, but not necessarily the way the designer would have.
When the same person does both, the number of unanswered questions drops to near zero. Not because anyone is more talented, but because the loop closed.
You can try things instead of specifying them
In Figma, "what if the cards were wider and the gap tighter?" is a change you make, then imagine. In Webflow it is a change you make, then look at, on a real page, at every screen size, with real content in it.
Designers who build tend to iterate more, because iterating got cheap. The third version of a section is usually better than the first, and you only get to the third version if each one takes ten minutes.
Interaction becomes design, not decoration
This is the part designers get most enthusiastic about. In a static file, motion is a note that says "fades in on scroll". In Webflow it is something you design: timing, easing, stagger, what triggers it, what it does on mobile, what it does for someone who has asked for reduced motion.
Once motion is a material you work in rather than a request you make, you use it differently. Usually more sparingly, and with better reasons.
The work is finished when it is finished
A design file is never actually done. It gets approved, and then it gets built, and then it gets adjusted, and the file drifts out of date within a week of launch.
Building your own work means the deliverable is the site. There is no second version of the truth.
What designers have to learn to make it work
It would be dishonest to present this as pure upside. Designers who build well have picked up things that are not design:
Structure. HTML has a semantic order that matters for accessibility and SEO, and it does not always match the visual order.
A class system. Without one, a site becomes unworkable at about page six. Client-First or something like it is not optional.
Performance. Image sizes, how many scripts a page loads, what large animations do to a mid-range Android phone.
Knowing what to hand over. Memberships, payments, API integrations and anything with real security implications are still developer work.
Restraint. Having every effect available is not a reason to use them. A site with three well-chosen moments of motion feels more expensive than one with thirty.
What it means if you are the client
The practical effects are fewer people, fewer handovers and a shorter timeline. It also usually means the person you spoke to about the design is the person who can change it, which makes the revision stage much less painful.
What to check: ask to see something they have designed and built. Look at it on your phone. Resize the window and watch what happens. Tab through it with a keyboard. Sites built by someone who only half made the move tend to fall apart in exactly those places.
How we work
Design and build sit in the same team here, which is why what gets signed off is what gets published. We also take on other people's Figma work regularly, which is a different discipline — respecting someone else's intent while making the hundred small decisions a browser demands.
What to look for in someone who does both
If you are hiring, a few questions separate a designer who genuinely builds from one who has watched a course:
- What class naming system do you use, and why? Any clear answer is a good sign. No answer is a warning.
- How do you handle images? You want to hear about sizing, compression and formats, not "I upload them".
- Show me a CMS you have structured. Look for separate fields rather than one giant rich text box.
- How do you approach accessibility? Contrast, keyboard order and focus states should come up unprompted.
- What would you hand to a developer? Someone who says "nothing" is either exceptional or inexperienced.
Questions we get asked
Is it cheaper to have one person design and build?
Usually, because it removes a handover and a round of corrections. The saving is in time rather than day rate.
What if I already have a designer I like?
That works well. We build other people's designs regularly — it is a large part of what we do for agencies.
Who owns the files?
You should, both the design file and the Webflow project. Make sure that is written down before the project starts.
If you have a design waiting to be built, or a site that never quite matched the file it came from, we are happy to take a look.