amazon-returns-recover…
Suede-affiliated Amazon money-recovery audit for restocking fees, short or denied refunds, and Amazon-billed subscriptions. Use…
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, planning a price increase, or tearing down a pricing page for clarity and
$ npx -y skills add JasonColapietro/suede-creator-skills --skill suede-pricing --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/suede-pricingContext preview
The summary Claude sees to decide when to auto-load this skill.
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, planning a price increase, or tearing down a pricing page for clarity and
name: suede-pricing description: "Suede AI pricing and packaging: chooses the value metric (seats, usage, credits, outcomes), structures tiers, compares free trial, freemium, and reverse trial, plans willingness to pay research and price increases with grandfathering, and tears down a pricing page for buyer clarity and for search and AI-assistant readability (text prices, matching schema, quotable FAQ). Returns a Pricing Decision Brief or a scored teardown. Use when deciding what to charge, restructuring tiers, pricing AI features with variable compute cost, raising prices, or fixing a pricing page that buyers or AI answers misread. NOT FOR: in-product upgrade screens (use suede-paywalls), offer bonuses and guarantees (use suede-offers), or executing billing changes." metadata: version: 2.1.0
Suede AI 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):
---
Three axes, decided in this order: **packaging** (what's included per tier), **pricing metric** (what you charge for), **price point** (how much).
Price sits between the next best alternative (the floor) and the customer's perceived value (the ceiling). Cost to serve is a baseline, never the basis.
---
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?"
When a feature's cost to serve scales with model usage, flat per-seat pricing can turn heavy users unprofitable. Common structures:
For each, model margin at the 90th-percentile user, state included limits on the pricing page, and give buyers a usage view before the bill surprises them.
These are the answers a model reaches for unprompted. Each is allowed, but only once you state why it beats the alternative for this product: never by default: **$9/$29/$99** (or any flat 3x ladder); **Starter/Pro/Enterprise** names that carry no product meaning; **exactly three tiers** when the buyer set is two or four; **20% off annual** as the reflex discount; **"Contact us"** on the top tier, which hides price from buyers and from the agents that now shortlist tools (see Pricing Page Teardown); **per-seat** when usage, records, or transactions track value better.
---
**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](references/tier-structure.md)
---
Four questions that identify acceptable price range: 1. Too expensive (wouldn't consider) 2. Too cheap (question quality) 3. Expensive but might consider 4. A bargain
Analyze intersections to find optimal pricing zone.
Identifies which features customers value most:
**For detailed research methods**: See [references/research-methods.md](references/research-methods.md)
---
**Market signals:**
**Business signals:**
Open-source AI skills for SEO, AI search visibility, conversion copy, marketing strategy, and business operations. Reusable workflows for Claude Code and Codex, plus code review, app delivery, and creator tools.
Suede-affiliated Amazon money-recovery audit for restocking fees, short or denied refunds, and Amazon-billed subscriptions. Use…
Suede Labs Android app factory: plan, build, test, and release a production-grade native Android app from a product idea through…
Suede AI full-stack surface builder that runs design, copy, and visual QA as one pass: landing pages, brand surfaces, product UI,…
Suede Labs full writing stack: sharper copy for docs, pages, email, social, headlines, CTAs, product listings, and public…
Suede Labs workflow for turning a website, PWA, dashboard, or marketplace into an iOS app. Use when the user has a live site or…
Suede-owned recovery discipline for recurring charges billed outside Amazon: App Store, Google Play, PayPal, direct-bill…