White-label AI product work: how agencies say yes without losing the client

The request usually arrives inside a conversation about something else. A client you've worked with for years mentions a product idea for their own customers, or asks whether the new site could "do something with AI", or wants an AI feature in the app you designed for them. Your team is good at brand, design, marketing or development. It isn't staffed to decide what an AI product should do, build it, test it and launch it. What you say next decides more than one project.

01Why are clients asking agencies for AI products?

Because they already trust you, and because AI work no longer looks like a separate specialism from where they sit. Your client doesn't want a new vendor relationship, a new procurement process and a new team to brief. They want the people who already understand their brand and their customers to have an answer.

That's an opportunity, and it's also a risk. An agency that keeps saying "we don't ship that" teaches its best clients to look elsewhere. The first project goes to another firm. The second conversation happens without you. Eventually the other firm offers to handle the brand work too.

02What does white-label delivery actually mean?

White-label delivery means a partner does the building while your agency sells, manages and owns the relationship. Done properly, it has four properties, and you should get all four in writing:

• Your brand on everything. Your client sees your agency. The partner stays behind it unless you choose to bring them forward.
• Your tools and channels. Communication runs through your workspace, your email and your project tools, not the partner's.
• A named, stable team. The same people for the whole project, so what the client teaches the team about the product stays with the people building it.
• Non-solicitation in the contract. The partner never approaches your clients, during the project or after it.

The last one is the answer to the question every agency owner asks first, usually before anything else: will they go direct to our client? If a partner hesitates, hedges or offers a gentleman's agreement instead of a clause, that's your answer.

03Should you hire, use freelancers, or partner?

Each works in the right conditions. The honest comparison includes the cases where a partner is the wrong choice.

If you win AI product projects every month and intend to be known for them, build the team. Until then, a partner turns lumpy demand into work you can say yes to without carrying the cost of a team between projects.

There's a fourth option, and it deserves more respect than it gets: saying no, well. If the request sits outside what you and any partner can do properly, tell the client so and point them to someone who does it well. A clean no keeps the relationship. A shaky yes spends it.

04How do you scope and price AI product work without losing margin?

Most agencies lose margin on product work in the same four places, and the partner's rate is rarely one of them.

1. Vague scope. "An AI assistant for our customers" is a direction, not a scope. Fix what the first release does, for whom, and what it deliberately leaves out, before you quote. The Scope Cut is how we do it: every item gets build first, later, cut or don't build, with a reason.
2. Changes absorbed silently. Every "small addition" you absorb comes out of your margin. Agree up front that changes are priced from a rate card, never quietly absorbed, and hold your partner to the same rule.
3. Discovery squeezed to hit a date. Most rework on product projects traces back to a discovery phase cut short. Protect it in the plan, even when the client wants to start building yesterday.
4. The unglamorous work left out. Testing the AI's behaviour, security, monitoring and a staged release are what make a product dependable. Leave them out of the quote and you'll deliver them anyway, unpaid, after launch.

That line is aimed at every quote built from optimism instead of scope. Quote fixed scope, bill by milestone, and put support after launch in a separate agreement. Your margin is protected by the shape of the scope, not by the number at the bottom of it.

05How does a white-label project run, step by step?

The shape is the same as any product engagement. What changes is who faces the client at each step.

1. The brief stays with you. Your client briefs your agency, as they always have. You bring the partner in behind the scenes, with everything you know about the client's business and brand.
2. Scoping, together. The partner works through the product decisions with you: what the first release does, who it's for, and what it leaves out. If the client joins the session, the partner joins as part of your team.
3. A fixed-scope proposal to you, from the partner, before you quote. Your quote to the client rests on it, with your own margin and your own terms.
4. Milestones you present. Each milestone ends with something working. You show it to the client, under your name, with the partner in the room only if you want them there.
5. Testing and a staged release, so problems surface with a small group before the client's customers see them.
6. Handover under your brand: documentation, runbooks and the reasoning behind each decision, written so your client's team, or yours, can run the product without the partner.
7. Support after launch, agreed separately, with its own scope and its own price, so it never becomes unpaid work.

Done this way, the client experiences one agency that can suddenly ship products. That's the point. The partner's job is to make your agency look like it always could.

06How do you protect the client relationship?

The contract does the heavy lifting, and the working rhythm does the rest.

• In the contract: non-solicitation that survives the project, confidentiality, and a clear statement of where the code lives and how intellectual property transfers on payment.
• In the rhythm: your agency runs the client meetings, and the partner joins as part of your team when you want them there. Decisions go through you.
• In the exit: you should be able to stop at any milestone and pay only for the milestones completed. A partner who can't offer that is asking you to carry their risk.

Keep the decisions your client pays you for. Strategy, brand and the relationship are yours. The partner should hold the parts you can't staff, not the parts that make you valuable.

07What should you ask a white-label AI partner before signing?

1. What have you built and run yourselves? Ask to see live products, labelled honestly as their own work or client work. A partner that has only built demos will learn on your client.
2. Who exactly is on the team, and will it stay the same? Names, not roles.
3. How do you test the AI's behaviour? Look for an evaluation set agreed before the build and run before every deploy. "We test it thoroughly" isn't an answer.
4. How do you handle change requests? The right answer is a rate card and a written change note, every time.
5. What's in the contract about my clients? Non-solicitation, in writing, during and after.
6. What happens if we stop halfway? Stopping at a milestone should cost only the milestones completed.
7. Where does the code live? In a repository the right party owns from day one, not handed over at the end.
8. Can you also do the launch? A product that launches without a demo, launch visuals and an updated site undersells your agency as much as the client.

08Which half of the work are you missing?

Different agencies need different things from a partner, and naming the gap precisely saves a lot of mismatched conversations. The Foundation Matrix splits the work into three areas, Strategy, Creativity and Technology.

• Design and brand agencies usually hold Creativity and often Strategy. The missing half is Technology: product engineering, AI features, testing and release.
• Marketing agencies usually hold Strategy and some Creativity. They need Technology, plus product-grade interface design.
• Development agencies hold Technology. Their gap runs the other way: brand, product design, positioning and launch creative, which is why their proposals sometimes lose to worse-built products with better brands.

Name your missing area before you brief anyone, and look for a partner who is strong exactly there.

09What are our terms, stated plainly?

We build AI products and creative behind agencies' brands, for design, brand, marketing and development agencies whose clients now want AI work. Through our Partners programme, we deliver our AI Product Build and AI Creative Build work white-label, with the same stages, gates and evaluation as our own work. The only difference is whose name is on it.

• We never approach your clients. It's in the contract, during the project and after it.
• We work through your tools and channels.
• You get a named, stable team.
• You can stop at any milestone and pay only for the milestones completed.

White-label work stays private unless you give permission to show it. What we can show is our own: otlo and apprn, products we built and run ourselves.

10Questions agencies ask