Real white-label.
I work inside the agency process, under your brand. The end client never knows I exist.
Freelance WordPress developer for agencies.
Design to code —I build from scratch, from Figma or an approved design — Bricks, Gutenberg, Elementor. Precise implementation, QA and a handoff your team can pick up.
Support —When the project is already running I take over the technical work, close the open issues and keep it moving without slowing designers or the internal team.
An approved design is only half the work.
The other half is everything Figma does not show: states, edge cases, performance, editable fields, the colleague who has to update the page six months from now. That is where I come in. I work remotely as a freelance WordPress developer for agencies, white-label. I bring 20+ years of frontend and 8+ years on WordPress into every build I hand over. With agencies I stay behind the scenes, under your brand, or join the technical calls: whoever hands me the project decides.
The projects I take on, how I work with agencies, when it makes sense to call me.
Last updated: 29 July 2026
// typical situations
The design is approved. The site is not.
The file is ready, the build is not. The project sits between pending reviews and a launch date that keeps sliding.
The project manager is chasing responsive fixes.
Breakpoints, forms, plugins, refinements. The time of the people who should move the project forward goes there.
Open issues pile up.
No single task looks big. Together they hold delivery still for weeks.
You need one more person, not one more process.
I step into the workflow you already have, white-label. No extra alignment calls.
I build and I unblock.
I step in on approved designs to build, and on running projects to carry home: custom plugins, open issues, pre-launch review.
Twenty years that show up in delivery.
Frontend since 2006, WordPress for eight years. It shows in the detail of the builds and in how they are structured for whoever inherits them.
I step in without slowing you down.
I work best with an approved design and clear priorities. But I also step in when there is technical work backed up, without taking control of the project away from you.
When it makes sense.
It works when
- The design is approved and the scope is clear.
- The agency holds the client. I hold the execution.
- You need to move forward, not another person to manage.
An approved design sitting still, or issues that never close?
Send me a few lines. I tell you the same day whether and how I can step in.
What I take on.
Four blocks of work. I take them defined and carry them through to delivery, with visible progress and no constant supervision.
- 01View service
I build from scratch, or from your Figma
Bricks, Gutenberg, Elementor. Precise implementation, reusable components, no shortcuts you pay for later in maintenance.
Design to codeFigma, XD or PSD - 02View service
I close the open issues
I step into a running project, work out what is really blocking delivery and close it. Without rewriting everything on principle.
UnblockClear work blocks - 03View service
Plugins, forms, integrations
Custom fields, APIs, booking or e-commerce logic. Code that holds when the client grows.
CustomACF and WooCommerce - 04View service
QA and a delivery that is ready
Responsive, Core Web Vitals, on-page SEO, written handoff. You hand it to the client with your back covered.
Pre-launch360 / 768 / 1440
WordPress project already running?
No formal paperwork. Context, project stage and deadline are enough.
How I work.
A real case · Hospitality · Design-to-code · WordPress · SEO
Casa Carla. Multilingual WordPress Hospitality Website
End-to-end WordPress development from the agency's Adobe XD design: custom theme, Elementor templates, ACF fields, SEO and launch for a holiday apartment website in Italian, English and German.
01
File review
Design, constraints, builder, who maintains the site afterwards. I tell you straight away what does not hold.
02
Block estimate
I break the work into blocks, priorities, risks. You know what costs what before a line of code is written.
03
Build on staging
Visible progress every day. Reviews on the live build, no surprises at the end.
04
Delivery and handoff
Checklist closed, short documentation. The team knows where to put its hands.
Frequently asked questions about how I work.
Short answers, before we start.
How much does the collaboration cost?
I read what you send, break the work down and propose either an hourly rate or a block estimate, depending on how defined the scope is. Scope closes before work starts. No hidden costs, no surprises halfway through.
Do you really work white-label?
Yes. The end client stays yours: I only speak to whoever assigns me the project, I use your channels and every deliverable is presentable under your brand. The end client never knows I exist.
Do you also handle performance work?
Yes. On every build I watch Core Web Vitals, asset weight, builder output and theme structure. On a live site I work on caching, images, fonts and code to bring the metrics back into the expected ranges.
Who handles maintenance after delivery?
Delivery is built to be maintained by your team without depending on me. If you prefer, I handle routine maintenance in agreed blocks: updates, technical fixes and small evolutionary work.
How does handoff to the internal team work?
I deliver on staging with a readable structure: plainly named components, documented ACF fields, reusable templates and notes for editors and developers. The team knows where to put its hands before go-live.
Which tools do you use, and how long does a project take?
Bricks, Gutenberg and Elementor, plus custom plugins when the logic goes beyond what a builder covers. An approved-design build usually takes a few weeks. Open issues close in blocks, on shorter deadlines.
Further reading
Contact
Send me the project.
Where you are, what is missing, when it needs to be online. I reply within 24 working hours — even just to tell you I am not the right person.