# Decide which pricing plan a new feature belongs in

A packaging recommendation that weighs adoption, upgrade pull, and fairness to existing customers.

- Topic: Business Strategy & Startups
- Framework: RTF
- Level: Standard
- Tags: Finance, Analyze, Plan, Fill-in Template
- Source: https://www.thinkwithprompt.com/prompts/decide-which-pricing-plan-a-new-feature-belongs-in

## Prompt

```text
Help me decide how to package a new feature across our pricing plans.

**Our plans today:** [PLAN NAMES, PRICES, WHAT EACH INCLUDES, WHO BUYS EACH]
**New feature:** [WHAT IT DOES]
**Who values it most:** [SEGMENTS, USE CASES]
**Cost to serve:** [e.g. usage-based infrastructure or third-party costs]
**Business goal:** [drive upgrades / reduce churn / win a segment / increase adoption]
**Data I have:** [PLAN MIX, UPGRADE RATES, BETA USAGE BY PLAN]

Evaluate these options: include in all plans, include in a higher plan only, free plan with limits and full version in higher plans, paid add-on, or usage-based pricing.

For each option assess:
- Adoption and learning: how many users will try it.
- Upgrade pull: does it give a clear reason to move up, and for whom?
- Fit with how each plan's buyers think about value.
- Existing customers: grandfathering, perceived take-aways, support load.
- Margin impact if cost to serve is meaningful.
- Simplicity: can sales and the pricing page explain it in one line?

Return a comparison table, a recommendation, the limits or thresholds if you suggest a limited version, and a plan to test or review the decision after 90 days. Use only my data; mark gaps [ADD DATA]. Have finance review any change to revenue assumptions.
```

## What to fill in

- PLAN NAMES, PRICES, WHAT EACH INCLUDES, WHO BUYS EACH
- WHAT IT DOES
- SEGMENTS, USE CASES
- e.g. usage-based infrastructure or third-party costs
- PLAN MIX, UPGRADE RATES, BETA USAGE BY PLAN
- ADD DATA

Free to copy and use. From ThinkWithPrompt (https://www.thinkwithprompt.com/), a library of 2,663 curated AI prompts.