What white label means in practice
Everything we produce ships under your name: commits in your repository, documentation in your template, staging on your domain, handover notes written as if your team wrote them. No logo, no signature line, no credit request in the footer.
If you want us on a client call we will join as your team, briefed on the account beforehand. If you would rather we never appear, that is the default and it costs nothing extra.
- NDA signed before any access is granted
- Work delivered in your repo, following your conventions
- No portfolio use, no case study, no name-dropping
A day rate, not a fixed-price guessing game
Agency work changes shape mid-flight, and fixed prices push both sides into defending scope instead of shipping. A day rate with an agreed number of days per sprint keeps that argument out of it: you buy capacity and you direct it.
The rate is published on this page rather than quoted per enquiry, so you can price your own proposal before you ever speak to us. Where a project genuinely suits a fixed price, we will quote one.
How we slot into your process
We take work from your tracker, not a separate one, and we write in the channel your team already uses. Branch naming, commit style, review rules and definition of done follow your handbook. Onboarding is usually an afternoon, because the point is that nothing about your process has to change.
For agencies without a fixed process, we bring one and hand it over. That is not a condition of working together — it is just what makes an overflow arrangement survive past the first month.
Who carries the risk
The reason to subcontract is rarely a lack of skill; it is a lack of predictable capacity. That risk moves to us: agreed days are reserved, and if we miss an agreed date through our own fault, the day is not billed.
What we cannot absorb is scope arriving late from your client. We flag that early and in writing, so the conversation happens with them rather than with you at the deadline.
Confidentiality across borders
An NDA is signed before any access is granted, and access is scoped: a collaborator seat on the repository and on the specific Shopify store, not an organisation-wide admin role. When an engagement ends, access is removed and we confirm it in writing.
Client data stays where it is. We do not copy production databases onto local machines, and where test data is needed we work with anonymised or generated records.
What we turn down
We do not take work that requires contacting your client behind you, and we do not accept a direct approach from an agency's client once we have worked on that account. Poaching would earn a single fee and end a pipeline.
We also decline briefs we cannot staff properly. An overflow partner who says yes to everything is the usual reason overflow arrangements fall apart.
