For agencies
Your dev team, without hiring one.
About half our work comes through agencies. You've sold the job; we build it under your name. You keep the client and the credit, and you deal directly with the developer writing the code.
Websites, web apps, mobile apps and AI work, for design studios, PR and comms agencies and marketing teams who'd rather not run a development team of their own.
Who talks to whom
Happy being invisible.
White-label only works if your client never has a reason to wonder who built it.
You own the client
We talk to you, not your client, unless you ask us to. If you'd like us on a call, we'll join as part of your team and you can introduce us however you like. If your client gets in touch with us directly, we'll point them back to you.
Our name stays off it
No footer credits, no "built by" links, and no portfolio post unless you say we can. Most of the agency work we've done isn't on this site, which is rather the point.
One person, start to finish
The person who estimates the job is the person who builds it and the person who answers when your client finds a bug on launch day. No junior handed your project halfway through, and nothing lost between a sales call and a dev team.
How it works
From brief to handover.
The brief
Send over whatever you've got: a proper brief, a Figma file, or the client's wishlist from the pitch. If you need an NDA signed first, send that too. We sign them all the time. Then we get on a call and ask the awkward questions now rather than three weeks in. If it's not a good fit, we'll say so.
The estimate
You get a written scope and a price, broken down so you can see where the time goes. It's written so you can drop it into your own proposal or forward it to your client. Assumptions and risks are spelled out, and anything meant only for you comes in a separate note.
The build
Phil builds it. You get a working link early and new versions as features land, so you can show your client real progress rather than a status report. Changes come through you. If something's going to take longer or cost more, you hear about it before it happens, not on the invoice.
Launch and handover
We deploy wherever the project needs to live: your hosting, the client's, or ours. You get the code, the logins and enough documentation for your team or the next developer to pick it up. Or we stay on for support, still under your name.
Your side
What we need from you.
Agency jobs go well when a few things are in place before we start.
One person who can decide
Someone on your side who can answer questions and sign things off. Most delays on agency jobs come from waiting for a decision, not from the build.
Designs, or a clear idea
Finished designs in Figma are ideal. A wireframe and your brand guidelines work too. We're developers, so if you need a brand or a full visual design, that's your studio's bit.
Access, early
Hosting, DNS, the old CMS, the client's API keys. Chasing logins is the most common reason a launch slips, so the sooner we have them, the better.
The real deadline
Tell us the date it actually has to go live, not the padded one. We'll tell you honestly whether it's doable.
Common questions
FAQ.
What do you build for agencies?
Marketing sites on WordPress, Craft, Statamic or Next.js. Web apps in Laravel, Vue and React. React Native apps. AI features and automations. HTML email templates, which nobody else wants to do. The services pages have the detail.
How do you charge?
Fixed price when the scope is clear, day rate when it isn't or when you need an extra pair of hands for a few weeks. Rates are on the pricing page. You set your own price to your client. We don't need to know it.
What happens when the client changes their mind?
They will, and that's fine. We'll tell you what the change costs in time and money before we start on it, so you can decide whether to absorb it or pass it on.
There's only one of you. Is that a risk?
It's a fair question. It means we take on a small number of projects at a time and tell you straight when we can start. Code lives in a repository you can access, and it's documented as we go, so nothing lives only in one person's head.
Can you work in our tools?
Usually, yes. We'll join your Slack or your project board and fit in with how your studio already works, rather than making you learn ours.
Contact
Got a job that needs building?
Send the brief, or just the deadline and a rough idea. You'll hear back from Phil within one working day, with either a sensible next step or an honest “not this one”.