Lessons 80.4 and 83.2 asked for offers a stranger can repeat back. This appendix is the blank card plus a filled example: buyer, outcome, proof, included and excluded, price, delivery, and next action — one page, no feature soup.

The blank template

Copy this into OFFER-CARD.md and fill every line. Blank lines are decisions you have not made yet.

# OFFER-CARD.md — [Offer name], [date]

## Buyer (who it is for — and not for)
- For: ___
- Not for: ___

## Outcome (the painful now → the specific after)
- Starting situation: ___
- Finished result: ___
- By when / in what form: ___

## Proof (why a stranger should believe it)
- Method or evidence: ___
- Example, sample, or reference: ___

## Included / excluded (the boundary)
- Included: ___
- Excluded: ___
- Revision / support rule: ___

## Price and terms
- Price: ___ / one-time or recurring: ___
- Payment method: ___ / refund or cancellation rule: ___

## Delivery (how and when they receive it)
- Format and steps: ___
- Timeline: ___ / capacity (slots per month): ___

## Next action (one verb, one path)
- ___

Seven fields, each earning its place. Buyer prevents selling tailoring to people who want a new suit. Outcome states the finished result in the buyer's words, not your tool list. Proof answers "says who?" — a sample, a method, a reference. Included/excluded is the scope boundary from Lesson 82.1: what you will and will not do. Price and terms make the exchange legible. Delivery names format, timeline, and capacity so you cannot overbook. Next action is one verb — book, buy, reply — not three hopeful buttons.

Rules that keep it honest

• Write the outcome before the price. If the outcome is vague ("premium alterations services"), the price will be arbitrary. Lesson 80.5's three questions apply: what result is bought, what delivery costs, what alternative the buyer compares against.
• Name the exclusion that scares you. The line you most want to leave fuzzy ("unlimited tweaks") is the line that will cost you a weekend. Write it while you are calm.
• One buyer per card. A card for "event guests and boutiques and theaters" is three cards hiding in one. Split them.
• Price the delivery you can repeat, not the heroic first run. Include prep, communication, and revision time, not just the visible meeting.
• For packaging and pricing mechanics worth borrowing, compare your draft against the Paddle pricing strategy guide (value metric, packaging, order-of-magnitude price) and check fee reality on Gumroad pricing if you sell a fixed download or membership through a simple storefront.

Filled example: same-week event tailoring (illustrative fictional example, not a real shop quote)

A tailor in the local-business running example filled the card like this:

# OFFER-CARD.md — Same-Week Event Fit, 2026-10-04

## Buyer
- For: event guests with one garment that must fit by Saturday
- Not for: full-wardrobe rebuilds, bridal parties of six, same-day emergencies

## Outcome
- Starting situation: good clothes, wrong fit, event in 5 days
- Finished result: one garment altered, pressed, ready to wear
- By when: pickup Thursday 5pm for Saturday events (drop-off by Monday)

## Proof
- Method: pinned fitting + photographed marks + press checklist
- Example: 40+ event fits this year; photo permission available at pickup

## Included / excluded
- Included: fitting, one alteration pass, pressing, minor hem/seam fix
- Excluded: restyling, fabric replacement, additional garments
- Revision rule: one tweak round within 48 hours of pickup; re-cuts re-quoted

## Price and terms
- Price: $95 fixed, one-time; rush (under 72h) $140 if a slot is open
- Payment: card at drop-off / cancellation: full refund before pinning, none after

## Delivery
- Steps: drop-off + pinning (20 min) → alteration → pressed pickup
- Timeline: 4 days standard / capacity: 6 event slots per week

## Next action
- Book a Monday fitting: reply with garment type + event date

Why it works: a guest can repeat it ("$95, drop Monday, wear Saturday, one garment"). The exclusions protect the tailor from bridal-party scope creep. Capacity (six slots) connects straight to Appendix 83.D's pause trigger — when the seventh inquiry arrives, the answer is next week, not a rushed weekend.

Verify fast

Read the card aloud to someone outside the project. Ask them to repeat who it is for, what they get, what it costs, and what to do next. If any answer is wrong, the card — not the listener — failed. Fix that field, then re-test. Repeat-back passed means shippable.