AISTORSApplied AI and cloud engineeringBook a 30-minute call

AISTORSFor agencies

For partners

You sold it. We deliver it, under your name.

Your 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
Three colleagues from two organisations working together around a laptop and a shared monitor in a bright co-working space, the screens showing a project plan of rows and simple bars.

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.

01

Who this is for

If the left column is not you, say so on the call and we will tell you whether there is a fit at all.

This is for you if

  • You have won work you cannot staff. A live commitment with a date, rather than a pipeline you might convert later.
  • You need senior capability, not headcount. The problem is usually one or two people who can architect and decide, not a larger team of hands.
  • Your client relationship is the asset. And you want it protected in writing rather than protected by goodwill.
  • You sell AI or cloud and deliver something else. Common, and not a criticism. Selling ahead of capability is how most agencies grow into a practice.
  • You want to be told about capacity honestly. Before you commit to your client, so you can shape the promise around what can actually be delivered.

This is not for you yet if

  • You want the cheapest possible hands. We are a senior founder-led practice and we are not priced or shaped as a body shop. There are better options and we will say so.
  • You want us to carry the client relationship. That is a referral or a direct engagement, which is fine, but it is a different arrangement and should be named as one.
  • The scope is undefined and the date is fixed. We will help you scope it, but we will not accept a fixed date against an undefined scope. Neither of us survives that.
  • You need round-the-clock cover as standard. Not offered by default. Where a tier genuinely requires it, it is scoped with named associates and disclosed to you individually.
  • You would rather we did not sign an NDA. Then we cannot proceed. Mutual confidentiality before any scoping conversation is not negotiable in either direction.
02

What we fix, and how

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.

PROBLEM 01

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.

PROBLEM 02

You do not want a third party visible

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.

PROBLEM 03

You cannot risk a capacity failure mid-project

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.

PROBLEM 04

You need somebody accountable when it breaks

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.

PROBLEM 05

You need to know what your client will own

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.

03

What you get

What the arrangement covers, and where its edges are.

What we build

  • Any of the ten service groups. Delivered under your brand on the same basis as our direct engagements, with the same baseline discipline and the same handover artefacts.
  • Your project management or ours. Agreed per engagement. Some partners keep client contact entirely; others hand delivery management across and stay at governance level.
  • A named engineer and a defined response window. Under the service tier you select, with escalation to a named individual rather than to a shared address.
  • Mutual non-disclosure before scoping. Signed in both directions before any client detail is shared, as standard practice rather than on request.
  • Non-solicitation for 24 months after the engagement. Written into the contract, covering direct approach to your client during and after the work.
  • Rates shared on request under NDA. Discussed on the introductory call and confirmed in writing before anything is committed. Nothing is published here, because a rate without scope is meaningless to both of us.

What this is not

  • Not a body shop. Senior, founder-led capacity attached to your engagement, not interchangeable headcount billed by the hour against a backlog.
  • Not a reseller arrangement. We hold no reseller agreement or commission with any cloud or model provider, so there is no hidden margin inside what you quote your client.
  • Not a white-label of somebody else's work. We deliver what we scope. If a specialism sits outside what we do, we tell you rather than subcontract it onward without saying so.
  • Not unlimited capacity. A founder-led practice has a ceiling and we state it. Where an engagement needs more, it is scoped with vetted associates and individuals are disclosed by name.
  • Not a route to your client. If you ever believe otherwise, the non-solicitation term is the remedy and it is enforceable rather than aspirational.
04

How it runs

The first engagement is deliberately small, because that is how you find out whether this works.

01

Mutual NDA

Signed in both directions before any client detail is discussed. No scoping conversation happens before this, in either direction.

Standard practice · Not on request

02

Capacity and fit conversation

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.

An honest no is a valid outcome

03

Scope, terms and tier agreed in writing

Deliverables, response window, named engineer, escalation path, non-solicitation and onward ownership of the work, all confirmed before delivery begins.

Fixed scope · Written change control

04

Delivery under your brand

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.

White-label by default

05

Handover to you, then to your client

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.

Exit designed in from the start

05

Questions we are actually asked

Will you approach our client?

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.

Whose name is on the work?

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.

Who runs the project?

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.

What happens if we win more than you can staff?

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.

Can you join client calls?

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.

How do we know the quality before we commit?

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.

06

Next step

Start with one engagement, not a framework.

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.

Starts with
A mutual NDA, then a capacity and fit conversation. Neither commits you to anything.
Rates
Shared on request under NDA and confirmed in writing before commitment. Nothing published, because a rate without scope tells you nothing.
If we cannot staff it
We say so immediately. That is the point of the conversation and it is more useful to you than a maybe.
Book a 30-minute call

Booking link: ‹FILL: scheduling URL›
Or write to [email protected]