Price ai products
Skill hiteshbandhu/skills-i-use/skills/ai-engineer-talks/price-ai-products
Runs Stripe-style workflows for AI product pricing — value definition, charge metrics, hybrid models, billing guardrails, and fast iteration. Use when the user prices an AI feature, picks usage vs seats, designs credits, or says "AI pricing", "hybrid pricing", "margin risk", "price AI SaaS".From its SKILL.md
npx -y skills add hiteshbandhu/skills-i-use --skill price-ai-productsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
0.8 KB, 128 tokens by cl100k_base, as published. Nobody here has run it
Price AI products
Playbook from Mayank Pant (Stripe). Five workflows map to the five-step framework in workflows.md.
├─ Define customer-perceived value → A
├─ Choose charge metric → B
├─ Pick pricing model (hybrid default) → C
├─ Add billing guardrails → D
└─ Iterate pricing (hypothesis, not final) → E
Source: playlists/aie-for-founders/. Optional: {SKILL_OUTPUT_DIR}/price-ai-products/
What ships with it: 3 files
2.6 KB alongside SKILL.md
- README.md412 B
- source-index.md317 B
- workflows.md1.9 KB
Gives 0 of the 12 instructions most pricing monetisation skills give in 128 tokens
Counted across 324 of the 339 authors here whose files we hold, read 2026-09-06
- Read product marketing context before asking questionsin 39 of 324, across 16 files
- Demonstrate paid feature value with previewsin 21 of 324, across 8 files
- Choose a value metric that scales with customer valuein 21 of 324, across 14 files
- Verify webhook signatures on every eventin 19 of 324
- Send trial expiration warnings earlyin 16 of 324, across 6 files
- Minimize steps from paywall to paymentin 15 of 324, across 5 files
- Price between next best alternative and perceived valuein 15 of 324, across 7 files
- Grandfather existing customers when raising pricesin 14 of 324, across 10 files
- Understand upgrade context, product model, and user journey firstin 14 of 324, across 5 files
- Show paywalls only after users experience valuein 13 of 324, across 6 files
- Include an escape hatch on every paywallin 12 of 324, across 4 files
- A/B test paywall variationsin 11 of 324, across 3 files
Said here and by no other author read
- define customer-perceived value
- pick the pricing model, defaulting to hybrid
- add billing guardrails
- treat pricing as hypothesis, not final
- follow the five-step framework in workflows.md
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.