SkillAgentSearch skills...

finance-based-pricing-advisor

Evaluate pricing changes using ARPU, conversion, churn risk, NRR, and payback

Install / Use

npx skills add deanpeters/Product-Manager-Skills --skill finance-based-pricing-advisor

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Supported Platforms

Universal

Tags

Our assessment of finance-based-pricing-advisor

finance-based-pricing-advisor scores 86/100 on our quality scale, 210th of 319 Customer Support skills we index.

Its SKILL.md is 23 KB long, well organised into 45 sections and no code examples: a thorough specification that gives an agent plenty to work with.

With 7,063 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
13/20
Description
12/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so finance-based-pricing-advisor is actively maintained.
  • Our last check on 2026-11-03 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

finance-based-pricing-advisor compared with similar skills

All 4 of these similar skills score higher than finance-based-pricing-advisor; compare them before choosing.

SkillScoreStarsUpdatedFormat
finance-based-pricing-advisor (this skill)by deanpeters867.1k3mo agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install finance-based-pricing-advisor?
Run npx skills add deanpeters/Product-Manager-Skills --skill finance-based-pricing-advisor. The install tabs above show the steps for each supported agent.
Which AI agents does finance-based-pricing-advisor work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is finance-based-pricing-advisor safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is finance-based-pricing-advisor still maintained?
The repository was last updated about 3 months ago, so finance-based-pricing-advisor is actively maintained.

name: finance-based-pricing-advisor argument-hint: "[pricing change to evaluate]" description: Evaluate pricing changes using ARPU, conversion, churn risk, NRR, and payback. Use when deciding whether a pricing move should ship. intent: >- 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. type: interactive best_for:

  • "Evaluating price increases, discounts, or new packaging"
  • "Estimating churn and conversion risk before a pricing change"
  • "Making a go/no-go call on monetization changes" scenarios:
  • "Should we raise prices 15% for new customers next quarter?"
  • "Evaluate a new premium tier for our SaaS product"
  • "Help me assess whether an annual discount will improve revenue" theme: finance-metrics estimated_time: "20-30 min"

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.

Input

Works best with: The pricing change on the table — increase, new tier, add-on, or discount — and current pricing. Also useful: Current ARPU/ARPA, conversion and churn baselines, NRR, and who's pushing for the change.

Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.

Arriving empty-handed? That works too. The advisor opens by asking what change is proposed and what today's pricing looks like.

Example invocation: Evaluate raising our Pro plan from $49 to $59/seat; ARPU $52, monthly logo churn 1.8%, NRR 108%.

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 raise prices 20%?")
  • You need to quantify revenue, churn, and conversion trade-offs
  • You're deciding between pricing change options (test A vs. B)
  • You need to present pricing change impact to leadership or board

Don't use this when:

  • You're designing pricing strategy from scratch (use value-based pricing frameworks)
  • You haven't validated willingness-to-pay (do customer research first)
  • You don't have baseline metrics (ARPU, churn, conversion rates)
  • Change is too small to matter (<5% price change, <10% of customers affected)

Facilitation Source of Truth

Use workshop-facilitation as the default interaction protocol for this skill.

It defines:

  • session heads-up + entry mode (Guided, Context dump, Best guess)
  • one-question turns with plain-language prompts
  • progress labels (for example, Context Qx/8 and Scoring Qx/5)
  • interruption handling and pause/resume behavior
  • numbered recommendations at decision points
  • quick-select numbered response options for regular questions (include Other (specify) when useful)

This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.

Application

This interactive skill asks up to 4 adaptive questions, offering 3-5 enumerated options at decision points.


Step 0: Gather Context

Agent asks:

"Let's evaluate the financial impact of your pricing change. Please provide:

Current pricing:

  • Current ARPU or ARPA
  • Current pricing tiers (if applicable)
  • Current monthly churn rate
  • Current trial-to-paid conversion rate (if relevant)

Proposed pricing change:

  • What change are you considering? (price increase, new tier, add-on, etc.)
  • New pricing (if known)
  • Affected customer segment (all, new only, specific tier)

Business context:

  • Total customers (or MRR/ARR)
  • CAC (to assess payback impact)
  • NRR (to assess expansion context)

You can provide estimates if you don't have exact numbers."


Step 1: Identify Pricing Change Type

Agent asks:

"What type of pricing change are you considering?

  1. Price increase — Raise prices for new customers, existing customers, or both
  2. New premium tier — Add higher-priced tier with additional features
  3. Paid add-on — Monetize a new or existing feature separately
  4. Usage-based pricing — Charge for consumption (seats, API calls, storage, etc.)
  5. Discount strategy — Annual prepay discount, volume pricing, or promotional pricing
  6. Packaging change — Rebundle features, change pricing metric, or tier restructure

