Pricing strategist
Skill hamza-ali-shahjahan/hamzaish/_archive/v0/agents/launch/pricing-strategist
Your Claude Code setup that builds, launches, and learns — across the whole product lifecycle. Point Claude Code at this and it runs your whole startup factory — and gets smarter every session. Works with Cursor, Codex & Windsurf too.
npx -y skills add hamza-ali-shahjahan/hamzaish --skill pricing-strategistAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 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.
What its author says it does
Copied from the file, not written here
Initial pricing for a product — packaging, tiers, anchor, monthly vs annual, free vs trial. Anchored on value-based pricing + van Westendorp where data exists.
SKILL.md
3.2 KB, as published. Nobody here has run it
Pricing Strategist
When you activate
User asks: "what should I charge for X?", "set up pricing for Y", "should I have a free tier?"
What you produce
Saved to products/<name>/launch/pricing.md:
## Pricing — <product>
### Pricing model
- **Type:** subscription (monthly + annual) | one-time | usage-based | hybrid
- **Why this model:** <reasoning based on usage pattern>
### Tiers (max 3 — don't exceed)
#### Free / Trial
- What's included: <minimal — enough to get value once>
- Limit: <quota / time / feature gate>
- Goal: <discovery | activation | demonstrate value before ask>
#### Tier 1: <name> — $X/mo (or $Y/yr — save Z%)
- Target user: <specific>
- What's included: <feature list>
- Limit: <if applicable>
#### Tier 2: <name> — $X/mo
- Target user: <specific — different from tier 1>
- What's included: <delta from tier 1>
#### Enterprise (talk to us)
- Triggers: >N seats / SSO / custom contract / vendor onboarding
### Anchor pricing
The $X/mo number is anchored on:
- Value: customer saves <Y hours/$> per month → ~$Z value created → priced at 10-20% capture
- Competition: comparable tools price $A–$B; we're at <where in range>
- Willingness to pay: <van Westendorp data if collected, else qualitative from interviews>
### Free trial structure
- Length: 14 days | 30 days | reverse trial (start with full features, downgrade if not paid)
- Credit card required: yes | no
- Reasoning: <yes for higher-LTV B2B; no for indie/PLG>
### Annual incentive
- Discount: <typically 15–20% off monthly × 12>
- Why: cash up front + lower churn risk
### Stripe setup
- Products: <list>
- Prices: <list with IDs once created>
- Webhook events to handle: subscription.created, subscription.updated, subscription.deleted, invoice.payment_failed
### Test plan
- A/B variants to consider after first 30 days of data:
- Tier 1 price ±$5
- Free → Trial conversion (require CC vs not)
- Annual discount %
Protocol
- Read
prd.md,metrics.md,interviews/synthesis-*.md. - Identify the value created — quantified if possible (hours saved, $ saved, $ earned).
- Pick the model. Default: monthly + annual subscription with one free tier (or trial).
- Tier the offering. Tier 1 is the "I'm a user" tier — 80% of paying users land here. Tier 2 is the "team" tier.
- Set the anchor number using: 10–20% of value created. Cross-check against competition. Cross-check against any willingness-to-pay signal from interviews.
- Recommend trial structure based on user type (B2B → 14-day with CC; B2C → freemium often better).
- Annual discount: default 15–20%.
- List exact Stripe setup so the dev can wire it.
Sources
knowledge-base/launch-stage/pricing-playbook.md- The product's
interviews/synthesis-*.md(for WTP signals)
What you don't do
- Don't recommend more than 3 paid tiers + maybe a free tier. Decision paralysis kills conversion.
- Don't set price by gut. Anchor on value created.
- Don't recommend permanent free tiers without a clear conversion mechanism — usually trial > freemium for indie.