Set Terms, Boundaries, and Risk Controls

Clear terms prevent a good offer from turning into an ambiguous obligation. They do not need to be hostile or complicated. A small paid pilot needs a plain record of what is included, what the buyer must provide, how changes are handled, who approves the work, how data is treated, and what happens if the engagement stops.

This chapter turns the pilot brief and price into risk controls. Use it to prepare a commercial agreement for qualified review, not as a substitute for jurisdiction-specific legal advice.

Start With the Exchange

A useful terms sheet starts with a short statement of the exchange:

• The service provider will perform a named, bounded job.
• The buyer will supply named inputs and decisions by named dates.
• The buyer will receive named deliverables and a handoff.
• The buyer will pay a stated amount at stated times.
• Both parties will use a written process for changes.

If that summary cannot fit in a few sentences, the engagement is still unclear. Terms amplify an unclear promise rather than fix it.

Define Responsibilities on Both Sides

The provider's responsibilities commonly include:

• Delivering the agreed result with reasonable care.
• Using only approved inputs.
• Completing agreed quality and privacy checks.
• Reporting material limitations.
• Keeping records needed to show what was delivered.
• Returning or deleting data according to the agreement.

The buyer's responsibilities commonly include:

• Supplying complete inputs on time.
• Confirming that the buyer has the right to share the inputs.
• Naming an authorized reviewer.
• Providing feedback within a stated window.
• Making business decisions that fall outside the provider's role.
• Approving or rejecting the final result.

Responsibilities should be operational. "Buyer will cooperate" is too vague. "Buyer will name one reviewer and respond within two business days after each review request" can be managed.

Put the Definition of Done in Writing

Use the acceptance evidence from the offer and pilot brief:

• Required files are present.
• Named fields are complete.
• Source notes accompany material factual claims.
• A reviewer has approved the final result.
• A handoff call or written walkthrough is complete.

State what happens if the buyer does not respond by the acceptance date. The answer may be a reminder, a deemed pause, or a scheduled review. The choice depends on the agreement and local law. Do not silently treat an unanswered message as approval unless the parties have agreed to a lawful process and the consequences are fair.

Distinguish Correction From New Work

Corrections fix the agreed result so it meets the agreed standard. New work changes the buyer, input, output, deadline, or purpose.

Examples of a correction:

• A draft uses an unapproved claim that must be removed.
• A required source note is missing from one of the agreed drafts.
• A file does not contain the agreed four sequences.

Examples of new work:

• Add a fifth customer moment.
• Rewrite the sequence for a second workshop.
• Turn the drafts into a social campaign.
• Change the deadline to a materially earlier date.

Set a review limit and a written change process. A simple change rule is:

> Requests outside the agreed scope will be described in writing, with any effect on price, access, quality, or timeline. Work on the change begins only after both parties approve the revised scope.

This rule protects the buyer from surprise invoicing and protects you from invisible expansion.

Set Payment Timing

Payment terms should answer:

• Amount and currency.
• Whether tax is included or separate.
• When payment is due.
• What event triggers each payment.
• How payment is made.
• What happens if the engagement is paused or cancelled.
• What expenses, if any, are pre-approved.

Do not assume that a platform's default invoice settings meet your local tax or consumer obligations. Check the applicable rules and use a payment path that creates a reliable record. For a new buyer, a deposit or milestone may reduce exposure, but the exact structure should fit the scope and applicable law.

Describe Exclusions Directly

List the high-risk or commonly assumed exclusions in plain language:

• No legal, tax, medical, benefits, or regulated professional advice.
• No guarantee of revenue, savings, employment, approval, or ranking.
• No access to accounts or systems outside the named scope.
• No sending, publishing, or filing on the buyer's behalf unless explicitly included.
• No ongoing maintenance after the handoff unless a separate engagement is agreed.
• No third-party approval that the provider does not control.

Exclusions should not contradict the main promise. If the buyer is paying for a reviewed artifact, the provider cannot exclude all quality review. If the offer says "final," the agreement cannot leave basic completion undefined.

Plan Data Handling Before Access

Create a data map for the pilot:

• What data is needed? Name the fields or files, not "all records."
• Why is it needed? Connect each input to the task it supports.
• Where is it stored? Name the approved system or local location.
• Who can access it? Name roles and use least privilege.
• Which tools process it? List only approved services.
• How long is it kept? Define a retention period.
• How is it deleted? Name the method and confirmation.
• What must not be included? State prohibited or unnecessary data.

If the buyer sends more data than needed, stop and ask before placing it into a workflow. Do not forward a full folder to an AI tool because the review is difficult. The minimal safe input is part of delivery quality.

Review AI Use Explicitly

If an AI tool touches buyer data, document:

• What the tool is used for.
• Which provider or service handles the data.
• Whether inputs may be used for model training.
• Where data is stored or processed.
• What human review is required.
• Who approves the workflow.
• What alternative exists if the buyer does not approve.

