Finance Based Pricing Advisor
Run ARPU, churn, conversion, NRR, and payback math on a proposed price change before you ship new tiers, increases, or discounts.
Overview
Finance-Based Pricing Advisor is an agent skill most often used in Validate (also Grow) that evaluates proposed pricing changes with ARPU, churn, NRR, and payback math for go/no-go decisions.
Install
npx skills add https://github.com/deanpeters/product-manager-skills --skill finance-based-pricing-advisorWhat is this skill?
- Interactive financial evaluation for price increases, new tiers, add-ons, and discounts—not a full pricing-strategy work
- Models ARPU/ARPA, conversion impact, churn risk, NRR effects, and CAC payback implications for go/no-go calls
- Scenario-ready prompts such as 15% increases, premium tiers, and annual discount tradeoffs
- Clear boundary: evaluates changes you already propose; not willingness-to-pay research or competitive positioning framew
Adoption & trust: 1.2k installs on skills.sh; 5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are considering a price increase, new tier, or discount but do not know whether revenue upside outweighs conversion and churn risk.
Who is it for?
Founders deciding whether to raise prices, add a premium tier, or offer annual discounts when you can supply or estimate core SaaS metrics.
Skip if: Greenfield pricing strategy, value-based pricing frameworks, willingness-to-pay research, or competitive pricing intelligence from scratch.
When should I use this skill?
Use when deciding whether a pricing move should ship—price increases, new tiers, add-ons, or discounts—and you need ARPU, conversion, churn, NRR, and payback evaluation.
What do I get? / Deliverables
You leave with a data-driven go/no-go recommendation on the pricing move, including financial impact framing and explicit risk on churn, NRR, and payback.
- Go/no-go recommendation with financial impact narrative
- Risk assessment on conversion, churn, and NRR
- Payback and revenue implications for the proposed packaging or price point
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Pricing go/no-go decisions sit in Validate when you test whether a monetization move is worth building and rolling out. The skill is explicitly financial impact evaluation for pricing moves—not full packaging discovery—so the canonical shelf is pricing.
Where it fits
Stress-test a 15% price increase on new logos with churn and conversion scenarios before updating checkout.
Decide whether a premium tier belongs in the next release scope based on ARPA uplift vs support cost.
Assess whether an annual prepay discount improves NRR without destroying expansion revenue.
How it compares
Financial impact checker for a proposed change—not a replacement for positioning, packaging discovery, or market research skills.
Common Questions / FAQ
Who is finance-based-pricing-advisor for?
Solo builders and small SaaS teams who need spreadsheet-grade pricing impact analysis before shipping monetization changes.
When should I use finance-based-pricing-advisor?
In Validate when scoping price tests; in Grow when revisiting tiers, discounts, or NRR after you have baseline ARPU and churn signals.
Is finance-based-pricing-advisor safe to install?
It is procedural PM guidance without automatic repo access; review the Security Audits panel on this Prism page before adding any third-party skill pack.
SKILL.md
READMESKILL.md - Finance Based Pricing Advisor
## Purpose Evaluate the **financial impact** of pricing changes (price increases, new tiers, add-ons, discounts) using ARPU/ARPA analysis, conversion impact, churn risk, NRR effects, and CAC payback implications. Use this to make data-driven go/no-go decisions on proposed pricing changes with supporting math and risk assessment. **What this is:** Financial impact evaluation for pricing decisions you're already considering. **What this is NOT:** Comprehensive pricing strategy design, value-based pricing frameworks, willingness-to-pay research, competitive positioning, psychological pricing, packaging architecture, or monetization model selection. For those topics, see the future `pricing-strategy-suite` skills. This skill assumes you have a specific pricing change in mind and need to evaluate its financial viability. ## Key Concepts ### The Pricing Impact Framework A systematic approach to evaluate pricing changes financially: 1. **Revenue Impact** — How does this change ARPU/ARPA? - Direct revenue lift from price increase - Revenue loss from reduced conversion or increased churn - Net revenue impact 2. **Conversion Impact** — How does this affect trial-to-paid or sales conversion? - Higher prices may reduce conversion rate - Better packaging may improve conversion - Test assumptions 3. **Churn Risk** — Will existing customers leave due to price change? - Grandfathering strategy (protect existing customers) - Churn risk by segment (SMB vs. enterprise) - Churn elasticity (how sensitive are customers to price?) 4. **Expansion Impact** — Does this create or block expansion opportunities? - New premium tier = upsell path - Usage-based pricing = expansion as customers grow - Add-ons = cross-sell opportunities 5. **CAC Payback Impact** — Does pricing change affect unit economics? - Higher ARPU = faster payback - Lower conversion = higher effective CAC - Net effect on LTV:CAC ratio ### Pricing Change Types **Direct monetization changes:** - Price increase (raise prices for all customers or new customers only) - New premium tier (create upsell path) - Paid add-on (monetize previously free feature) - Usage-based pricing (charge for consumption) **Discount strategies:** - Annual prepay discount (improve cash flow) - Volume discounts (larger deals) - Promotional pricing (temporary price reduction) **Packaging changes:** - Feature bundling (combine features into tiers) - Unbundling (separate features into add-ons) - Pricing metric change (seats → usage, or vice versa) ### Anti-Patterns (What This Is NOT) - **Not value-based pricing:** This evaluates a proposed change, not "what should we charge?" - **Not WTP research:** This analyzes impact, not "what will customers pay?" - **Not competitive positioning:** This is financial analysis, not market positioning - **Not packaging architecture:** This evaluates one change, not redesigning all tiers ### When to Use This Framework **Use this when:** - You have a specific pricing change to evaluate (e.g., "Should we ra