Figma to WordPress, coded by hand
Send a finished Figma file and get back a WordPress theme built to match it, with no page-builder kit underneath it.
The same terms on every job
NDA signed first
Before designs, file access or a client’s name reach me.
No contact with your client
Questions, staging links and notes come to you, and stop there.
A fixed price, not an hourly rate
One figure for the build, confirmed before you quote.
What usually happens to a design on its way into WordPress
The build comes back approximate
A bought theme gets bent towards the artwork and a plugin is added for every section it did not anticipate. Spacing and the type scale drift, and the studio spends the review arguing about pixels instead of content.
The gaps get guessed
No mockup answers every case. Drzwi Portal left open what happens when a customer corrects a configured door already in the cart, and the brief left it open too. Guessed quietly, those become rebuilds.
The estimate arrives after you quoted
A number that lands once the build is underway is a number your margin absorbs. You need the figure before your own proposal goes out.
The handover ties the site to somebody
A licence to renew, a key to keep active or a theme author to keep paying leaves your client depending on a third party you never introduced them to.
How a build like this runs
What a Figma-to-WordPress build actually involves, from file format to handover.
Which file formats I work from
Figma is the easiest file to work from. Spacing and the type scale can be read straight off it.
Sketch, XD exports and flat artwork all work too, provided the design itself is finished.
a Figma file with spacing and the type scale readable off it
Sketch files and XD exports
flat artwork, as long as the design is final
the number of unique templates, not the number of pages
What "finished" means
A finished design is one the studio has already agreed on internally.
I do not redraw layouts. A page still under debate inside the studio should stay out of the brief until it settles.
agreed inside the studio before it reaches me
layouts get coded, never redrawn
design and art direction stay with you
a page still being argued about waits for the next brief
What happens with the gaps a mockup leaves
A Figma file rarely answers every case. Drzwi Portal’s design did not say what should happen when a customer wants to correct a configured door already in the cart, and the brief did not answer it either.
Those questions go to the studio in writing, at the start of the build, while the answer is still cheap. None of them get guessed and shipped quietly.
the questions go out in writing, at the start of the build
answers come back from you, never from your client
anything still open is written onto the quote as an assumption
What the agency gets at handover
The theme, the repository and handover notes in plain English, with nothing licensed, keyed or calling back to me.
the theme and the repository
notes written for whoever maintains the site next
no licence to renew and no key to keep active
nothing in the theme header points back to me
What happens instead
The same four points, answered in the order they were raised.
Coded from your file, template by template
The theme is written for this one design, with spacing and the type scale read straight off the file. No builder kit underneath it, and nothing shipping that the design does not use.
Every open question reaches you in week one
The cases the artwork leaves ambiguous go out in writing at the start of the build. The answers come from you, in your own words, and none of them get decided quietly at my end.
One figure before your proposal goes out
Priced from the number of unique templates and how complex they are, with a delivery date alongside it. Anything still open is written onto the quote as an assumption.
Theme, repository, notes, and nothing else
No licence to renew, no key to keep active and nothing calling back to me. The next developer picks the site up without ever hearing my name.
Three builds that started as a design file
Each came in as finished artwork from a studio and went out as a hand-coded WordPress theme, with the content structure agreed before a template was written. Comeco went from the Figma file to a live site in under a month.
About the file and the build
What studios ask once they have decided the coding is going out of house.
From the number of unique templates and how complex each one is, not from the page count. Forty pages built on six templates is a six-template job. Send the file and the date you have promised, and one figure for the whole build comes back before you quote your client.
A detail the artwork always implied gets absorbed. A new template, a new integration or a section redesigned after approval is priced on its own and confirmed before I start it, so it becomes a change order your client pays for rather than a hole in your margin.
ACF on a classic theme for most builds, because it gives editors fields that match the design rather than a canvas they can break it on. Block themes are an option when the client genuinely needs to compose new layouts themselves. Whichever it is, it is written into the quote, not decided quietly halfway through.
I can, and I will ask first. Where a breakpoint is missing from the file I propose how it should behave and wait for your answer in writing, because a mobile layout invented by a developer is the fastest way to lose a review.
Keep reading
Online shops coded from your design
WooCommerce and PrestaShop built to the artwork rather than bent out of a bought store theme, including the views a platform does not hand you.
How I work with a design studio
NDA first, no contact with your client, and a fixed price before you quote. This is what a build with me looks like end to end.
Overflow support for a WordPress build already underway
The deadline is close, the site is half built, and someone else wrote the code so far. Send access to the repository and get help finishing it under your name.
Work I am allowed to show
These are the case studies I am free to show. Most of my work goes out under a studio’s own name, so the full count runs higher than this page. Each one below follows the same structure: what came in, what I built, and what it changed.
Send the Figma file and see what it costs
One figure for the whole build and a delivery date, back before you put a number in front of your client.