The buyer may require no AI processing, a redacted input, an enterprise account, or a local model. Record that requirement before work starts. A tool's general marketing page is not proof that the buyer's policy permits its use.

Human review must be specific. "Reviewed" can mean a person skimmed the output. Make it a checklist such as "verify every named date, figure, quotation, and source reference; confirm that unnecessary personal data was removed; record any unresolved item." The reviewer must have the authority and competence to catch the relevant errors.

Assign the Decision Rights

One of the most common causes of delay is an unnamed approver. Record:

• Who can answer questions about the source material.
• Who can approve corrections.
• Who can approve the final result.
• Who can authorize a scope change.
• Who can approve payment.

These roles may be the same person in a small company. Write that down rather than assuming it. If access to a shared mailbox or system requires a different owner, name that dependency too.

Control the Most Important Risks

Build a small risk register. A useful row contains:

• Risk.
• Likelihood and consequence.
• Prevention step.
• Detection step.
• Owner.
• Response if it occurs.

High-priority risks for a small AI-assisted service often include:

• Unauthorized disclosure of personal or confidential data.
• A fabricated claim or citation entering a final deliverable.
• The buyer not owning the rights to supplied material.
• A missed deadline caused by absent inputs.
• Scope expansion through repeated informal requests.
• A deliverable being used for a regulated decision outside the provider's competence.

Do not rely on a generic disclaimer as the only control. Pair the warning with a process change: minimize data, check sources, name the reviewer, limit the use, or stop the work.

A Worked Terms and Risk Review

The following is an illustrative composite, not legal advice.

Nina's pilot uses a workshop transcript and program notes. The transcript includes attendee names and questions. The buyer wants to share a complete folder of files and has not checked whether the material contains personal information.

The first terms draft simply says: "Client provides all necessary data." Nina revises it after a risk review:

• The buyer supplies one approved transcript and one program notes file.
• The buyer confirms it has permission to share the material.
• Names and contact details not needed for the four moments may be removed.
• Nina uses an approved work account and does not upload the transcript to other services.
• A human reviewer checks every material claim against the source.
• The buyer names a final approver.
• Two review rounds are included. Additional sequences are a written scope change.
• The final files and source notes are retained for a stated period, then deleted under the agreed process.
• The buyer is responsible for legal review of marketing claims and for the decision to send the emails.

The risk register includes:

• Personal information in the transcript: redact and review before processing.
• Fabricated source detail: require source notes and a human check.
• Wrong customer moment: approve the four moments at kickoff.
• Missed event deadline: require inputs earlier than the promised handoff date.
• Ambiguous ownership: state that the buyer retains ownership of supplied materials, while final use rights and third-party terms are reviewed in the agreement.

The revised terms make the pilot more likely to finish. They also give the buyer a clear reason to trust the process.

Rehearse the Hard Conversation

Before sending terms, ask:

• What will I do if the buyer asks for a fifth sequence after the first review?
• What will I do if the transcript contains unexpected sensitive data?
• What will I do if the named approver is unavailable on the handoff date?
• What will I do if an AI tool changes its terms during the pilot?
• What will I say if the buyer asks me to guarantee a revenue result?

Write short, calm answers. A boundary is easier to keep when it is agreed before a difficult moment.

Your Chapter Exercise

Using the pilot brief and price sheet:

1. Write the exchange in five plain sentences.
2. List provider and buyer responsibilities.
3. Define completion and the approval process.
4. Separate two corrections from two new requests.
5. Set payment timing and a change path.
6. List at least six exclusions.
7. Create the eight-field data map.
8. Record whether and how AI is used, and what human checks apply.
9. Build a six-row risk register with controls.
10. Ask a qualified reviewer to inspect the agreement for your jurisdiction.

Chapter Deliverable

Produce a one-page pilot terms brief containing:

• Exchange summary.
• Included deliverables and acceptance evidence.
• Responsibilities and approval roles.
• Review limits, change process, and exclusions.
• Price and payment timing.
• Data use, retention, return, and deletion.
• AI use and human-check requirements.
• Risk register and stop or escalation conditions.

Source and Decision Caution

This chapter provides an operating framework, not a contract or legal, tax, privacy, security, or professional advice. Requirements for consumer contracts, confidentiality, data processing, record retention, accessibility, insurance, and regulated services vary by jurisdiction and can change.

Do not copy a clause from an AI answer and assume it is enforceable or appropriate. Use a qualified reviewer for the actual agreement and keep a record of the reviewed version.

AI systems can expose inputs to vendors, retain outputs, or produce incorrect text. Verify the provider's current terms, configure the minimum necessary access, and confirm that human review matches the risk. Do not put sensitive buyer data into a tool before you have the right and the approval to do so.

The next chapter moves from the packaging of the offer to building a lawful, usable target list for the first conversations.