Pricing Tiers and Revenue Impact Model
Design value-based tiers and model revenue, contribution, and break-even customer loss before changing prices.
Before & after
Same prompt, same agent — the only difference is the skill.
Pricing is an important decision for your business. You'll want to think about what your customers are willing to pay and what competitors are charging. Consider different pricing models like per-user, usage-based, or flat-rate. You might create tiers for different segments. Revenue impacts are important to model. Many companies iterate on pricing over time. There are lots of approaches to consider depending on your market and customer base. What are your thoughts on the different options?
3-TIER PRICING MODEL TIER 1: Starter ($29/mo, 1000 API calls/mo) Target: Solo developers Margin: 82% gross Elasticity: -2.1 (small sensitivity) TIER 2: Professional ($149/mo, 50k API calls/mo) Target: Small teams Margin: 76% gross Elasticity: -1.4 (moderate) Conversion lift vs Starter: 23% TIER 3: Enterprise (custom, unlimited) Target: Fortune 500 adjacent Margin: 65% gross Elasticity: -0.6 (inelastic) Average ACV: 34k REVENUE IMPACT SCENARIOS: +10% price increase: +8.2% revenue (loses 2% of Starter; Professional holds) -15% price increase: -12.1% revenue (gains 4% conversion; insufficient volume lift) Add upsell feature ($19/mo): +3.4% ARPU with 12% attach rate BREAK-EVEN ASSUMPTIONS: Support cost per user: 2.80/mo Infra cost per user: 0.41/mo Monthly churn: 5% Note: illustrative numbers only, not financial advice.
About this skill
“Will this price increase make us more money, or just cost us customers?” Build a pricing decision around explicit tier economics, customer response scenarios, and the exact customer loss you can afford. Separate what your data supports from what still needs testing.
What it does
- Selects a value metric that customers understand and that supports sustainable delivery costs.
- Designs tiers with distinct buyers, meaningful upgrade triggers, and measurable economic boundaries.
- Models price changes by affected cohort, including discounts, downgrades, conversion changes, and migration timing.
- Calculates separate break-even thresholds for revenue and contribution.
- Tests elasticity assumptions with downside, working-case, and upside scenarios without presenting guesses as forecasts.
- Builds a price-test plan with a primary outcome, guardrails, and decision rules.
What you get
A recommended pricing structure or price-change decision, an auditable financial model, and a bounded validation plan. Quick questions get the relevant calculation; larger requests get tier economics and cohort scenarios.
Best for
Founders, finance leads, and product teams deciding how to package value, change prices, or defend a pricing recommendation with numbers.
SKILL.md preview
---
name: pricing-tiers-and-revenue-impact-model
description: Designs value-based pricing tiers and models price changes using cohort economics, explicit response scenarios, and separate revenue and contribution break-even thresholds. Use when the user says "design our pricing tiers", "should we raise prices?", "model a 15% price increase", "how many customers can we afford to lose?", "our tiers aren't making enough money", "customers keep downgrading", "test our price sensitivity", or "justify value-based pricing".
---
# Pricing Tiers and Revenue Impact Model
… (sign up to view the full skill)More finance skills
View all Finance skills →Portfolio Rebalance Advisor
Drop in your current holdings and target allocation — get the exact buy/sell list, tax-loss opportunities, and drift alert.
Personal Finance Q&A
Ask any personal-finance question and get a plain-English answer tailored to your bracket, timeline, and risk appetite.
Earnings Report Analyzer
Paste a 10-K, 10-Q, or earnings call transcript — get the numbers that matter, the narrative changes, and what the CFO tried to bury.
Investment Committee Decision Memo
Turn deal materials into an investment memo with traced evidence, reconciled financials, downside cases, and decision gates.