JasonColapietro/suede-creator-skills / skills/suede-offers
suede-offers
VerifiedSuede Offer Design Skills: risk reversal, value levers, scope, proof, bonuses, guarantees, deadlines, and testable persuasion hypotheses. Use when asked "improve this service offer" or to diagnose a course, agency, coaching, or B2B offer. NOT FOR: SaaS tier architecture (suede-pricing), sales-page copy (suede-copy), upgrade screens (suede-paywalls), or clinical advice.
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 4.4 KB |
| SKILL.md | skill md | 10.0 KB |
| agents/openai.yaml | config | 642 B |
| evals/evals.json | config | 4.5 KB |
| references/behavioral-models.md | markdown | 24.1 KB |
| references/bonus-stacking.md | markdown | 7.6 KB |
| references/examples.md | markdown | 9.6 KB |
| references/guarantee-design.md | markdown | 7.9 KB |
| references/offer-anatomy.md | markdown | 8.6 KB |
| references/offer-formats.md | markdown | 10.3 KB |
| references/scarcity-urgency.md | markdown | 9.3 KB |
| references/value-levers.md | markdown | 7.6 KB |
| references/worked-contract.md | markdown | 2.2 KB |
references/value-levers.md
View on GitHub# The Suede Value Levers
Suede's core frame for offer design. A buyer weighs what they expect to get against what it costs them besides money, then compares that to the price. Four levers move the result.
## The formula
```
Outcome × Confidence
Value = ───────────────────────────
Wait × Effort
```
- **Outcome**: the result the buyer actually wants, usually one level above the surface ask.
- **Confidence**: how strongly they believe it will work for them specifically.
- **Wait**: time to the first win and to the full result.
- **Effort**: everything they give up besides money: time, learning, decisions, willpower, social risk.
The customer compares the *Value* score to the *Price*. If Value > Price, they buy. If not, they don't, no matter how good the copy is.
**Price is the comparison, not the value.** Most "lower the price" requests are actually "raise the numerator or lower the denominator" requests.
---
## Lever 1: Outcome (numerator)
What the customer *actually* wants, usually one or two levels above the surface ask.
### Surface ask → outcome
| Surface ask | Outcome |
|-------------|---------------|
| "I want a website" | "I want more qualified leads I can close" |
| "I want to learn copywriting" | "I want to write copy clients pay me $5K+ per project for" |
| "I want a meal plan" | "I want to feel confident in a swimsuit on a beach in 12 weeks" |
| "I want fitness coaching" | "I want my back pain gone so I can pick up my kids without thinking about it" |
| "I want a Notion template" | "I want to feel in control of my work for the first time in years" |
| "I want to lower CAC" | "I want a marketing engine I can step away from for two weeks without things breaking" |
### How to increase
- **Name it specifically.** "Feel confident in a swimsuit" beats "lose weight." The specific name is the offer.
- **Connect to the bigger goal.** The outcome behind the surface ask is almost always emotional or identity-based.
- **Show the future state in concrete sensory terms.** What does the morning of day one *after they have it* actually look like?
### Common mistake
Pitching the surface ask. ("Get a website" instead of "get a website that brings you 5 qualified leads a week.") The bigger the buyer's pain, the more important this is: they're not buying a deliverable, they're buying a future.
---
## Lever 2: Confidence (numerator)
Do they actually believe they'll get the outcome? This is the single most underweighted lever: most offers are perfectly fine on the outcome side but the buyer just doesn't think it'll work *for them*.
### How to increase
- **Proof**: case studies with names, numbers, before/after metrics, photos. Specific > glossy.
- **Methodology specificity**: name your process. "The 5-step VAULT framework" beats "our proprietary system." Even if the substance is the same, naming it raises confidence.
- **Guarantees**: risk reversal directly raises confidence (more in [guarantee-design.md](guarantee-design.md)).
- **Reduce sample-of-one objection**: show people *like them* who got results. "Other people get results but I'm different" is the universal objection.
- **Pre-empt the failure path**: explicitly address what could go wrong and how you handle it. Builds trust faster than hiding the risk.
### Common mistake
Stacking more features ("we also include X, Y, Z") instead of stacking more proof. Features address outcome. Proof addresses confidence. Most stuck offers need proof, not features.
---
## Lever 3: Wait (denominator)
How long from purchase to result. The denominator is doing a lot of work here: slow results don't just feel slow, they erode confidence (the longer it takes, the less the buyer believes it'll work).
### How to decrease
- **Faster first win**: find the smallest possible early result and engineer it into the first 7 days
- **Onboarding velocity**: replace a 60-minute kickoff with a 10-minute async intake and a recorded walkthrough
- **Front-load the assets**: give the templates / swipe files / decks on day 1, not "throughout the program"
- **Faster end-to-end timeline**: "in 8 weeks" beats "in 6 months." If you can credibly compress, do.
- **Quick-start path**: explicit "first thing to do today" so they don't lose momentum
### Common mistake
Promising a faster timeline than you can deliver. The first time you miss it, confidence for every future buyer drops permanently as the failure story spreads.
---
## Lever 4: Effort (denominator)
What the buyer pays *besides money*: time, learning curve, decisions, willpower, social risk, opportunity cost.
### How to decrease
- **Done-for-you over do-it-yourself**: DFY tiers move the effort to you. Charge accordingly.
- **Fewer decisions**: every decision the buyer makes is friction. Bundle, default, recommend.
- **Lower learning curve**: pre-built templates, examples, defaults. "We did the thinking, you do the executing."
- **Removed risk**: emotional risk (am I dumb if this doesn't work?), social risk (what will my team think?), opportunity cost (what am I not doing while I do this?). Address all three explicitly.
- **Async over live**: for many buyers (founders, executives), removing synchronous commitments is huge value
- **Less willpower required**: automation, accountability, environmental design
### Common mistake
Overestimating how much your buyer *enjoys* the work. They want the outcome, not the process. (Exception: identity-buyers: fitness, learning, mastery. For those, the process *is* part of the outcome. Read your buyer.)
---
## Diagnostic: scoring the levers
When an offer is stuck, score each lever 1–10 honestly. The lowest is the binding constraint.
### Quick scoring prompts
- **Outcome (1–10)**: Can the buyer picture, in concrete sensory terms, the day after this works? Is the outcome named specifically enough that they can repeat it back to a friend?
- **Confidence (1–10)**: Do they have at least three named, comparable proof points? Is the methodology specific enough to repeat? Have you addressed the "but my situation is different" objection?
- **Wait (1–10)**: What's the first concrete win, and how soon do they get it? What's the end-to-end timeline? Are there any "delay surfaces" (onboarding lag, asset drip, week-1 friction)?
- **Effort (1–10)**: How much work does the buyer do? How many decisions? How much learning curve? How much synchronous time? How much emotional/social/opportunity-cost risk?
### Worked example: a stuck $3K copywriting course
Initial scoring:
- Outcome: 6 (`become a better copywriter`, too vague)
- Confidence: 4 (one testimonial, no methodology name)
- Wait: 5 (6-month course, no first-win mechanic)
- Effort: 4 (lots of homework, live calls, weekly assignments)
Lowest: effort and confidence are tied. Pick one (confidence, easier to move and unblocks more downstream work):
- Name the methodology: "The VAULT framework: 5 angles every winning sales page uses"
- Add 8 named-customer case studies with before/after copy + revenue numbers
- Add an "even if you've never written before" cohort with 3 named graduates
After: re-score confidence and measure sales-page conversion against the prior cohort. Next cycle, attack effort (replace weekly live calls with async + 1 live Q&A).
---
## Key idea to internalize
**The price-vs-value comparison happens in the buyer's head, not yours.** You only know it's working when the buyer can articulate the outcome back to you in their own words, and when they don't need to ask "but does this actually work?"
If they're asking either of those questions, you have a Value Levers problem, not a copy problem.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |