Your first revenue test is chosen. Now it needs words a stranger can understand in sixty seconds and repeat accurately to someone else. That is the offer — and most beginners substitute a feature list for it.

Offer vocabulary, precisely

• Offer — the whole promise: who it is for, what changes, what is included and excluded, proof, price and terms, and the next action.
• Package — a bundled, bounded version of the offer ("event package," "team plan") with a fixed scope and price.
• Scope — the boundary: what you do and do not do, by when, with how many revisions or seats.
• Deliverable — each tangible thing the buyer receives (brief PDF, fitted garment, working project).
• Outcome — the change the deliverables produce (a decision made Monday, an outfit ready Friday, a skill demonstrated).
• Proof — evidence the promise is credible: sample, method, pilot result, testimonial with specifics.
• Constraint — capacity or eligibility limits stated upfront ("two slots per month," "teams of 3–10").
• Bonus / guarantee / policy — extras and risk terms, only if you can honor them (a walkthrough call, a fix window, a refund path — see 80.6).
• Call to action — the single next step ("reply to book a May slot," "checkout before Friday").

Deliverables without an outcome are inventory. An outcome without scope is a wish.

The page sequence that sells honestly

Every offer page, email, or one-pager follows the same seven-step order. Do not rearrange it — each step earns the next:

1. Who it is for — name the buyer so the right person keeps reading and the wrong person leaves early. 2. Painful current situation — describe their today in their words (three hours of scavenging, a closet of ill-fitting suits, a course backlog never finished). 3. Specific outcome — the after-state with a date ("a source-linked brief on three companies, delivered Friday, ready to forward Monday"). 4. What is included (and not) — deliverables, boundaries, timeline. Exclusions build trust faster than bonuses. 5. Proof / method — a redacted sample, the three-step method, one pilot quote with numbers. 6. Price / terms — one number with its rhythm (one-time, per month, per seat) and the exit path. 7. Next action — one verb, one channel, one deadline.

Run the sequence on the local tailor (illustrative fictional example): "For wedding parties of four (who) facing mismatched off-the-rack suits two weeks out (pain) — everyone fitted and pressed by the Friday before (outcome) — two fittings each, backup hems, one coordinator; shoes and rush remakes excluded (included/not) — 40 parties dressed since 2023, see the photo wall (proof) — $480 fixed for four, balance on pickup (price) — text the shop to hold a May slot (action)." Nothing clever. Everything legible.

Features are not an offer

"AI dashboard with 20 tools, semantic search, and real-time alerts" is a feature list. It does not say whose job completes, by when, or what happens if it does not. Buyers cannot repeat it, so they cannot buy it — or refer it.

Translate every feature into the job it finishes:

| Feature | Offer language |

|---|---|

| 20 dashboard tools | "One Monday brief your team can forward — every claim linked to its source." |

| Premium alterations services | "Same-week tailoring for one event: fitted and pressed by Friday." |

| 40 video lessons | "Ship a working research workflow in four Saturdays, reviewed twice." |

If a line on your page does not change the buyer's picture of *after*, cut it or move it to documentation.

DO: build your OFFER-CARD.md

Exercise. Create OFFER-CARD.md with exactly these fields — one to three lines each:

# OFFER-CARD
Audience: [buyer, by role/situation]
Outcome: [after-state + date]
Included: [deliverables + timeline]
Not included: [explicit exclusions]
Proof: [sample / method / pilot result]
Price architecture: [number + rhythm + exit path]
Capacity: [slots, seats, or clients per period]
Next action: [one verb + channel + deadline]

Finish line: a card someone outside the project can read once and accurately repeat — who it is for, what changes, what it costs, what to do next.

Verify (the repeat test): read it to a friend, take it away, and ask them to restate it. If they reproduce audience, outcome, price, and action without notes, it passes. If they describe features ("something with AI tools?"), rewrite the outcome and exclusions first.

Common failure mode: hiding the exclusions and exit path to seem agreeable. Vague scope produces the worst customers: they expected everything, you resent delivering it, and the testimonial reflects neither. State the boundary on the card.

Check your understanding

1. What is the difference between a deliverable and an outcome? Give one example from your own offer. 2. Why do exclusions build trust faster than bonuses? 3. What is the seven-step offer sequence, and what breaks if price comes before outcome?

Next

Lesson 80.5 prices the offer you just wrote. Not a magic number — a decision system with a floor, a ceiling, and three hypotheses you test in conversation.