An offer is everything a buyer gets for the price, framed around the result
they want. When good products do not sell, the usual cause is that buyers
cannot see how the offer gets them past the obstacles they already expect. This
skill builds the offer from those obstacles, scores its perceived value,
checks that every component earns its cost, prices the guarantee into the
contribution, and refuses fake urgency.
The agent works from the buyer's words: obstacles, objections and the result
they want come from interviews, reviews or panel answers, not from the seller's
feature list.
For setting the price point, tiers and value metric, use a pricing skill; this
one designs what the price buys.
The obstacle list shapes this output more than anything else: the offer is
built to remove them. Settle the inputs below before producing anything. When
one is missing or vague and would change the result, ask about it; when it
wouldn't, use a sensible default and say which one you used.
obstacle invented by the seller produces a component nobody values.
guarantee is affordable.
and the score must not credit proof that does not exist.
could verify it.
Ask about the two or three inputs that matter most for this request, not the
whole list. If the user wants a result straight away, produce it and state your
assumptions at the top, marking estimated values and costs.
python3 business-growth/offer-design/scripts/offer_scorer.py \
--input business-growth/offer-design/assets/sample_offer.json
python3 business-growth/offer-design/scripts/offer_scorer.py \
--input business-growth/offer-design/assets/sample_offer_flawed.json --format json
| Tool | Input | Output | Exit codes |
|---|---|---|---|
offer_scorer.py | Offer JSON | Value score 0-100, best lever, stack ratio, obstacle coverage, component efficiency, contribution after guarantee, findings | 0 no fail, 1 fail finding, 2 bad input |
Stdlib-only and deterministic, with --format text|json. The scoring formula is
printed in --help so every number can be checked by hand.
(references/offer-construction.md, section 1). If two are weak, rework who
the offer is for before designing anything.
and after. Pull them from interviews, reviews of alternatives or panel
objections.
its delivery cost.
days to first result, effort.
python3 business-growth/offer-design/scripts/offer_scorer.py --input offer.json
effort and time to the first result.
terms, and enter an honest claim rate. The scorer subtracts expected claims
from contribution and fails a guarantee that makes sales lose money.
deadline) and mark it verifiable. The scorer fails unverifiable urgency.
assets/offer-sheet-template.md.then a real priced test.
component that answers it, re-score and re-test.
Use this checklist; each item must pass:
| Situation | Guarantee | Confidence |
|---|---|---|
| Results depend on the buyer's participation | Conditional (did the work, no result, refund) | [PROVEN] |
| Low delivery cost, strong onboarding | Unconditional within a window | [RECOMMENDED] |
| Measurable result with a delivery track record | Outcome guarantee | [RECOMMENDED] |
| Heavy front-loaded delivery cost, high belief already | None, with proof instead | [RECOMMENDED] |
| Weakest signal | Lever | Why |
|---|---|---|
| Belief under 6 | [PROVEN] Proof and a guarantee | New businesses lose most buyers on "will this work for me" |
| Effort 7+ or first result over 90 days | [RECOMMENDED] Done-for-you parts, a week-one win | Cheaper to fix than outcome size |
| Stack under 3x price | [RECOMMENDED] Add obstacle-removing bonuses before cutting price | Price cuts invite matching; stack changes do not |
| Coverage under 100% | Add a component per unanswered obstacle | An unanswered obstacle is a standing reason to say no |
| Check | Warn | Fail |
|---|---|---|
| Stack value / price | Under 3x | Under 1x |
| Obstacle coverage | Any obstacle unanswered | Under 60% |
| Component value / cost | Under 3x | — |
| Contribution after guarantee | Under 20% of price | Zero or below |
| Urgency | — | No reason, or not verifiable |
| Belief without proof | 8+ with fewer than 2 proof items | — |
Mistake: Listing everything the product does as bonuses, regardless of what the buyer worries about.
Why it happens: The seller knows the features and assumes more equals better.
Instead: Start from obstacles. A component that answers no obstacle reads as
padding and lowers perceived value; the scorer flags it.
Mistake: Offering a no-questions refund on a product with high delivery cost and weak onboarding.
Why it happens: Strong guarantees lift conversion in case studies, and the claim rate is never estimated.
Instead: Price the guarantee in: expected claims times price comes out of
contribution. Pick a conditional guarantee when results depend on participation.
Mistake: Adding a deadline or "only a few left" that is not true.
Why it happens: Urgency lifts short-term conversion, and the cost lands later.
Instead: Use only constraints a buyer could check: cohort dates, capacity
caps, published price changes. Fake scarcity breaks trust and can breach
consumer-protection rules.
Mistake: Responding to "too expensive" by cutting the price.
Why it happens: It is the fastest change and the objection names price.
Instead: First raise belief, cut effort and add obstacle-removing components;
re-test at the same or a higher price. "Too expensive" often means "not sure it
will work for me".
Mistake: Rating belief 8-9 because the founder is confident.
Why it happens: The seller scores from their own view rather than the buyer's.
Instead: Score belief from the buyer's side and back anything above 7 with
proof. The scorer warns when the score is not earned.
references/offer-construction.md — market check, the four value drivers,building from obstacles, guarantee types and affordability, honest urgency,
naming, testing, and offer versus price
| File | Purpose |
|---|---|
scripts/offer_scorer.py | Scores value, stack, coverage, efficiency, guarantee cost and urgency |
references/offer-construction.md | The method behind the scorer |
assets/sample_offer.json | Sound example: beginner bouldering course (exit 0) |
assets/sample_offer_flawed.json | Deliberately flawed example: online course with fake urgency (exit 1) |
assets/offer-sheet-template.md | One-page offer sheet to fill after scoring |
In Scope:
offer_scorer.pyOut of Scope:
Important Caveats:
consistent; it does not make them true. Validate with real buyers.
benchmark across businesses.
deadline or scarcity claims checked against local consumer-protection law.