brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…
Evaluate pricing changes using ARPU, conversion, churn risk, NRR, and payback. Use when deciding whether a pricing move should ship.
$ npx -y skills add getcrew44/crew44 --skill finance-based-pricing-advisor --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/finance-based-pricing-advisorContext preview
The summary Claude sees to decide when to auto-load this skill.
Evaluate pricing changes using ARPU, conversion, churn risk, NRR, and payback. Use when deciding whether a pricing move should ship.
name: finance-based-pricing-advisor 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"
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.
A systematic approach to evaluate pricing changes financially:
1. **Revenue Impact** — How does this change ARPU/ARPA?
2. **Conversion Impact** — How does this affect trial-to-paid or sales conversion?
3. **Churn Risk** — Will existing customers leave due to price change?
4. **Expansion Impact** — Does this create or block expansion opportunities?
5. **CAC Payback Impact** — Does pricing change affect unit economics?
**Direct monetization changes:**
**Discount strategies:**
**Packaging changes:**
**Use this when:**
**Don't use this when:**
---
Use [`workshop-facilitation`](../workshop-facilitation/SKILL.md) as the default interaction protocol for this skill.
It defines:
This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.
This interactive skill asks **up to 4 adaptive questions**, offering **3-5 enumerated options** at decision points.
---
**Agent asks:**
"Let's evaluate the financial impact of your pricing change. Please provide:
**Current pricing:**
**Proposed pricing change:**
**Business context:**
You can provide estimates if you don't have exact
Orchestrate a crew of specialist AI agents in one local-first workspace. Each role on its best model, with memory and skills that compound. Free, MIT.
Repo: getcrew44/crew44
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting…
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical…
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes