Contracting clients
You hold the client relationship. We hold the technical side.
This page is for agencies, studios, consultancies, integrators and independents who need a skill they don't have in-house, or extra hands at a peak. In this relationship we're a technical subcontractor, and there's no reason to dress it up otherwise.
1 · What we take on
The list, plainly.
Integration and development. Foundations and hosting: domains, email, deliverability, backups. E-commerce: catalogue, checkout, payment, connection to stock. Automation and connecting tools. Taking on technical debt in a poorly documented system. Technical SEO: structure, speed, markup, indexability. Maintenance and monitoring after delivery.
Format: time and materials or fixed price, depending on whether you’re buying days or a deliverable.
2 · What we don't take on
What guarantees we won't tread on your toes.
Graphic design, identity, brand world. Content, editorial line, writing copy. Communications strategy, advertising, lead generation.
This isn’t a courtesy: it’s structural. What we exclude is exactly your trade, and what occupies us is often the weak point of a project. So there’s no possible competition: we will never become the candidate who takes the whole budget from you.
For a consultancy or an integrator, whose trade is technical like ours, that argument doesn’t hold in the same way: the guarantee against competition isn’t the scope, it’s the relationship. It rests on the three commitments below, non-solicitation first among them.
3 · The three commitments
Written, not implied.
Non-solicitation.
We don't approach your clients, during the engagement or after it. No exception, and no period after which the rule would lapse.
Discretion.
We never appear publicly on a project delivered for you, and we don't communicate about it. This isn't a favour granted case by case: we publish for no one, ever, including our direct clients.
Deadlines met.
It's your signature on a date, not ours. What holds it: the specification written before the code, which removes the end-of-project back and forth, and a production speed that AI has genuinely changed. A date about to slip is announced before it slips.
4 · How we fit in
Visible or invisible, as you choose.
Quiet subcontracting or a named presence in front of your client: both are possible, and you choose. That’s a separate question from public communication, on which we never appear.
Our tools line up with yours: your ticket tracker, your repository, your environments, your conventions. We don’t ask a contracting client to adopt our tooling for an engagement.
One point of method, said plainly because it will come up: you will sometimes arrive with specifications already sold to your client. If something in them raises a technical problem, we flag it in writing and we propose an alternative, then we carry out your decision. You are the one holding the client relationship. What we don’t do is carry out in silence a specification we know to be bad.
5 · What you get back
An end of engagement that creates no debt.
Code documented and readable by someone other than its author. Clean, reproducible environments. Written handover and deployment procedures. Access and accounts handed over, with no dependence on our own tools.
You must be able to take the work back in-house, or hand it to someone else, without asking us for anything. It’s the same rule as for our direct clients.
6 · To start
One scoped piece of work, delivered fast.
The best way to know whether a collaboration holds is to test it on a short scope: one scoped piece of work, one date, one deliverable. No sales qualification, no prospecting form: write directly, describing the work and the date that matters to you.