Add a new expert to the Remotion experts page
日本語の概要は準備中です。原文の説明を表示しています。
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 questions like 'should I charge for this?' or 'is freemium right for us?' or 'my conversion rate is low, is it the price?' are pricing strategy questions. Covers value-based pricing, tier structure, price psychology, and competitor benchmarking.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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 |
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Add a new expert to the Remotion experts page
日本語の概要は準備中です。原文の説明を表示しています。
Add a new sound effect to @remotion/sfx
日本語の概要は準備中です。原文の説明を表示しています。
Use when setting up a secure email inbox for any AI agent — configuring inbound email via Resend, webhooks, tunneling for local development, and implementing security measures to prevent prompt injection attacks. Also use when someone mentions 'agent email', 'bot inbox', 'receive emails for agent', 'agent webhook', 'email security for AI', 'prompt injection via email', 'inbound email for bot', or wants their AI agent to receive and respond to emails securely.
日本語の概要は準備中です。原文の説明を表示しています。
Builds, measures, and improves an Answer Engine Optimization program across ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews, and Copilot. Use for AEO, GEO, LLMO, AI search visibility, AI citations, brand mentions, answer-engine monitoring, llms.txt, AI crawler audits, or questions like 'what does AI say about us?' and 'why are competitors cited instead of us?'. Produces a durable evidence report and prioritized gameplan, not a one-shot content checklist.
日本語の概要は準備中です。原文の説明を表示しています。
Generate Apple App Store screenshot pages as a Next.js app with html-to-image export at required resolutions. Screenshots are advertisements, not documentation — every screenshot sells one idea. Use when building App Store screenshots, generating exportable marketing screenshots for iOS apps, or creating programmatic screenshot generators. Triggers on 'app store screenshots', 'App Store', 'screenshot generator', 'iOS screenshots', 'marketing screenshots', 'phone mockup', 'ASO screenshots', 'app store assets', 'app listing', 'app store page', or 'app preview images'. Also use when someone is about to submit an app and needs store assets, or when they say 'make my app store page look good'. Includes iPhone and iPad mockup components with pre-measured dimensions.
日本語の概要は準備中です。原文の説明を表示しています。
Build detailed buyer personas and audience profiles from research. Use this skill whenever the user mentions audience, buyer persona, ideal customer, target market, ICP, watering holes, 'who am I selling to', customer research, or audience profile. Also use when content feels unfocused or generic (that's an audience problem), when conversion is low because messaging doesn't resonate, when starting any new project (audience should be first), or when any downstream skill needs audience.md but it doesn't exist yet. Even if the user doesn't explicitly ask for audience research, trigger this if they're writing copy or building a landing page without a clear audience defined. Three approaches: Quick Profile, Persona Build, Community Mining.
日本語の概要は準備中です。原文の説明を表示しています。