Founder offer skill

Builds an offer too good to refuse.

by Jakeschincariol·MIT license·★ 322 Stars on the repo·GitHub ↗

Use now

Inside this skill

SKILL.md · the author's own words
# founder-offer

Most businesses sell a product. Good ones sell an offer: the product plus
everything that makes buying it an easy yes. This skill builds that, using the
Offers lens in `../founder-board/lenses.md` as the method (a summary of the
framework in Alex Hormozi's *$100M Offers*; never present it as his words).

## Step 1: read what is already known

- `founder/idea.md` and `founder/pitch.md`: what is sold today.
- `founder/panel/results.md`: why buyers pass, in their words. This is the raw
  material: every top objection should be answered by something in the offer.
- `founder/numbers.json`: what each extra costs, so the stack stays profitable.
- `founder/board.md`: the board's conditions.

## Step 2: the problem list

Word-for-word excerpt, not a result. Read the full SKILL.md ↓

Files of Founder offer

Jakeschincariol/main1 file shown
SKILL.md
Show the full text76 lines

founder-offer

Most businesses sell a product. Good ones sell an offer: the product plus everything that makes buying it an easy yes. This skill builds that, using the Offers lens in ../founder-board/lenses.md as the method (a summary of the framework in Alex Hormozi's $100M Offers; never present it as his words).

Step 1: read what is already known

  • founder/idea.md and founder/pitch.md: what is sold today.
  • founder/panel/results.md: why buyers pass, in their words. This is the raw material: every top objection should be answered by something in the offer.
  • founder/numbers.json: what each extra costs, so the stack stays profitable.
  • founder/board.md: the board's conditions.

Step 2: the problem list

Write every obstacle between the buyer and the result they want, in the buyer's words: before buying (doubt, price, effort to switch), during (waiting, learning, inconvenience), after (does it last, what if it fails). Aim for 15 to 30. Pull from the panel objections and the competitor complaints first.

Step 3: solutions, trimmed and stacked

Turn each problem into a solution (a feature, a service, a guarantee, a format). Score each on value to the buyer (1 to 5) and cost to deliver (1 to 5, from the CFO's numbers). Keep high value, low cost. Stack what is left into:

  • The core: the thing itself, described by the outcome, not the ingredients.
  • Bonuses: two or three, each killing one specific objection.
  • The guarantee: what happens if it does not deliver. Model what it costs at a realistic claim rate with the CFO's tool before promising it.
  • Urgency and scarcity: only if they are true (a launch week, a limited first batch). Never fake a countdown or a "only 3 left".
  • The name: a clear, specific name for the offer, not the company.

Step 4: score it

On the value equation, before and after, 1 to 10 each: dream outcome, perceived likelihood of getting it, time to the result, effort and sacrifice. Say which element of the stack moves which score.

Step 5: re-test it

Write the new offer into founder/pitch.md (keep the old one as founder/pitch-v1.md) and run /founder-consumer --quick with the same seed. Report the buy rate before and after and which objections dropped. If nothing moved, say so: the problem may be the market or the price, not the offer.

Rules

  • Every promise must be deliverable and affordable; check costs with the CFO.
  • No fake reviews, testimonials, scarcity, discounts or "as seen on".
  • Follow the advertising and consumer-protection rules of the user's market for guarantees and claims (health claims especially). Not legal advice.

Output

founder/offer.md (problem list, the stack, costs, the value-equation scores, the re-test result) and the updated founder/pitch.md. Next: /founder-cfo to re-run the numbers with the stack, then /founder-marketing.

1---
2name: founder-offer
3description: >-
4 Builds an offer too good to refuse. Lists every problem the buyer hits on the way
5 to the result they want, turns each into a solution, trims to what is cheap to
6 deliver and valuable to the buyer, and stacks it with honest bonuses, a guarantee
7 the CFO can afford, real urgency and a clear name. Scores it on the value
8 equation (outcome, likelihood, time, effort) and re-tests it on a quick buyer
9 panel. Use when the user says "make my offer better", "why won't people buy",
10 "what should I include", "guarantee", "bonuses", "grand slam offer", or after the
11 panel shows people passing.
12argument-hint: "[what you sell]"
13---
14 
15# founder-offer
16 
17Most businesses sell a product. Good ones sell an offer: the product plus
18everything that makes buying it an easy yes. This skill builds that, using the
19Offers lens in `../founder-board/lenses.md` as the method (a summary of the
20framework in Alex Hormozi's *$100M Offers*; never present it as his words).
21 
22## Step 1: read what is already known
23 
24- `founder/idea.md` and `founder/pitch.md`: what is sold today.
25- `founder/panel/results.md`: why buyers pass, in their words. This is the raw
26 material: every top objection should be answered by something in the offer.
27- `founder/numbers.json`: what each extra costs, so the stack stays profitable.
28- `founder/board.md`: the board's conditions.
29 
30## Step 2: the problem list
31 
32Write every obstacle between the buyer and the result they want, in the buyer's
33words: before buying (doubt, price, effort to switch), during (waiting, learning,
34inconvenience), after (does it last, what if it fails). Aim for 15 to 30. Pull
35from the panel objections and the competitor complaints first.
36 
37## Step 3: solutions, trimmed and stacked
38 
39Turn each problem into a solution (a feature, a service, a guarantee, a format).
40Score each on value to the buyer (1 to 5) and cost to deliver (1 to 5, from the
41CFO's numbers). Keep high value, low cost. Stack what is left into:
42 
43- **The core**: the thing itself, described by the outcome, not the ingredients.
44- **Bonuses**: two or three, each killing one specific objection.
45- **The guarantee**: what happens if it does not deliver. Model what it costs at a
46 realistic claim rate with the CFO's tool before promising it.
47- **Urgency and scarcity**: only if they are true (a launch week, a limited first
48 batch). Never fake a countdown or a "only 3 left".
49- **The name**: a clear, specific name for the offer, not the company.
50 
51## Step 4: score it
52 
53On the value equation, before and after, 1 to 10 each: dream outcome, perceived
54likelihood of getting it, time to the result, effort and sacrifice. Say which
55element of the stack moves which score.
56 
57## Step 5: re-test it
58 
59Write the new offer into `founder/pitch.md` (keep the old one as
60`founder/pitch-v1.md`) and run `/founder-consumer --quick` with the same seed.
61Report the buy rate before and after and which objections dropped. If nothing
62moved, say so: the problem may be the market or the price, not the offer.
63 
64## Rules
65 
66- Every promise must be deliverable and affordable; check costs with the CFO.
67- No fake reviews, testimonials, scarcity, discounts or "as seen on".
68- Follow the advertising and consumer-protection rules of the user's market for
69 guarantees and claims (health claims especially). Not legal advice.
70 
71## Output
72 
73`founder/offer.md` (problem list, the stack, costs, the value-equation scores, the
74re-test result) and the updated `founder/pitch.md`. Next: `/founder-cfo` to re-run
75the numbers with the stack, then `/founder-marketing`.
76 

Discussion