What is pricing-strategy?
When the user wants help with pricing decisions, packaging, monetization strategy, or subscription models. Make sure to use this whenever someone is making ANY pricing decision — even ques
MoizIbnYousaf/marketing-cli
When the user wants help with pricing decisions, packaging, monetization strategy, or subscription models. Also use when the user mentions 'pricing', 'price', 'monetization', 'freemium', 'Van Westendorp', 'how much should I charge', 'pricing tiers', 'good-better-best', 'SaaS pricing', 'subscription model', 'free vs paid', 'packaging', 'pricing page', 'annual vs monthly', or is deciding between free and paid models. Make sure to use this whenever someone is making ANY pricing decision — even ques
npx skills add https://github.com/MoizIbnYousaf/marketing-cli --skill "skills/pricing-strategy"Quick start
Install it or open the source, trigger it with a clear task, then follow the source workflow.
npx skills add https://github.com/MoizIbnYousaf/marketing-cli --skill "skills/pricing-strategy"Use pricing-strategy to help me with: [describe your task]. Before you begin, tell me what input you need, the steps you will follow, and the expected output.
No structured workflow was detected; follow the original SKILL.md below.
Continue to the workflowDirect answers
When the user wants help with pricing decisions, packaging, monetization strategy, or subscription models. Make sure to use this whenever someone is making ANY pricing decision — even ques
It is relevant to workflows involving Marketing, Design, Operations, Research.
SkillSignal detected this source-specific command: npx skills add https://github.com/MoizIbnYousaf/marketing-cli --skill "skills/pricing-strategy". Inspect the repository and command before running it.
The upstream source does not declare a dedicated Agent platform.
No obvious permission action was detected by the static rules. This is not proof that the Skill is safe.
This page combines upstream documentation with deterministic repository, quality, and static-risk signals. It is not described as a manual test or security review.
SkillSignal brief
When the user wants help with pricing decisions, packaging, monetization strategy, or subscription models. Make sure to use this whenever someone is making ANY pricing decision — even ques
Useful in these contexts
Core capabilities
Distilled from the source
About 7 min · 13 sections
Also use when the user mentions 'pricing', 'price', 'monetization', 'freemium', 'Van Westendorp', 'how much should I charge', 'pricing tiers', 'good-better-best', 'SaaS pricing', 'subscription model', 'free vs paid', 'p…
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
Compare before choosing
These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.
Optimizes multi-step conversion flows including signup, onboarding, upgrade, and checkout. Maps each step, identifies friction and drop-off risks, then recommends specific copy/UX changes with A/B test plans. Use when someone says 'signup flow', 'onboarding optimization', 'checkout conversion', 'paywall optimization', 'activation rate', 'funnel analysis', 'why are users dropping off', 'registration flow', 'trial conversion', 'free to paid', 'upgrade flow', 'user journey', or wants to improve any
Designs cancel flow UX, dunning email sequences, win-back campaigns, and retention triggers. Covers the full churn prevention lifecycle from early warning signals to 90-day win-back. Use when someone mentions 'churn', 'retention', 'cancel flow', 'dunning', 'win-back', 'users leaving', 'reducing churn', 'keep users', 'customers canceling', 'payment failed', 'failed payments', 'losing subscribers', 'customer retention', or wants to prevent customers from leaving. Even if they just say 'people keep
Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.
Use when the user wants to generate an image or video via Higgsfield AI. Covers 30+ models: Soul V2, Seedance 2.0, Kling 3.0, Veo 3.1, GPT Image 2, Nano Banana 2. Also covers Marketing Studio — branded ad video/image with avatars and products. Use whenever: "generate an image", "make a video", "animate this photo", "image-to-video", "img2vid", "edit this image with AI", "produce a clip", "create an ad", "make a UGC video", "marketing video", "brand video", "TV spot", "import product from URL", "
Analyze Neuropixels extracellular recordings end-to-end with SpikeInterface. Covers loading SpikeGLX/Open Ephys/NWB data, preprocessing, drift/motion correction, Kilosort4 (and CPU) spike sorting, quality metrics, and unit curation (threshold-based, model-based UnitRefine, and AI-assisted visual review). Use when working with Neuropixels 1.0/2.0 recordings, spike sorting, or extracellular electrophysiology analysis.
You are an expert in pricing and monetization strategy. Your goal is to help design pricing that captures value, drives growth, and aligns with customer willingness to pay.
brand/ directory exists in the project rootbrand/positioning.md, brand/audience.md, and brand/competitors.md for contextFollow these phases in order. Do not skip phases.
Ask these questions (skip any already answered by brand/ files):
Business Context:
Value and Competition:
Current Performance (if applicable):
Goals:
If web search is available (Exa MCP or firecrawl), research competitor pricing:
If web search is unavailable: Ask the user to provide competitor pricing tiers directly. Note limitation: "Market benchmarking is based on provided data, not live research. Validate competitor pricing before finalizing strategy."
Using the fundamentals below, determine the right value metric. Ask: "As a customer uses more of [metric], do they get more value?" If yes, it's a good metric.
Using references/tier-structure.md, design tiers:
Apply value-based pricing:
Write marketing/pricing/strategy.md using this template:
# Pricing Strategy: [Product Name]
## Overview
- **Product type:** [SaaS / Marketplace / etc.]
- **Target market:** [SMB / Enterprise / Consumer]
- **Go-to-market:** [Self-serve / Sales-led / Hybrid]
- **Optimizing for:** [Growth / Revenue / Profitability]
## Value Metric
- **Metric:** [What you charge for]
- **Why:** [How it aligns with value delivered]
- **Scales with:** [What grows as customer gets more value]
## Competitive Landscape
| Competitor | Lowest Tier | Mid Tier | Highest Tier | Value Metric |
|------------|-------------|----------|--------------|--------------|
| [Name] | [Price] | [Price] | [Price] | [Metric] |
## Recommended Tier Structure
### [Tier 1 Name] — $[Price]/mo
- **For:** [Target persona]
- **Includes:** [Key features and limits]
- **Purpose:** [Why this tier exists]
### [Tier 2 Name] — $[Price]/mo (Recommended)
- **For:** [Target persona]
- **Includes:** [Key features and limits]
- **Purpose:** [Why this tier exists]
### [Tier 3 Name] — $[Price]/mo
- **For:** [Target persona]
- **Includes:** [Key features and limits]
- **Purpose:** [Why this tier exists]
## Pricing Psychology Applied
- **Anchoring:** [How highest tier anchors perception]
- **Recommended badge:** [Which tier and why]
- **Annual discount:** [% and rationale]
## Price Increase Strategy
[When and how to raise prices as product matures]
## Risks and Mitigations
| Risk | Mitigation |
|------|------------|
| [e.g., Too cheap signals low quality] | [e.g., Round pricing, premium positioning] |
Tell the user: "Pricing strategy written to marketing/pricing/strategy.md. Here's the summary: [2-3 sentences with specific price recommendations]. Suggested next steps: [specific skills]."
Recommend related skills:
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 contact/record | CRM, email tools | Email platforms |
| 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:
| Anti-pattern | Why it fails | Instead |
|---|---|---|
| Copying competitor pricing without analysis | Competitors may be mispriced themselves, or their positioning may not match yours — copying inherits their mistakes | Research competitors to understand their positioning, then price based on YOUR value |
| Recommending prices without understanding the value metric | Without knowing what customers pay for, tier boundaries are arbitrary and upgrades feel forced | Always identify the value metric first — price follows value |
| Skipping competitor research and guessing market rates | Users make real business decisions on this output — unresearched numbers can cost thousands in lost revenue | Use Exa MCP or ask user for competitor data before setting price points |
| Producing generic "charge more" advice | Vague advice is indistinguishable from a blog post — the user came here for specific, actionable numbers | Commit to specific numbers with justification tied to research |
| Recommending 5+ tiers for a new product | Paradox of choice — too many tiers causes decision paralysis and increases support complexity | Start with 3 tiers (Good-Better-Best). Add complexity only when data supports it |
| Ignoring brand positioning when setting price points | A premium brand using charm pricing ($29) undercuts its own authority; a budget brand using round pricing ($100) alienates its audience | Premium positioning = round pricing. Budget positioning = charm pricing. Always align |