You are afraid we will take your client
What we do. Non-solicitation is a written term. We will not approach your client directly during the engagement or for 24 months after it ends. It is signed before scoping, not discussed afterwards.
AISTORSFor agencies
For partnersYour client, your brand, our delivery.
For agencies, consultancies and managed service providers who have won AI or cloud work they cannot currently staff. We work as your delivery team. Your client relationship, your brand, and either your project management or ours. The commitments below are contract terms, not reassurances, because that is the only version worth anything to you.
Book a 30-minute call
Before you commit to your client
We tell you what we can absorb first, and refuse what we cannot staff properly. A refusal now is worth more to you than an apology after you have promised your client a date.
If the left column is not you, say so on the call and we will tell you whether there is a fit at all.
Five things make agencies wary of subcontracting delivery. Each one is answered by a term in the contract rather than by a promise on a page.
What we do. Non-solicitation is a written term. We will not approach your client directly during the engagement or for 24 months after it ends. It is signed before scoping, not discussed afterwards.
What we do. White-label discipline by default. Our name appears nowhere in the deliverables, documentation or client communication unless you specifically ask for it.
What we do. We tell you what we can absorb before you commit to your client, and we refuse work we cannot staff properly. A refusal early is worth more to you than an apology late.
What we do. A named engineer and a defined response window under the tier you choose, including out-of-hours where that tier covers it. Named individual, not a shared inbox.
What we do. The same terms as our direct work. Code, configuration, prompts, evaluation suites and documentation, assigned onward so your client owns what you delivered rather than renting it from us.
What the arrangement covers, and where its edges are.
The first engagement is deliberately small, because that is how you find out whether this works.
Signed in both directions before any client detail is discussed. No scoping conversation happens before this, in either direction.
What you have won, when it lands, and whether we can staff it properly. This is where we say no if the answer is no, which is the most useful thing we can do at this stage.
Deliverables, response window, named engineer, escalation path, non-solicitation and onward ownership of the work, all confirmed before delivery begins.
Your client relationship, your name on the work. We produce the same artefacts as a direct engagement, prepared so you can hand them on without editing our name out of them.
Runbooks, infrastructure as code and decision records written as delivery proceeds, so your team can support the work or pass it on without depending on us.
No, and it is a contract term rather than an assurance. Non-solicitation runs for the duration of the engagement and for 24 months after it ends, in writing, signed before scoping.
Yours, unless you ask otherwise. White-label discipline means our name appears nowhere in the deliverables, the documentation or the client-facing communication by default.
Whichever way you prefer. Some partners keep project management and their own client relationship and use us purely as the delivery team. Others hand the delivery management to us and stay across it at a governance level. Both work; we will say which we think fits the shape of the engagement.
We tell you before you commit to your client, not after. Capacity honesty is the single most valuable thing a subcontractor can offer an agency, and we will refuse work we cannot staff properly rather than accept it and disappoint you downstream.
Yes, under your brand and your introduction, or not at all. Some partners want an engineer in the room for technical credibility; others prefer we never appear. Either is fine and it is agreed before the engagement starts.
Start with a diagnostic on one of your client engagements. It is small, fixed-scope, produces something you can hand your client regardless, and tells you far more about how we work than a capability deck would.
Thirty minutes, under NDA if you prefer. Tell us what you have sold, when it lands and what you cannot staff. We will tell you plainly whether we can absorb it, and if we cannot we will say so before you have promised anything else to your client.
Booking link: ‹FILL: scheduling URL›
Or write to [email protected]
Enablement and handover
How work leaves our hands and stays working in yours, which is what makes onward handover to your client possible.
DisclosureAI capability and data handling
The disclosure page your client's procurement team will ask for, covering providers, terms, residency and sub-processors.
Service 09Managed AI and cloud operations
Where you have sold ongoing support, the layer that keeps a live AI system working after go-live.