AI design partner agreements: what data are you giving away?

What is an AI design partner agreement?#

An AI design partner agreement is a contract in which an early-stage AI vendor gives a company early access, discounted pricing or influence over the product in exchange for feedback, a reference and, very often, access to the company's records. The vendor usually drafts it, and the data terms are written for the vendor's roadmap rather than yours.

The pilot itself is often worth doing. The issue is that a document framed as a product trial can contain a data license broader than one the company would sign if it were asked directly to license its support history or proposals for model training.

What data are you actually giving away?#

A design partner usually receives more data than the pilot needs, because integrations connect to whole workspaces rather than to a chosen set of records. A connector to Zendesk, Salesforce, Slack or SharePoint can reach every ticket, account note or channel the connecting user can see.

Staff corrections deserve particular attention. When experienced estimators or support engineers fix the vendor's drafts, they produce exactly the human-generated, domain-specific signal that the SourceX Enterprise Data Value Framework treats as a value driver, and a broad feedback clause can hand all of it to the vendor.

• 1Historical records pulled through the integration, often going back years.
• 2Live records created during the pilot.
• 3Derived data: embeddings, labels, summaries and search indexes built from your records.
• 4Your staff's corrections, ratings and edits to the vendor's outputs.
• 5Usage data showing how your team works inside the product.
• 6Prompts and documents your staff upload directly.

Clause checklist for design partner agreements#

The clause checklist compares the version a vendor usually drafts with the version a supplier of records should ask for. Most early-stage vendors expect to negotiate these points with design partners they value, because a reference customer matters to them.

It helps to know what the vendor genuinely needs. Product feedback, a named reference and permission to describe the pilot in sales conversations usually matter more to an early-stage vendor than open-ended training rights, so offering those freely can make the data terms easier to narrow.

How design partner terms compare with a data license#

A design partner agreement and a data license can cover the same records but serve different purposes, and the difference shows up in compensation, scope and documentation. Treating training rights as a license, rather than as a side term of a pilot, is the main protection.

The comparison also explains why the same records can be worth very different amounts in the two settings. In a pilot, the vendor's access is a cost of getting a product; in a license, access is the product, and it is prepared, scoped and documented accordingly.

Red flags in a vendor's draft#

Red flags in a design partner draft usually hide in definitions and survival clauses rather than in the headline terms. Read these sections before the commercial ones.

If the agreement is a click-through, save a copy of the version accepted, with the date and the name of the person who accepted it. Vendors update online terms, and you will need to know which version applied when your records were shared. FTC staff warned in February 2024 that quietly adopting more permissive data practices, such as AI training, through a retroactive change to terms may be unfair or deceptive, but that guidance protects consumers and does not replace reading your own contract.

• 1Customer Data defined to exclude usage data, outputs or feedback, which then fall under broader vendor rights.
• 2A right to use data to improve the vendor's products and services generally, with no limit to your account.
• 3An aggregated data carve-out with no definition of aggregation or de-identification.
• 4License grants that survive termination with no end date.
• 5No deletion certificate, or deletion only on written request.
• 6No list of the model providers and subprocessors that will receive your records.

Illustrative: a consulting firm narrows a proposal-writing pilot#

Illustrative: a fictional management consulting firm agrees to be a design partner for a startup building an AI proposal assistant. The draft would connect the startup to the firm's SharePoint, which holds proposals, staffing plans, internal playbooks and client deliverables, and grants the startup the right to train its models on all of it.

The firm's general counsel narrows the scope to firm-owned proposals and playbooks, excludes every client folder because client contracts restrict reuse, limits use to the firm's own instance and requires deletion with a certificate at the end. Any training of the startup's general model would need a separate paid license. The startup accepts, the pilot runs, and the firm keeps the option to license its proposal history later on its own terms.

How SourceX treats training rights in a pilot#

SourceX treats any request to train general models on a company's records as a data license, whatever the document is called. That means running it through the SourceX five-step transaction, Supply, Rights, Preparation, Approval and Delivery, with the company approving each step.

The SourceX Enterprise Data Value Framework helps weigh what a pilot asks for: uniqueness, domain expertise and human-generated signal raise value, exclusivity raises price, and preparation cost and privacy burden reduce net value. This is general information, not legal advice; review specific agreements with counsel.