Home›AI Agency Academy›Lesson 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, 2026•15–25 minutes•Free AI agent course
What you will learn

Write the proposal scope

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.

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

How to write the proposal scope

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

Worked case: sell scope, not hype

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

Complete the working artifact

Current state: [description]. First-release scope: [list]. Client duties: [list]. Delivery duties: [list]. Exclusions: [list]. Launch gate + proof: [details].
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.

Lesson progress

Finished this lesson?

Save your place on this device so it is easy to pick up where you left off.

Not marked complete yet.