Skip to content
Explore Build TBD

ACD delivery partners

Bring ACD into your delivery practice.

The proposed ACD partner program is for consultancies and agent-development firms that want a structured way to help clients design, test, and improve human-agent work. We are starting with bounded partner pilots.

Discuss a partner pilot

Your engagement, supported practice

Your firm delivers the professional work

You lead the client engagement and retain your professional-services revenue. The pilot names the client workflow, delivery team, work products, and responsibilities for review and handoff.

Build TBD supports the method

The proposed arrangement provides licensed method assets, current instruments, bounded delivery authorization, and agreed support. Onboarding and an ongoing annual partner arrangement would be scoped separately from your client fees.

Clients may choose an internal-use subscription for continued practice. Any corporate activation requirement and associated costs belong in the initial proposal, so the client can decide before work begins.

Start with a client problem you can own

A partner pilot is a fit for a firm with relevant client delivery experience, a named delivery lead, and a workflow where the client can participate in review. Qualification covers:

  • The business outcome, client sponsor, and one engagement suitable for a bounded trial.
  • Your team’s ability to facilitate, implement within the agreed scope, and evaluate work with the client.
  • Permission to use the proposed source material and clear handling of client records.
  • Capacity for onboarding, supported delivery, outcome review, and client handoff.

An inquiry begins a fit discussion. It does not confer partner status, certification, or permission to deliver the method to clients.

Make the first pilot useful and reviewable

  1. Agree the engagement. Define permitted use, responsibilities, fees, support, and the evidence needed to judge the result.
  2. Prepare and deliver with support. Map one workflow, define context and authority, keep a Decision Thread, and run a scoped experiment with an agreed review cadence.
  3. Return the work. Give the client an operating map, decision and experiment records, an outcome review, and a practical handoff.
  4. Decide what continues. Review delivery quality, client value, and support needs before considering further authorization or corporate activation.

The pilot proposal identifies the materials and support that can actually be supplied. Timing and implementation beyond the pilot depend on the agreed scope.

Give clients a clear way to continue

The proposed corporate arrangement supports continued platform operation, current licensed instruments, updates, or support. It is not triggered by a client’s possession or export of its own historical records.

Define usable client-record export, partner offboarding, and the handoff owner in the initial terms. Ongoing value should come from maintained assets and supported practice.

Explore corporate internal use

Keep learning and delivery rights distinct

Training completion, assessed competence, client-delivery authorization, and corporate use are separate decisions. A workshop or knowledge-access subscription does not automatically grant consulting-delivery or redistribution rights.

Certification badges, train-the-trainer rights, and unrestricted OEM distribution are not offered through this pilot. Named assets, clients, reuse limits, term, support, and renewal would be agreed explicitly.

Compare licensing pathways

Tell us what needs to work better.

Discuss a partner pilot