A published component library, not a page of rectangles
A real component gets built once and reused. Detached copies make every instance a decision I have to make on your behalf, and their differences are invisible to me.
Your design stays exact: every component you drew becomes a component in the code, your content team can edit it, and the page still loads fast. No page builder pouring it into someone else's markup.
Trusted by development & marketing teams at
A real component gets built once and reused. Detached copies make every instance a decision I have to make on your behalf, and their differences are invisible to me.
A card with tier and featured properties becomes one template. Six detached copies become six templates.
Default, hover, disabled map straight to CSS. “Frame 214” maps to nothing.
Styles become the theme's design tokens. Loose hex values become forty near-identical greys.
I read the file, list the components and flag what is ambiguous. This is where the quote comes from.
Your components as real markup, matched to the design rather than approximated by a builder.
Template parts and a token layer, so the second page costs a fraction of the first.
Every piece of text and every image gets its own labelled field. Nothing your team edits is hardcoded.
Heading structure, schema and metadata built in, not bolted on by a plugin later.
Escaped output, a minimal plugin surface, and a build that survives core updates.
Real devices, real content, Core Web Vitals checked before launch rather than after.
www.forter.com
Fraud-prevention platform.
Built: theme development and localisation.
www.tasc-consulting.com
Management consulting firm.
Built: custom theme and performance work.
storyboards.io
Video collaboration platform.
Built: the custom WordPress theme.
www.gn-law.co.il
Medical negligence litigation firm.
Built: the theme from the Figma file, plus a 301-article migration. Read the rebuild.
He does precise work, taking designs and creating ultra-fast WordPress pages accordingly.
Limor AlmagorMARCOM at Onebeat.co
I had the chance to work with Roee on a collaboration project, where Roee produced a high quality and fast turn-around WordPress based website.
Vova NurenbergProduct Design Manager at Meta
Built for your design, with no unused framework code shipped to the browser.
Labelled fields, not one editor box. Marketing changes copy without a ticket.
No builder overhead to optimize away later.
Semantic structure and schema in the templates from day one.
The read and the quote cost nothing. If the file is not ready, I will tell you what to fix rather than quote around it.
The guide on component properties and Code Connect covers what I look for, written for designers.
Not the question you had? Send it over and I will answer it.
Ask on WhatsAppNo, but I need it to be real. A file still in flux is fine; a file where half the screens are screenshots pasted in is not, because there is nothing underneath to build from.
Sketch, XD and a well-organised set of exports all work. Figma is easiest because I can read the components and their properties directly rather than measuring pictures. If what you have is a generated app from v0, Lovable or Bolt rather than a design, that is the vibe code to WordPress rebuild instead.
Yes. Every piece of content sits in a labelled field rather than in one editor box, so changing a heading or swapping an image does not need a developer.
I can, and sometimes it is the right call for a small site. When you have invested in a design, a custom theme stays closer to it and loads faster, which is why it is the default here.
A link and a sentence about what the site needs to do is enough to start. The file does not have to be finished yet.
Replies usually within an hour.