Partner programme

The engineering team your clients never meet

Agencies bring us the WordPress work they cannot staff, and we deliver it under their name. No badge in the footer, no email to your client, no awkward questions.

102sites in the showcase 3,923,520monthly visits served NDA firstbefore we see anything
Who this is for

Three kinds of partner

Design and marketing agencies

You win the work and own the relationship. We build what you sold, to your designs, and never appear in the room.

Hosts and platform companies

Migrations, malware cleanups and performance work for your customers, handled under your support brand instead of yours.

Plugin and theme companies

Overflow engineering when the roadmap outgrows the team: features, compatibility work and the support queue nobody wants.

In writing

How we stay invisible

Every white-label page in this industry says "NDA protected" and stops there. These are the specifics, and they go in the agreement.

  • A mutual NDA signed before we see anything, not after the first invoice
  • We never contact your client, on any channel, for any reason
  • No CodeTrappers credit in the footer, the source, the readme or the commit history
  • Reports and update summaries come out under your logo, ready to forward
  • We join your calls under your domain if you want us there at all
  • Nothing we build for you appears in our showcase or case studies without your written say-so
  • Credentials stay in your password manager, scoped per site, revoked when the job closes
  • Code is delivered to your repository, so the work is yours if we ever part ways
Commercials

Three ways to work together

Rates depend on the stack and the volume, so they are quoted rather than listed. The model is your choice and you can change it.

Per project

You send a scope, we send a fixed price and a date. Best when the work is defined and you want certainty rather than a running meter.

One-off builds and migrations

Retained hours

A block of engineering time each month that you allocate across whichever clients need it. Unused hours are visible, not quietly pocketed.

Steady pipeline, changing priorities

Care plans per site

Updates, backups, monitoring and fixes on your clients' sites, reported under your brand. You set the retail price; we bill you wholesale.

Recurring revenue you resell
Getting started

Small first, then bigger

  1. 1

    A call with an engineer

    Not a salesperson. Thirty minutes on what you build, where you are stuck and whether we are actually a fit.

  2. 2

    NDA, then a small first job

    Paperwork first, then something low-stakes and real. Nobody should hand over a flagship client to an agency they have never worked with.

  3. 3

    A shared channel

    Slack or whatever you already use, with the engineers in it. No account manager relaying messages between two teams who could just talk.

  4. 4

    Scale it, or do not

    If the first job goes well, we agree a model and a rhythm. If it does not, you have lost one small project rather than a client.

Start here

Start with something small

Send us one job you are behind on. NDA signed before we look at anything, fixed price before we start.

We will not approach your client, now or later.

  • A free audit first

    We'll look at your site and tell you straight what needs doing.

  • Fixed scope, fixed price

    Agreed in writing before any work starts. No hidden fees.

  • A real engineer on the call

    You talk to the people who do the work, not a sales script.