Clients often come to me with a Figma file and one worry: will the live site actually look like this? It should, and it should load fast and be easy to edit too. This is the process I follow on every build, whether the site ends up in WordPress, Webflow or Next.js.
1. Brief: agree on the goal before the pixels
Before I open the design, I want to know what the site is for. Who visits it, what should they do, and who will update it later? From that I recommend a stack and confirm the scope, the price and the deadline in writing. A clear brief prevents most of the problems that show up at the end of a project.
- Pages and templates needed, and which ones repeat
- Content that the team will edit, so I can plan the CMS fields
- Forms, integrations and anything that needs a backend
- SEO basics: target keywords, existing URLs that must keep working
2. Design: check the Figma file like a developer
If the design is not finished, I design the key screens in Figma first and we polish them together. If it is finished, I review it the way a browser will see it:
- Responsive states. Is there a mobile and tablet version? If not, I propose one before building.
- Components. Buttons, cards and sections that repeat become reusable components, so the site stays consistent.
- Type and spacing. I turn these into a small set of design tokens: a type scale, a spacing scale and colours.
- Assets. Images are exported at the right size and converted to WebP or AVIF.
3. Build: frontend, CMS and backend together
I build the frontend and the content structure at the same time, so the CMS matches what the design needs. In WordPress that means a custom theme with custom post types and fields. In Webflow, CMS collections with sensible templates. In Next.js, typed components fed by a headless CMS or an API.
Clients get a staging link early and regular updates, so they can review real pages in a real browser instead of waiting for a big reveal. Semantic HTML, accessible markup and clean headings go in from the start, not as a fix at the end.
4. Launch: speed, SEO and device checks
Before the site goes live, I run through a launch checklist:
- Performance: Core Web Vitals, image sizes, caching and unused scripts.
- SEO: titles, meta descriptions, Open Graph tags, schema markup, an XML sitemap and robots.txt.
- Redirects from old URLs, so existing rankings are not lost.
- Testing on real phones and the main browsers.
- Forms and integrations tested end to end.
Then I deploy, connect Google Search Console and hand over a short guide so the team can manage the site on their own.
A Figma design is a promise. The build is where you keep it.
Want your design built?
If you have a Figma, XD or PSD file ready, send it over. I'll recommend the right stack and give you a clear quote. You can also read how I choose between WordPress, Webflow and Next.js.