onward
For agencies
When agencies need an extra pair of expert hands on a WordPress, Laravel or Statamic project, that's often where I come in. I work directly with your team, under your brand, and billed through your invoices, for a sprint, a project, or an ongoing partnership. Your client doesn't ever have to know I exist unless you'd like them to.
Built via partner agencies
Most of the time, agencies book me in one of three shapes. Each one's sized a little differently and billed in its own way, so have a look at the one that sounds closest to what you have in mind and we can tune the details together on a call.
001 / Embedded
I join your Slack, sit in on your stand-ups, push to your repo and ship the work under your brand. You stay in charge of the client relationship, and I slot in alongside your in-house developers as another senior teammate they can rely on.
002 / Project
You hand me a brief, and I hand a built thing back to you. Fixed scope, fixed price, with your project manager running all of the conversations with the client, while I deliver into your environment, working to your conventions and your handover format.
003 / Overflow
Your in-house developer is over-allocated and the client really doesn't want to wait. I take a defined slice of the work off your hands for a sprint or two, properly ticketed and scoped, slotted in alongside your team in a way that doesn't disrupt the rest of what they're doing.
I'm always happy to sign your NDA, or to send mine across as a starting point if you'd prefer. Your client doesn't see me unless you want them to, and I never name agency-side work in my public portfolio without your explicit written approval.
I invoice you and you invoice them, which keeps things cleanly white-label with predictable margins and a single PO from your finance team to manage. I bill by bank transfer, monthly or per milestone, whichever fits the way you usually run your billing cycle.
After years of doing this work, I'll spot the thing your account manager missed, the dependency that's quietly about to bite the project, or the spec that just won't survive contact with reality. And then I'll suggest a fix, in writing, in your channel, before it ends up costing anyone money to put right.
Format A
Day rate
Best for embedded sprints and overflow.
Format B
Sprint rate
Two-week blocks, fixed deliverables.
Format C
Project rate
Fixed scope, fixed price, milestones.
Format D
Monthly retainer
Reserved capacity, rolling agreement.
You won't find fixed prices on this page. The ranges are something we'll discuss properly on the call, once I understand the work itself, the deadline you're working to, and how much of the risk is sitting on your side of the table. All four formats sit within the senior-developer band.
001 / WordPress
002 / Laravel
003 / Statamic
Yes, of course. Most agencies have their own NDA they prefer to use, and I'm happy to sign whatever your legal team is comfortable with. If you'd rather use mine as a starting point, I can send a clean mutual NDA across. I've signed quite a few of these over the years, and I treat all agency-side work as private by default: nothing goes in my public portfolio, there's no name-dropping in commit messages, and no social posts about who the end client is.
For overflow work and short sprints, it's usually within one or two weeks of the paperwork being signed. For larger embedded engagements, the lead time will be whatever's showing on the availability pill at the top of the page, which I update weekly. If something feels really urgent, please do ask anyway, because I try to keep a small amount of capacity in reserve for partner agencies who I've worked with before.
Yes, I carry both professional indemnity and public liability insurance through a UK-based broker, kept current to the standard agency-side limits. I can share the certificate on request, and I'm happy to be named on your master services agreement if that's something your finance team needs.
Often, yes. Cover engagements usually run somewhere between two and six weeks, scoped against your developer's existing ticket queue so we both know what's on the list. I'll need a half-day handover with them before they leave, write-up access to your stack documentation, and a single point of contact on your side while they're away. These tend to work much better when they're booked a little ahead rather than scrambled together at the last minute.
For overflow work, three days is usually the smallest piece I'll take on. For projects, it's whatever the scope realistically needs, which tends to be a fortnight or more. I've stopped taking single half-day "just look at this" jobs because in practice the context-switching cost makes them poor value for both of us, even when the work itself looks small.
Yes, that's the default. I commit under whichever name and email you choose, sit in your Slack workspace under your domain, and sign off any written client comms in your house style so it all reads consistently. If you'd rather have me visible to the client as a named senior contractor, that works perfectly well too, we just agree which model we're using up front so nobody's surprised later.
Next step