Skip to content

borghei/Claude-Skills / business-growth/offer-design

offer-design

Verified

Build an offer from the buyer's obstacles: component stack, value drivers, an affordable guarantee and honest urgency, scored before launch. Use when buyers say no, packaging bonuses, choosing a guarantee, or naming an offer.

references/offer-construction.md

View on GitHub
# Offer Construction

An offer is everything the buyer gets for the price, framed around the result
they want. Most offers fail not because the product is weak but because the
buyer cannot see how it gets them past the obstacles they already expect. This
reference covers building an offer from those obstacles, scoring its perceived
value, choosing a guarantee the business can afford, and using urgency honestly.

## 1. Start with the market, not the offer

No offer rescues a buyer group that lacks one of these:

| Condition | Question | Red flag |
|-----------|----------|----------|
| Pain | Is the problem costly or frustrating enough to act on now? | "Nice to have" language in every interview |
| Budget | Do they already spend money on this or something close? | No existing spend anywhere in the category |
| Reach | Can you name where to find a hundred of them this month? | "Everyone" or "social media" as the channel |
| Momentum | Is the group growing or shrinking? | A shrinking group with entrenched habits |

If two of the four are weak, rework who the offer is for before reworking the offer.

## 2. The four value drivers

Perceived value rises with the size of the outcome and the buyer's belief they
will get it; it falls with the time until the result and the effort asked of
them. Score each from the buyer's point of view, not the seller's.

| Driver | Scored as | Raise it by |
|--------|-----------|-------------|
| Outcome | 1-10: how much the result matters to the buyer | Naming the specific result in the buyer's words |
| Belief | 1-10: how sure the buyer is they will get it | Proof: results from similar buyers, demonstrations, credentials, a guarantee |
| Days to result | Days until the first result the buyer can feel | A quick first win in week one, staged milestones |
| Effort | 1-10: work, change and sacrifice asked | Done-for-you parts, templates, fewer steps, included equipment |

The scorer combines them into a 0-100 value score. Belief is usually the
weakest driver for a new business with no track record, and time and effort
are usually the cheapest to improve.

**Do not score belief above 7 without proof.** The scorer warns when belief is
8 or more with fewer than two proof items.

## 3. Build from obstacles

1. **List the obstacles.** Every problem the buyer expects between paying and
   getting the result: before they start, while they use it, and after. Pull
   them from buyer interviews, reviews of alternatives and panel objections.
2. **Turn each into a component.** For every obstacle, write the thing in the
   offer that removes it. One component can answer several obstacles.
3. **Value and cost each component.** Buyer value is what the buyer would pay
   for it alone or what the problem costs them; delivery cost is what it costs
   the business per sale.
4. **Trim.** Keep components that return at least three times their cost in
   buyer value. Cut or rework the rest. Cut anything that answers no obstacle:
   filler makes the stack feel padded.
5. **Check the stack.** Total buyer value should be three or more times the
   price. Under one times, the offer is overpriced for what it contains.

### Core versus bonus

Core components deliver the result. Bonuses remove a specific obstacle that
would stop a buyer from saying yes or from finishing. A bonus that removes no
obstacle is decoration, and buyers discount it.

## 4. Guarantees

A guarantee reverses the risk the buyer feels. Choose the strongest one the
contribution can afford.

| Type | Promise | When it fits |
|------|---------|--------------|
| `none` | No refund | Belief already high, or cost of delivery is front-loaded |
| `conditional` | Refund if the buyer did their part and did not get the result | Results depend on participation (courses, coaching, programs) |
| `unconditional` | Refund for any reason within a window | Low delivery cost, confident product, low expected claims |
| `outcome` | A specific result or the business works for free / pays back | Proven delivery with measurable results |

**Afford it.** Expected guarantee cost per sale is price times expected claim
rate. The scorer subtracts it from contribution. A guarantee that makes each
sale lose money is a fail, not a marketing choice.

**Estimate the claim rate honestly.** Conditional guarantees on participation
programs usually see low single-digit claim rates; unconditional guarantees on
digital products with weak onboarding can see far higher. Use your own refund
history where it exists.

**Write the terms.** A guarantee without written terms invites disputes; the
scorer fails one with no terms.

## 5. Urgency and scarcity

Urgency that is real helps buyers decide. Urgency that is invented destroys
trust the moment it is noticed, and in many markets it is a consumer-protection
problem.

| Type | Real example | Fake example |
|------|--------------|--------------|
| `deadline` | Early price ends on the published opening date | A countdown that resets for every visitor |
| `capacity` | Eight places per coach per cohort | "Only 3 left" on a digital download |
| `cohort` | Next group starts on a fixed date | A "closing soon" page that never closes |
| `seasonal` | Garden service booked before spring | A seasonal sale running all year |

The scorer fails urgency that is not marked verifiable or that has no stated
reason. Verifiable means a buyer could check it: a published date, a stated cap,
a calendar.

## 6. Naming the offer

Name the offer by the outcome, the timeframe and, where it matters, the buyer:
"Climb your first V3 in six weeks". Keep it under twelve words. Avoid
superlatives, which lower belief rather than raise it.

## 7. Testing the offer

1. Score the offer and fix every fail.
2. Put it in front of buyers: a simulated panel to find objections fast, then a
   real priced test.
3. Read which objection still blocks the most buyers, add or rework the
   component that answers it, re-score, and test again.
4. Change one thing per round so the result can be attributed.

## 8. Price and offer together

Do not compete only on price. If the only reason to choose the offer is that it
is cheaper, the offer is a commodity and a competitor can match it overnight.
Raise the stack, the belief and the speed to result before lowering the price,
and test whether the improved offer supports a higher price rather than the
same one.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall