Why I build websites in code, not Figma
The code-first approach saves weeks and delivers better results. Here's how skipping the mockup stage actually works.
When a client hires an agency, here's what usually happens: a designer spends 1–2 weeks in Figma, the client reviews static screens, then a developer rebuilds everything from scratch. The mockup and the final product are two different things.
I skip the middleman. I go straight to code. Within hours, you see a real website — with animations, responsive layout, and working buttons — on your actual phone.
Why this works better
Speed. A Figma mockup takes 1–2 weeks. I deliver a working site in 1–2 days. The client sees results immediately, and we iterate on something real.
Accuracy. A mockup lies. It doesn't show how text reflows on mobile, how animations feel at 60fps, or how a button responds to a tap. Code tells the truth.
Cost. No design phase means no design budget. The client pays once for the final product, not twice for a picture and then a build.
When does this NOT work?
Large teams with multiple stakeholders who need to sign off on visuals before development. Enterprise projects with design systems that require Figma documentation. Those are valid use cases for mockups.
But if you're a business owner who needs a website that converts — you don't need a picture of a website. You need the website.
The stack
I use Next.js, TypeScript, Tailwind CSS, and GSAP. The browser is my canvas. Every design decision is made in the medium where it will actually live.
The result? You get a live product in one day. Not a mockup. Not a prototype. A website that works.