---

name: yepai-pm-finance-based-pricing-advisor description: >- Use when the user is evaluating pricing structure, monetization changes, or pricing tradeoffs across seat-based, usage-based, hybrid, or migration paths. Best for product decisions where pricing must be tied to business impact, risk, and unit economics. metadata: {"openclaw":{"emoji":"💵"}} license: MIT-0

YepAI PM Finance Based Pricing Advisor

Use this skill when pricing is a product decision, not just a finance opinion.

Use Cases

• seat vs usage pricing
• pricing migration decisions
• packaging changes
• hybrid monetization design
• expansion revenue questions
• balancing adoption vs monetization

Core Rule

Pricing advice must connect user value, business impact, tradeoffs, and migration risk. Do not present pricing preference as a complete recommendation without comparison.

Pricing Workflow

1. Clarify the pricing frame

Identify:

• target segment
• current model
• proposed alternatives
• business objective
• major constraints

2. Assess the monetization logic

Look for:

• value metric fit
• predictability for the buyer
• expansion potential
• implementation complexity
• sales and billing implications
• unit economics impact

3. Compare at least two paths

Typical paths:

• keep current model
• full migration
• grandfathered rollout
• hybrid seat + usage model

4. Make the tradeoffs explicit

State what is gained and lost in each path:

• simplicity
• revenue expansion
• buyer trust
• implementation cost
• sales friction
• churn risk

5. Recommend a path with caveats

End with:

• recommended direction
• key assumptions
• migration risks
• validation step

Output Format

Prefer this structure:

## Pricing Decision Frame
## Options Considered
## Business Impact
## Tradeoffs / 取舍
## Risks / Assumptions
## Recommended Path
## Recommended Next Step

Quality Rules

• Compare multiple paths explicitly
• Tie the answer to business metrics when possible
• Do not invent pricing data
• If key pricing inputs are missing, ask or label the analysis as provisional
• Keep migration risk visible
• Avoid recommending monetization changes without user and operational consequences