Choose a number, or describe your specific pricing change."

Based on selection, agent adapts questions:


If Option 1 (Price Increase):

Agent asks:

"Price increase details:

  • Current price: $___
  • New price: $___
  • Increase: ___%

Who is affected?

  1. New customers only (grandfather existing)
  2. All customers (existing + new)
  3. Specific segment (e.g., SMB only, new plan only)

When would this take effect?

  • Immediately
  • Next billing cycle
  • Gradual rollout (test first)"

If Option 2 (New Premium Tier):

Agent asks:

"Premium tier details:

  • Current top tier price: $___
  • New premium tier price: $___
  • Key features in premium tier: [list]

Expected adoption:

  • What % of current customers might upgrade? ___%
  • What % of new customers might choose premium? ___%

Cannibalization risk:

  • Will premium tier cannibalize current top tier?"

If Option 3 (Paid Add-On):

Agent asks:

"Add-on details:

  • Add-on name: ___
  • Price: $___ /month or /user
  • Currently free or new feature?

Expected adoption:

  • What % of customers would pay for this? ___%
  • Is this feature currently used (if free)?
  • Will making it paid hurt retention?"

If Option 4 (Usage-Based Pricing):

Agent asks:

"Usage pricing details:

  • Usage metric: (seats, API calls, storage, transactions, etc.)
  • Pricing: $___ per [unit]
  • Free tier or minimum? (e.g., first 1,000 API calls free)

Expected impact:

  • Average customer usage: ___ units/month
  • Expected ARPU change: $current → $new

Expansion potential:

  • As customers grow usage, will ARPU increase?"

If Option 5 (Discount Strategy):

Agent asks:

"Discount details:

  • Discount type: (annual prepay, volume, promotional)
  • Discount amount: ___% off
  • Duration: (ongoing, limited time)

Trade-off:

  • Lower price vs. improved cash flow (annual prepay)
  • Lower price vs. larger deal size (volume)
  • Lower price vs. urgency (promotional)"

If Option 6 (Packaging Change):

Agent asks:

"Packaging change details:

  • What are you changing? (bundling, unbundling, pricing metric)
  • Current packaging: [describe]
  • New packaging: [describe]

Expected impact:

  • ARPU change: $current → $new
  • Conversion change: ___% → ___%
  • Churn risk: (low, medium, high)"

Step 2: Assess Expected Impact

Agent asks:

"Now let's quantify the impact. Based on your pricing change, estimate:

Revenue impact:

  • Current ARPU: $___
  • Expected new ARPU: $___
  • ARPU lift: ___%

Conversion impact:

  • Current conversion rate: ___%
  • Expected new conversion rate: ___%
  • Conversion change: [increase / decrease / no change]

Churn risk:

  • Current monthly churn: ___%
  • Expected churn after change: ___%
  • Churn risk: [low / medium / high]

Expansion impact:

  • Does this create expansion opportunities? (new tier to upgrade to, usage growth)
  • Expected NRR change: ___% → ___%

You can provide estimates. We'll model scenarios (conservative, base, optimistic)."


Step 3: Evaluate Current State

Agent asks:

"To assess whether this pricing change makes sense, I need your current baseline:

Current metrics:

  • MRR or ARR: $___
  • Number of customers: ___
  • ARPU/ARPA: $___
  • Monthly churn rate: ___%
  • NRR: ___%
  • CAC: $___
  • LTV: $___

Growth context:

  • Current growth rate: ___% MoM or YoY
  • Target growth rate: ___%

Competitive context:

  • Are you priced below, at, or above market?
  • Competitive pressure: (low, medium, high)"

Step 4: Deliver Recommendations

Agent synthesizes:

  • Revenue impact (ARPU lift × customer base)
  • Conversion impact (new customers affected)
  • Churn impact (existing customers affected)
  • Net revenue impact
  • CAC payback impact
  • Risk assessment

Agent offers 3-4 recommendations:


Recommendation Pattern 1: Implement Broadly

When:

  • Net revenue impact clearly positive (>10% ARPU lift, <5% churn risk)
  • Minimal conversion impact
  • Strong value justification

Recommendation:

"Implement this pricing change — Strong financial case

Revenue Impact:

  • Current MRR: $___
  • ARPU lift: ___% ($current → $new)
  • Expected MRR increase: +$/month (+%)

Churn Risk: Low

  • Expected churn increase: ___% → % (+% points)
  • Churn-driven MRR loss: -$___/month
  • Net MRR impact: +$___/month ✅

Conversion Impact:

  • Current conversion: ___%
  • Expected conversion: % (% change)
  • Impact on new customer acquisition: [minimal / manageable]

CAC Payback Impact:

  • Current paybac

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars7.1k
CategoryCustomer
Updated2mo ago
Forks846

Languages

Shell

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium