founder-offer
Skill131 starsChanged 37 days agoMITView on GitHub
Builds an offer too good to refuse. Lists every problem the buyer hits on the way to the result they want, turns each into a solution, trims to what is cheap to deliver and valuable to the buyer, and stacks it with honest bonuses, a guarantee the CFO can afford, real urgency and a clear name. Scores it on the value equation (outcome, likelihood, time, effort) and re-tests it on a quick buyer panel. Use when the user says "make my offer better", "why won't people buy", "what should I include", "guarantee", "bonuses", "grand slam offer", or after the panel shows people passing.
In this repository10 other files it gives its agents.
- founder-boardSkill
- founder-brandSkill
- founder-cfoSkill
- founder-competitorsSkill
- founder-consumerSkill
- founder-launchSkill
- founder-marketingSkill
- founder-opsSkill
- founder-planSkill
- founder-pricingSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
Write every obstacle between the buyer and the result they want, in the buyer's words: before buying (doubt, price, effort to switch), …
- Distinctive: line 47
Urgency and scarcity: only if they are true (a launch week, a limited first batch).
- Very specific: line 59
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.
- Distinctive: line 66
Every promise must be deliverable and affordable.
- Distinctive: line 67
No fake reviews, testimonials, scarcity, discounts or "as seen on".
- Distinctive: line 68
Follow the advertising and consumer-protection rules of the user's market for guarantees and claims (health claims especially).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.mdandfounder/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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

