HomeAI Agency AcademyLesson 32
Module 08 · Lesson 32

Sell scope, not hype

Present the delivery phases, shared responsibilities, exclusions, risk controls, and success measures plainly.

Last updated August 5, 202615–25 minutesFree AI agent course
What you will learn

Make a clear, safer operating decision.

You will be able to write a proposal that helps a buyer make a decision without implying autonomous performance, compliance certification, or financial results that have not been proven.

Why this matters

Good agent work is useful before it is impressive.

A clear proposal protects both sides. It turns uncertain work into a sequence of decisions: discover, build, test, pilot, review, and either improve, expand, or stop.

Field note 32

Make the relationship visible.

AI AGENTS · FIELD NOTE 32Scope → shared duties → launch gate → reviewTHE PROPOSAL01What changes02Who owns what03What stays out04How it is measuredOriginal visual framework for Sell scope, not hype.AI AGENTS · FIELD NOTE 32Scope → shared duties → launch gate → review01What changes02Who owns what03What stays out04How it ismeasured
Use this framework to make sell scope, not hype visible before you build.
Core concepts

The language that keeps the work clear.

ScopeThe exact workflow, users, systems, channels, and deliverables covered by the agreement.
AssumptionA condition that must be true for the work to proceed as described.
ExclusionWork that is specifically not included, even if it could be requested later.
Launch gateThe agreed evidence and approvals required before a workflow reaches real customers.
The practical method

Work through the decision in order.

Describe the change

State the before state, first release, and intended operating result in plain language.

Break delivery into phases

Use discovery, configuration, test, controlled pilot, review, and optional expansion rather than one black-box promise.

Assign responsibilities

List client policy approvals, data access, staff owner, feedback, and agency implementation or support duties.

State risk and measurement

Show exclusions, safeguards, acceptance tests, metrics, and what happens if the pilot does not meet the agreed criteria.

Worked example

A realistic, bounded implementation.

An agency proposes an inbound qualification workflow for a consulting firm. The proposal includes a discovery workshop, CRM field map, approved questions, test set, pilot with one service line, weekly review, and a measured decision at the end.

It excludes legal advice, changes to the client’s core billing system, and unrestricted outbound messaging. The firm owns policy approval and a named response owner; the agency owns configuration, test evidence, and operating reports.

The buyer can decide with clarity because the proposal describes the work and evidence—not a claim that agents will run the firm without people.

Build it in practice

Use this copyable working template.

Adapt it to the client’s evidence, policy, people, and tools. Do not treat placeholders as approved instructions.

Current state: [description]. First-release scope: [list]. Client duties: [list]. Delivery duties: [list]. Exclusions: [list]. Launch gate + proof: [details].
Spacebrain implementation

Put the operating system around the agent.

Use client workspaces, tasks, approvals, service records, reporting, and shared workflow documentation to make proposal commitments visible during delivery.

Practice

Before you move on

  • Turn one sales pitch into six delivery phases.
  • Add client responsibilities and three exclusions.
  • Ask a delivery lead whether the scope can be tested and supported as written.
  • The proposal is operationally specific.
  • Responsibilities are shared and named.
  • Exclusions and risks are visible.
  • Success is evaluated with agreed evidence.

Build the operating layer around your agent.

Use the free Spacebrain workspace to keep contact context, handoffs, tasks, automation, and reporting together.

Start for free →