White label

A developer
on your team
when you need one.

I build WordPress, Shopify and WooCommerce projects for design, marketing and SEO agencies — under your brand, to your deadlines. Your client never hears my name unless you want them to. Ten years of this, more than a thousand sites, and a good share of them delivered through other agencies.

What lands on my desk

The work agencies hand over most

  1. 01

    WordPress · Elementor

    Design to build

    You sold the design; I turn it into a site. Figma, XD or a flat PDF becomes a custom theme or a clean Elementor build that matches the comp, behaves on every screen size, and hands over an editor your client can actually use.

    • Custom themes
    • Elementor
    • ACF
    • Handover docs
  2. 02

    Shopify · WooCommerce

    Store builds and store surgery

    Theme customisation, product import, payments, shipping and tax, app and API integrations — plus the awkward jobs: a checkout that drops customers, a migration between platforms, a catalogue that has outgrown its theme.

    • Theme work
    • Migrations
    • Integrations
    • Speed
  3. 03

    Overflow · retainer

    Capacity when you are full

    A block of development hours each month for the jobs that pile up between projects: edits, bug fixes, plugin conflicts, speed work, small features. Invoiced to you, not your client, so your margin stays yours.

    • Monthly hours
    • One request queue
    • Agreed response times
  4. 04

    Rescue

    Inherited sites and rescue jobs

    The build a previous developer walked away from, the site that breaks on every update, the store that takes nine seconds to load. I take it over, document what is actually there, and give you a straight answer on repair versus rebuild.

    • Audits
    • Takeovers
    • Performance
    • Security

The ground rules

What white label means here

01

Your brand, start to finish

Staging links, documentation and handover notes carry your name, not mine. No credit in the footer, no link back, and nothing appears in my portfolio unless you tell me it can.

02

I don't approach your client

Not during the project, not after it. If they contact me directly, I send them back to you. I'm happy to sign your NDA or non-solicit before we even discuss scope.

03

Fixed quotes, not open meters

You get a written scope and a fixed price before work starts, so you can mark it up and quote your client with confidence. Changes get re-quoted rather than quietly billed.

04

You keep the relationship

I can join client calls as your developer, or stay invisible and work entirely through you. Your call, and it can differ from project to project.

How it works

From your brief to your handover

  1. 01

    Send the brief

    Designs, a URL, or a few paragraphs. Within a day you'll know whether it's a fit and what I still need in order to quote it.

  2. 02

    Fixed quote

    A written scope, a price and a delivery date — not an estimate that grows halfway through the build.

  3. 03

    Build on staging

    A private staging link from the first week, so you can follow progress and show your client whenever you're ready.

  4. 04

    Handover to you

    Deployed wherever you want it, with written handover notes in your name — and I stay available for the snags that surface after launch.

Ways to work together

Pick whichever suits the job

Monthly hours

A reserved block of development time each month for ongoing client work, edits and fixes — with first call on my availability.

  • Agreed hours on a single invoice
  • Priority over ad-hoc requests
  • One channel for your whole team
  • A monthly summary of where the time went

Next step

Got a build you'd rather hand over?

Send the brief, or just tell me what keeps landing on your desk. If it isn't something I should take on, I'll say so.