pricing
Skill258 starsChanged 28 days agoMITView on GitHub
Use this skill to decide what to charge: 'how much should I charge,' 'what should I charge my first customers,' 'pricing tiers,' 'freemium or free trial,' 'should I raise my prices,' or 'pricing page.' Before 10 paying customers it sets one simple price and works out how many customers the founder needs. After 10 it designs tiers from how real customers differ. Not for setting up Stripe or billing code (use payments) or for runway and the quit number (use finances).
58 other projects use a version of this.
Adopted by
Most recently taken up by
- alpit-patel/seo-aeo-geo-kittheir own version, first seen Nov 8, 2026
- insight68/Skillstheir own version, first seen Nov 8, 2026
- Jakeschincariol/whale-skilltheir own version, first seen Nov 8, 2026
- pixelswithbliss/claude-skillstheir own version, first seen Nov 1, 2026
- salacoste/daytona-seo-notchtheir own version, first seen Nov 1, 2026
- GAPZ787/claude-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use grow-sustainably, processize and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
slavingiaSkillgrow-sustainably
Evaluate business decisions through the lens of sustainable, profitable growth. Use when someone is making decisions about spending, hiring, fundraising, or scaling their business.
Also in 7 projects that use this
slavingiaSkillprocessize
Turn a product idea into a manual-first process you can start delivering today. Use when you have an idea and want to figure out how to deliver value by hand before writing any code.
Also in 7 projects that use this
CesarjoquinSkillpaywalls
When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.
Also in 19 projects that use this
CesarjoquinSkillpopups
When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.
Also in 18 projects that use this
coreyhaines31Skillmarketing-council
When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing mentors,' or asks how a famous marketer would approach their problem. The council gives each advisor's take through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. For executing the winning direction, hand off to positioning, offers, copywriting, ads, or the relevant skill.
Also in 14 projects that use this
- +6 more from Cesarjoquin
- +1 more from slavingia
Other versions58 projects use a version of this.
Word for word · 1
- whawkinsiv/solo-founder-skills★ 260100% same
Edited · 0
None found.
Wrote their own version · 57
- coreyhaines31/marketingskills★ 59ksame name
- slavingia/skills★ 11ksame name
- Nexus-JPF/note-companion★ 874same name
- AIDevGTM/gtm-cofounder★ 334same name
- QuantConnect/Documentation★ 268same name
- Piebald-AI/splitrail★ 228same name
- Cesarjoquin/Marketing-Skills★ 190same name
- open-fox/agents★ 55same name
- firatcand/founder-skills★ 37same name
- SZcalligrapher/slash-skills-subscription★ 32same name
47 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- about-meSkill
- beautifySkill
- buildSkill
- contentSkill
- domain-nameSkill
- emailSkill
- financesSkill
- first-customersSkill
- focusSkill
- go-liveSkill
- humanizeSkill
- is-this-an-appSkill
- journeySkill
- landing-pageSkill
- legalSkill
- paymentsSkill
- retentionSkill
- secureSkill
- seoSkill
- validateSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 52 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Ask how many people pay today.
- Distinctive: line 18
Set one price: No tiers, no free plan. Base it on what the customer spends on the problem today, in money or in hours multiplied by their …
- Distinctive: line 28
Raise the price as you go: When most people say yes without hesitation, the price is too low.
- Distinctive: line 30
If buyers need to try before they pay, offer a short trial that ends in payment, or a refund guarantee.
- Distinctive: line 45
Keep existing customers at their price for at least 6–12 months, or for good.
- Distinctive: line 53
Do not copy a competitor's price: Use it as an anchor only. Their costs, customers, and strategy are not yours.
“Common” is measured: kept by at least 6 in 10 of the 52 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Pricing
Charge from the first customer. A free user tells you they like free things. A paying customer tells you the problem is worth money.
Step 1: Find the stage
Ask how many people pay today. Before 10, use Step 2. From 10 on, use Step 3.
Step 2: Before 10 paying customers
- Set one price. No tiers, no free plan. Base it on what the customer spends on the problem today, in money or in hours multiplied by their hourly rate. Your costs set the floor, not the price.
- Check the anchor. What do these customers already pay for tools? A $49 add-on feels small to someone paying $300 a month for software, and large to someone who pays nothing.
- Do the customer math with the founder:
Show the timeline, so the founder sees the effect of price. At $99, the same goal needs 41 customers. finances has the full quit-number worksheet.Income needed per month ÷ price = customers needed e.g. \$4,000 ÷ \$49 = 82 customers At one new customer per week, that is about 18 months. - Take the money simply: a payment link or an invoice (see payments). Billing code can wait.
- Raise the price as you go. When most people say yes without hesitation, the price is too low. Raise it for new customers, and keep early customers at their price.
If buyers need to try before they pay, offer a short trial that ends in payment, or a refund guarantee. Do not offer a free plan.
Step 3: From 10 paying customers
- Choose the value metric: the unit that grows as customers get more value, and that they can predict: seats, projects, contacts, usage. Avoid gating that relies only on features, and flat prices that cannot grow.
- Build 2–3 tiers from real differences among the first customers: size, usage, or the job they hire the product for. Each tier gives a clear reason to move up, such as a limit they hit or a feature only one group needs.
- Free plan or trial:
- A free plan works only when free users bring paying users (they invite others or share output) and cost almost nothing to serve.
- A free trial fits products whose value needs setup to see.
- Most early products need neither: a trial that ends in payment is enough.
- Annual plans: offer about two months free. They help cash flow and reduce churn.
- The pricing page: mark the recommended plan, show the price, and answer "Can I cancel?" and "What happens to my data?" Hide prices only for a custom enterprise plan.
Changing prices
- Keep existing customers at their price for at least 6–12 months, or for good.
- Change prices for new sign-ups first.
- Announce increases at least 30 days ahead, with the reason.
Rules
- Most founders underprice. A price nobody complains about is too low.
- Price is a signal. Too low says "toy." Too high, without proof, says "not for me."
- Do not copy a competitor's price. Use it as an anchor only. Their costs, customers, and strategy are not yours.
Output
Stage: <before 10 / from 10>
Price: <amount, and the reason in one sentence>
Customer math: <customers needed for the founder's goal, and the timeline>
How to charge: <payment link / invoice / checkout>
Review on: <date, usually after the next 10 customers>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.

