I build Figma / Claude designs in Webflow, including the parts Webflow wasn't built to do.
What you get
The site. Every page in your file, built responsive and checked against the design at each breakpoint it shows.
The parts people edit. A CMS set up around how your team actually publishes, components for repeated sections, and class names a non-developer can follow.
The parts that move or connect. Interactions and Lottie as designed, forms wired to your CRM, analytics, and custom code where Webflow stops.
The parts nobody sees. Fast load times, clean metadata and social previews, alt text, a sitemap, and redirects from the old site.
After launch. Two weeks where I fix anything that turns up, and a walkthrough for whoever edits the site next.
Three recent builds
Village Global. A fund site whose pages open like folders, which Webflow doesn't support, but I came up with a solution.
Grindr. They needed an interactive Careers page with live job listings from Ashby. Webflow has no Ashby integration, so I wrote one.
Sphere. A company history told along an interactive horizontal timeline, with animation tied to scroll.
All three were designed by Carrara and built by me.
"He worked through a complex build like a boss, and pushed hard to meet deadlines. We'll work with him again." — Gonz Sanchez, Carrara
How I work with designers
The design is yours. Before I build anything, I go through the file and send back a short list: states it doesn't show, breakpoints it skips, anything that will behave differently in a browser. You decide, then I build.
If something won't work well on the web, I say so early, while it's cheap to change. I'll send you a staging link so you can follow the progress live, so there are no surprises at the end. I'm easy to reach and quick to reply.
A typical build takes about four weeks: the first goes to reading the file and setting up the system, three to building and connecting, the last few days to quality control and handing over.
I have a computer science degree and I'm a Webflow Premium Partner, so the parts that need real code get real code. I lead the build and do the hard parts myself; my team helps with production.
"Still have never had to ask for any edits or revisions, his work comes out impressively every time." — Brandon Barbash
What I need from you
The Figma or Claude Design file with desktop and mobile frames. Web licenses for any paid fonts. Access to your Webflow workspace, or I build in mine and transfer it. A site plan when you're ready to launch.
I build Figma / Claude designs in Webflow, including the parts Webflow wasn't built to do.
What you get
The site. Every page in your file, built responsive and checked against the design at each breakpoint it shows.
The parts people edit. A CMS set up around how your team actually publishes, components for repeated sections, and class names a non-developer can follow.
The parts that move or connect. Interactions and Lottie as designed, forms wired to your CRM, analytics, and custom code where Webflow stops.
The parts nobody sees. Fast load times, clean metadata and social previews, alt text, a sitemap, and redirects from the old site.
After launch. Two weeks where I fix anything that turns up, and a walkthrough for whoever edits the site next.
Three recent builds
Village Global. A fund site whose pages open like folders, which Webflow doesn't support, but I came up with a solution.
Grindr. They needed an interactive Careers page with live job listings from Ashby. Webflow has no Ashby integration, so I wrote one.
Sphere. A company history told along an interactive horizontal timeline, with animation tied to scroll.
All three were designed by Carrara and built by me.
"He worked through a complex build like a boss, and pushed hard to meet deadlines. We'll work with him again." — Gonz Sanchez, Carrara
How I work with designers
The design is yours. Before I build anything, I go through the file and send back a short list: states it doesn't show, breakpoints it skips, anything that will behave differently in a browser. You decide, then I build.
If something won't work well on the web, I say so early, while it's cheap to change. I'll send you a staging link so you can follow the progress live, so there are no surprises at the end. I'm easy to reach and quick to reply.
A typical build takes about four weeks: the first goes to reading the file and setting up the system, three to building and connecting, the last few days to quality control and handing over.
I have a computer science degree and I'm a Webflow Premium Partner, so the parts that need real code get real code. I lead the build and do the hard parts myself; my team helps with production.
"Still have never had to ask for any edits or revisions, his work comes out impressively every time." — Brandon Barbash
What I need from you
The Figma or Claude Design file with desktop and mobile frames. Web licenses for any paid fonts. Access to your Webflow workspace, or I build in mine and transfer it. A site plan when you're ready to launch.