Skip to main content
Discuss

Partner with XONIK: delivery and white-label

We work with agencies and consultancies that hold the client relationship and need senior delivery behind it, for AI, technology and research work, under their name or alongside it.

Line illustration of work handed between a partner and the firm in turn, where the hand-off must be explicit, drawn as parallel lanes, one hand-off broken.

In brief

XONIK works with agencies and consultancies as a delivery partner. Senior practitioners deliver AI, technology and research work under the partner's brand or alongside it, the arrangement XONIK ran for most of its history. Each partnership is agreed in writing, covers one engagement or an ongoing arrangement, and starts with a conversation.

On this page

How a partnership is set up

A partnership starts with a decision about whose name is on the work. Under white-label the work appears under your brand and we are not mentioned to your client unless the scope says so. Alongside you, we are introduced as your delivery partner. The next is how long it runs: a single engagement, or an arrangement that continues across clients.

White-label is the arrangement we worked in for most of our history, so it is not a special request. The work comes from the services on this site: AI delivery, technology and integration, research and evaluation, advisory support and product engineering. Senior practitioners do it, and the scope is written for the engagement in the same way as for any client.

Does a delivery partnership make sense for your agency?

It works when the roles are plain. These are the cases we see on each side of that line.

It tends to work when

  • You hold the client's trust and want to keep the relationship.
  • The problem needs senior judgment that you would rather not hire for the length of a single engagement.
  • You can describe the client's problem on a page, even if you cannot yet say how to solve it.
  • The client wants research or an evaluation done by someone other than the party selling them the build.
  • A product build needs specialists beside your own team, not instead of it.

Look for another arrangement when

  • You want extra hands who take daily direction from your project manager, with no scope of their own.
  • You want us to vouch for a capability claim that was made in a pitch and has not been checked.
  • Ownership of the work product, or what each side may say, is to be settled informally later.
  • You expect us to hold the client relationship that you will later be asked to account for.

You gain senior delivery without hiring for it, and you keep the client. You give up some control over the day-to-day choices of the people doing the work, and you commit to putting in writing who speaks to the client and what happens when the client asks us a direct question.

From the first note to the first delivery

  1. 01

    You describe the client's problem.

    A short note to the partners address says what the problem is and how you would like to work. The client does not need to be named at this stage.

  2. 02

    A senior practitioner replies, and we talk.

    The conversation covers what has been promised, what has been tried, and who on your side decides.

  3. 03

    A short diagnosis, if the problem is unclear.

    We write the scope once the cause is understood.

  4. 04

    The scope is written down.

    It names the arrangement, who speaks to the client, what each side may say, who owns the work product, and what finished means.

  5. 05

    Delivery.

    Progress is reported to your lead through the channel the scope names, and decisions are recorded as they are made.

  6. 06

    Handover.

    Run books and monitoring go to your lead and to a named owner on the client's side, and the work is presented by whoever the scope says.

A pattern we are brought into

The agency that sold the plan before it could build it

An agency wins an engagement to make a retailer's product information usable by an assistant on the retailer's site. The agency's people can design the experience and write the brief. The work also needs an integration with the retailer's catalog and order systems, an evaluation of what the assistant gets wrong, and someone able to say what it should refuse to answer. The agency's lead is wary of bringing in a subcontractor who might later approach the retailer.

  1. Read the brief. We read what the retailer was promised and mark where the promise outruns what can be built.
  2. Name the arrangement. The scope says the work is white-label, that we do not contact the retailer, and what we say if the retailer contacts us.
  3. Scope the part we own. The integration, the evaluation and the rules for what the assistant refuses, each with a named reviewer at the agency.
  4. Deliver and hand over. Progress goes to the agency's lead. The run book goes to the agency and to the retailer's named owner, and the agency presents it.

Where it endsThe retailer sees a single team. The agency keeps the relationship and has delivered something it can stand behind. A person at the retailer is able to say who runs the assistant.

What if the client's own rules ask who is in the delivery chain?

White-label limits what we say to your client unprompted. It does not allow a false answer to a direct question, or to a regulator. Some buyers are now answerable for their suppliers' suppliers, so a delivery chain that is hidden from a client's procurement or security review can become a problem for you as well as for us.

Where a client's rules require disclosure, the scope states what we disclose, to whom and when, so nobody has to improvise in the middle of a review. Our briefing on outsourced and white-label delivery sets out the rules that bear on this.

What we ask of a partner

  • Access to the client's people and systems, under the confidentiality terms of the engagement
  • A decision maker on your side with the authority to choose between options
  • An accurate account of what the client expects, including what was promised in the pitch
  • Review of the statement of work by your counsel, with ownership of the work product stated
  • A named owner for the result on the client's side

What do prospective partners ask?

Can you deliver under our brand?

Yes. That is how we worked for most of our history. The scope states that the work appears under your name, who speaks to your client, and what we may say about the engagement, which by default is nothing.

Will you approach our client directly afterward?

The agreement sets what each side may do with the client relationship, and we write it down before work starts. Where you want us not to contact your client, the agreement says so, and that is the term we work to.

Who owns what we produce for our client?

The statement of work says who owns the work product, and your counsel reviews it before work begins. Ownership is never left to be inferred later, because a gap there becomes a dispute between you, your client and us.

Can we try one engagement before an ongoing arrangement?

Yes. A single engagement is a normal way to begin. It shows both sides how the work and the communication go, and an ongoing arrangement can follow if it suits you.

How do we begin?

Write to the partners address with a short description of the client's problem and how you would like to work. A senior practitioner replies to arrange a conversation, and a scope follows if there is a fit.

Start a conversation

Tell us about your client's problem and how you would like to work. Write to [email protected]

Have a client problem you want delivered well?

Describe what you are weighing in a few lines. A senior practitioner replies with a suggested first conversation.