White-label capacity for agencies · US · UK
PHP Outsourcing
White-label PHP, Laravel and WordPress capacity for agencies in the US and UK. We work under your name, in your Slack, on your NDA, and your client never learns we exist. Ten working days risk-free, and every line of code assigned to you from the first commit.
- You are the client, not the middleman
- We invoice you, you invoice them. No revenue share, no attempt to go direct, ever.
- Your name on everything
- Your email domain, your Slack, your Git organisation, your project management tool.
- Non-solicit, both ways
- We will not approach your clients. You will not approach our engineers. In the MSA.
- Named engineer, not a pool
- The same person across your projects, so they learn your standards once.
- We stay off the call unless invited
- And when invited, we join as your team. Briefed on what we are called.
- Ten working days risk-free
- On a real ticket from a real client project. Walk away and owe nothing.
2 retainer slots open this quarter
Engagement models
Four ways agencies buy capacity
Pick by how predictable your pipeline is. Every model is the same engineers, the same review standards and the same published rate, with no agency markup on top.
Overflow hours
For the week a client says yes to three things at once. Billed in 15-minute blocks.
Priced on the rates pageReserved half-week
Eighty hours a month held for you, whether or not you use all of it.
Priced on the rates pageEmbedded developer
MOST CHOSENOne engineer, full time, in your Slack under your domain. Your clients assume they are staff.
Priced on the rates pageWhite-label pod
Two developers, QA and a PM. You keep the client relationship, we keep the delivery.
Priced on the rates pageStraight answer
Why agencies subcontract, and where it goes wrong
Agency pipelines are lumpy in a way product teams are not. You win two projects in a fortnight and then nothing for six weeks, so hiring against the peak leaves you paying salaries through the trough. Subcontracting moves that risk off your payroll, which is why roughly a third of our work now comes from agencies rather than end clients.
Where it goes wrong is almost never the code. It is the seam between two companies: a client question that sits unanswered for a day because it was asked in the wrong Slack, or a subcontractor who quietly optimises for hours rather than for your reputation. Both are avoidable, and both are about how the arrangement is set up rather than who writes the PHP.
So we set it up the same way every time. Our engineer lives in your workspace, not a shared one. You brief them, you review their work, and they are told what your agency calls them. We never contact your client, never appear on a call uninvited, and the non-solicit runs both ways. We will not approach your clients, you will not approach our engineers.
The one thing we will not do is price for the middle layer. Agencies get the same published rates as everyone else, which means your margin comes from what you add, strategy, design, account management, rather than from marking up ours. If that margin does not work for you, tell us and we will say so plainly rather than discount and resent it.
Two agencies have taken our engineers permanently after a year. We wrote the conversion fee into the MSA up front rather than pretending it never happens, and both are still sending us overflow work.
The alternatives
Subcontract, freelance, or hire
Freelancer and in-house figures are typical US mid-to-senior ranges for 2026, including employer costs. Ours are the published rates, with no agency markup.
Capabilities
What agencies hand us
Eight things agencies subcontract most. If yours is not on this list, describe it in a paragraph and we will tell you honestly whether it is us.
Custom PHP web application development
Greenfield builds on PHP 8.4 with a test suite, CI pipeline and written documentation from the first week, not bolted on before handover.
PHP 8.4Pest
GitHub Actions
Docker Legacy PHP 5.x to 8.4 upgrades
Static analysis first, then a branch-by-branch upgrade with the site staying live throughout.
Laravel application development
Multi-tenant SaaS, billing, queues and Filament panels on Laravel 12.
Laravel 12HorizonFilament 4 REST APIs and third-party integrations
Stripe, HubSpot, NetSuite, shipping and tax APIs, with retries, idempotency and a replay log.
StripeWebhooksOpenAPI CodeIgniter maintenance and migration
Keep CI3 patched and secure, or move it to Laravel one module at a time.
CodeIgniter 4 WordPress and WooCommerce engineering
Block themes built properly, headless front ends on a Laravel API, and stores that stay fast well past forty thousand products.
WordPress 6.8HPOSWP-CLIACF Pro Performance and database optimisation
Query profiling, indexing, caching layers and queue offloading, measured before and after, in writing.
RedisOctane Code audits and clean handover
A written report on an inherited codebase: risks, effort, and what to fix first. Yours to take elsewhere.
Something else?
Describe the problem in a paragraph. We will tell you honestly whether it is us, and who else to ask if it is not.
Tech stack
Current versions, not a wish list
What is in production for our clients this quarter. We will work in older versions too, most rescue jobs start there.
Language & frameworks
PHP 8.3 / 8.4 Laravel 11 / 12 
Livewire 3 Filament 4 CodeIgniter 4 
Symfony components Data & infrastructure
MySQL 8 
PostgreSQL 16 Redis Docker AWS · Hetzner · Forge GitHub Actions Quality & front end
Laravel Pint 
Vue 3 
Tailwind 4 
Alpine The engineers
The engineers who would sit in your Slack
Whoever we put on your account stays on it. You interview them first, and your client meets them as your team, under your domain, briefed on what you call them.
Subscription billing, multi-tenant schemas and the money paths. Reviews every pull request on his team himself.
Laravel 12 Vue 3 PostgreSQL Strangler migrations off CodeIgniter: one router, both frameworks live, no big-bang rewrite.
CodeIgniter PHP 8.4 MySQL 8 Integrations specialist, Stripe, NetSuite and three shipping carriers, all idempotent.
Stripe Sanctum Queues Writes the tests nobody else wants to write, starting with the paths where a wrong number costs real money.
5 more engineers, with full profiles, shipped work and GitHub history. Meet the whole team →
How we work
What your client would get, under your name
White-label work carries one extra requirement: none of it can embarrass you. These are the defaults that make that safe.
Your NDA, your email address, your project tool. We do not appear in front of them at any point.
You are not the last line of defence on code you did not write. Nobody here merges their own work.
Written for your client to read, in their language rather than ours, so you can pass it on unedited.
With the assumptions listed, so when scope moves you have something concrete to reprice against.
The same person for the engagement, so context does not reset when your client asks a follow-up question.
If you take the work in-house, the runbook and docs make that a decision rather than a project.
You do not have to take any of this on trust. The first ten working days are risk-free, every rate is published in full, and the work happens in your repository from the first commit.
How it works
From first email to an engineer in your Slack
Twelve working days end to end, and no money changes hands until you have seen the work on a real client ticket.
- Day 0
Tell us where you are short
The stack, the start date and roughly how many hours. An engineer replies, not a salesperson, inside one business day.
- Day 1
Shortlist, with rates
Two or three profiles with real GitHub history, each carrying a rate, a seniority and the date they come free.
- Day 2
Interview, then paperwork
Twenty minutes with the person who will write the code, then the MSA and non-solicit signed, with your client's NDA flowed down if they require one.
- Days 3-12
Ten days in your workspace
Your domain, your Slack, your Git organisation. Real tickets from a real client project. Walk away at the end and owe nothing.
- Ongoing
Scale, hold or stop
Add a second developer at the same published rate, or give 30 days' notice. Repo, cloud accounts and IP stay yours.
Why India
Why agencies outsource PHP to India
The arithmetic is what makes agency margin work: a senior engineer here costs roughly what a mid-level contractor costs in Austin, so you can quote competitively and still keep a real margin. The timezone helps more than it hurts, work lands overnight, so you review in the morning and reply to your client the same day.
YOUR WORKING DAY, AND OURS
- IP assignment on day one
- Everything written for you is yours on commit, not on final payment. Assignment clause, not a licence.
- NDA before repository access
- Yours or ours, signed before anyone is added to your GitHub organisation.
- Your jurisdiction, your paper
- We sign MSAs governed by Delaware, England and Wales, or Ontario law without argument.
- No lock-in, 30 days' notice
- Month to month after the trial. No annual minimum, no exit fee, documented handover included.
- Invoiced in USD or GBP, net 15
- Wire, ACH or card. One invoice a month, itemised by engineer and hours.
The commercial part
How agencies actually price our work into a quote
Nobody explains this and everybody asks, so here it is plainly. There is no markup on our side, which means the margin question is entirely yours.
Work out your blended rate first
If you bill a client $95 an hour and our engineer costs you $30, the gap covers your account management, your project management, your QA review and your risk. Agencies that forget to price their own oversight into that gap end up doing our management for free.
Charge for the review, because you will do it
Your senior still reads the pull requests, still talks to the client, still owns the relationship. That is real work and it belongs in the quote as a line rather than absorbed. The agencies who do best with us bill it explicitly and the client never blinks.
Reserved capacity beats hourly for lumpy pipelines
Hourly looks cheaper until the month you win two projects and we have nobody free. A reserved half-week costs you whether or not you use it, and it means the answer is yes when a client asks if you can start Monday.
Decide about disclosure early, not mid-project
Some agencies introduce us as their offshore team on day one, some never mention it. Both work. What does not work is a client discovering it accidentally in month four, so make the choice deliberately and tell us what you have said.
FAQ
Questions agencies ask before the first call
If yours is not here, email it. We publish the answer rather than saving it for a sales call.
Will you ever contact our client?
No, and it is a clause rather than a courtesy. We do not know who they are unless you tell us, we do not appear on calls uninvited, and the non-solicit in our MSA runs both ways.
Do agencies get a different rate?
No: the same published rates as everyone else. We do not mark up for the middle layer, which means your margin comes from what you add rather than from discounting ours.
Whose name is on the work?
Yours. Your email domain, your Slack, your Git organisation, your project tool. Commits carry your conventions, and documentation is written as though your team wrote it.
What if our client asks who built it?
That is your call to make, not ours. Some agencies introduce us as their offshore team, some never mention it. We will follow whatever you have told the client.
Can we resell your engineers as our staff?
Yes, that is what white-label means here. What we ask is that you do not present them as more senior than they are. It comes back on both of us when the work does not match the pitch.
How do you handle our client's NDA?
We sign yours, and yours can flow down whatever your client requires. We have signed client-of-client NDAs before and will do it without argument.
What happens if our pipeline dries up?
A reserved retainer holds capacity, so you pay for the hours whether or not you use them. If you need to pause, thirty days' notice and we release the engineer, no exit fee.
Can we hire the engineer permanently?
Yes, after twelve months, with a conversion fee agreed in the MSA up front. Two agencies have done it, and both still send us overflow work.
Who owns the code and the IP?
You do, assigned from the first commit, so you can assign it onward to your client cleanly. Work happens in your repository, not ours.
What if the work is not good enough?
Ten working days risk-free on a real client ticket, then a replacement within five business days at no cost. Your reputation is the thing at risk, so we would rather change the engineer than argue.
Talk to an engineer
Tell us what needs building
You get a reply within one business day from an engineer, not a form autoresponder, with a named person, their rate and the date they come free. We will never contact your client, and there is no discovery fee.
We never contact your client. It is in the MSA
Your NDA, and your client’s if they require one
Ten working days risk-free on a real client ticket
We never share your details, and we do not run a mailing list.