jasoncolapietro/suede-pricing
Suede-owned pricing and packaging discipline. Use when deciding what to charge, structuring tiers, choosing a value metric, comparing free trials with freemium, researching willingness to pay, or planning a price increase. NOT FOR: in-product upgrade screens (use suede-paywalls), offer bonuses and guarantees (use suede-offers), or executing billing changes.
npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-pricing
Suede Pricing turns verified product economics, buyer evidence, and commercial
constraints into testable prices, value metrics, tiers, and migration plans.
It produces a decision brief and measurement plan while keeping billing changes
behind explicit approval.
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
1. Packaging — What's included at each tier?
2. Pricing Metric — What do you charge for?
3. Price Point — How much do you charge?
Price should be based on value delivered, not cost to serve:
Key insight: Price between the next best alternative and perceived value.
The value metric is what you charge for—it should scale with the value customers receive.
Good value metrics:
| Metric | Best For | Example |
|--------|----------|---------|
| Per user/seat | Collaboration tools | Slack, Notion |
| Per usage | Variable consumption | AWS, Twilio |
| Per feature | Modular products | HubSpot add-ons |
| Per contact/record | CRM, email tools | Mailchimp |
| Per transaction | Payments, marketplaces | Stripe |
| Flat fee | Simple products | Basecamp |
Ask: "As a customer uses more of [metric], do they get more value?"
Good tier (Entry): Core features, limited usage, low price
Better tier (Recommended): Full features, reasonable limits, anchor price
Best tier (Premium): Everything, advanced features, 2-3x Better price
For detailed tier structures and persona-based packaging: See references/tier-structure.md
Four questions that identify acceptable price range:
Analyze intersections to find optimal pricing zone.
Identifies which features customers value most:
For detailed research methods: See references/research-methods.md
Market signals:
Business signals:
Product signals:
migrations without verified live state, a maximum-cost check, and explicit
approval.
measured unless current research or product data supports it.
business to a price; return a recommendation, assumptions, and validation
plan for the user to decide.
suede-paywalls for in-product upgrade and paywall experiences.suede-offers for bonuses, guarantees, and offer framing.suede-ab-testing to validate pricing-page or packaging hypotheses.suede-revops for approved deal-desk and pipeline implementation.Take jasoncolapietro/suede-pricing from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.