How to hire a WordPress developer: a checklist for businesses and agencies
What to ask, what to check in a portfolio, and how to scope a project so quotes are comparable.
Read the articlefigma → wordpress

This Figma to WordPress checklist is what I wish every design file came with. A good handover is the difference between a build that matches your design on every screen and one that only matches it on the screen you designed for. None of it is hard, but it’s easy to skip when a deadline is close.
Developers build from your styles, so make them complete and use them everywhere:
If a colour or font size appears outside the styles, the developer has to guess whether it’s intentional.
Buttons, cards, form fields and sections should be components with variants for each state: hover, focus, disabled and error. Components map naturally onto WordPress: a reusable block, an Elementor template or a theme part. Repeated sections that aren’t components often end up built twice, slightly differently.
Show at least desktop and mobile for every page type, and tablet for anything complex such as menus, tables and product grids. Note what happens in between: does a three-column grid become two or one? Does the menu become a burger, and at what width?
The last point matters most. A pixel-perfect site the client can’t update without a developer isn’t finished.
For The Rooted Daughter Collective the whole site was designed in Figma, from the homepage to checkout, then built in WordPress with Elementor and WooCommerce, with tools so the owner manages her own products. For Indigo Ag the same idea applied in HubSpot: each Figma section became a reusable module the marketing team edits themselves.
In both cases, a clear Figma file made the build faster and the result closer to the design.
Almost always, yes. The cleaner the file, with styles, components and breakpoints, the closer and faster the build.
Both can match a design exactly. Elementor suits teams that want to edit layouts visually; a custom theme suits sites that need tighter control and speed. Decide based on who will edit the site.
Yes, at least for every page type. Without it, the developer decides how your design adapts, and it may not be what you'd choose.
hire( wordpress_developer )
What to ask, what to check in a portfolio, and how to scope a project so quotes are comparable.
Read the articlewoo → quickbooks.sync()
When an off-the-shelf connector is enough, and when a custom OAuth 2.0 sync pays for itself.
Read the articleghl vs hubspot
A developer's comparison of features, integrations and automation, from real client set-ups.
Read the articleSend me the Figma link. I'll check it against this list and reply with any questions and a clear quote.
Cookies on this site
I use necessary cookies to make this site work. With your permission, I'd also like to use analytics cookies to see which pages are useful, and marketing cookies to measure any advertising. Privacy policy
Choose which cookies you're happy for me to use. Necessary cookies are always on. You can change your choice at any time with the "Cookie settings" link at the bottom of every page. Privacy policy
Needed for the site to work, for example to remember your cookie choice (yl_consent) and keep the project form secure. They can't be switched off.
Help me understand how visitors use the site, so I can improve it (Google Analytics: _ga, _ga_*). The information is grouped and doesn't identify you.
Let me measure advertising and show more relevant ads on other websites (Google Ads: _gcl_au).