Pricing and Packaging Strategy Prompt for SaaS Tiers

The fastest way to set SaaS pricing badly is to open a competitor's pricing page and copy the shape of it. Three tiers, a per-seat number, an enterprise "contact us." It looks like a decision. It's a costume. A pricing and packaging strategy prompt replaces the costume with a scored sequence: value metric first, then fences, then a price point you can defend when a board member asks why.

The guides that rank for this query are excellent essays and nothing more. Stripe and Paddle both lay out the theory well. Neither hands you a way to run the decision on your own product. You finish reading, agree with all of it, and still stare at a blank pricing page.

That's the whole gap. Theory is everywhere. The applied step — score my value metric, fence my tiers — is what no ranking page does.

Why the pricing guides leave you stuck

Stripe's pricing and packaging strategy guide is genuinely good. It names the four properties of a strong value metric — flexible with value, understandable, hard to game, aligned with budgets — and recommends two to four tiers with feature gates and usage limits. All correct. All prose. There's no scoring rubric, no decision tree, no worksheet you can run against your own product.

Paddle's SaaS pricing models breakdown lists the six models cleanly (flat, per-seat, tiered, usage, freemium, hybrid) and advises "start simple, launch with one or two tiers." Also correct. Also prose only, with no prompt and no structured way to pick between the six for your specific case.

So the reader walks away with the vocabulary of a good pricing decision and none of the mechanics. The gap between "I understand value metrics" and "I've chosen mine and can defend it" is exactly the gap a prompt fills.

What you can do with this prompt

• Score candidate value metrics on alignment, understandability, and gaming resistance
• Architect two to four tiers with a stated reason for each feature fence
• Reason a defensible price point from your segments and usage data
• Design fences that resist the "just buy the cheap tier and share it" leak
• Plan a repricing migration that doesn't churn your existing base
• Pressure-test the packaging against how customers actually budget

Anatomy of the prompt

The sequence is the point. Value metric first — everything downstream depends on it — then tiers, then price.

Variables
  {{product_description}}  — what it does, core jobs it serves
  {{customer_segments}}    — who buys, how they differ, how they budget
  {{current_pricing}}      — today's tiers/price, if any
  {{usage_data}}           — how consumption scales per customer

Prompt
  Role: pricing strategist choosing a value metric before tiers.
  Task: score 3 candidate value metrics, pick one, fence tiers
        around it, then reason a price point per segment.
  Rules: state the trade-off for every choice; no "it depends".

Output contract
  1. Value-metric scorecard (metric | 4 property scores | verdict)
  2. Tier map (tier | who it's for | fence | included | excluded)
  3. Price-point reasoning per segment, with the anchor logic

Keep the value-metric scorecard above the tier map in the output, because the tiers only make sense once the metric is chosen. If you let the model design tiers first, it anchors on a competitor's layout and reverse-justifies the metric. Order the contract to force metric-first thinking. GPT-4o will happily skip the scorecard and jump to tiers unless the contract numbers the steps explicitly.

1. Gather inputs

Drop a plain product description into {{product_description}} and your real segments into {{customer_segments}}. If you have usage telemetry, {{usage_data}} is where the value metric gets its teeth — a metric that doesn't track consumption is a guess.

2. Read the scorecard before the tiers

The value-metric scorecard is the load-bearing output. If your assumed metric (usually per-seat) scores low on gaming resistance, that's the prompt catching a leak before you ship it. Per-seat is the default precisely because it's easy, not because it's aligned.

3. Fence, then price

A tier without a fence is a suggestion. The tier map's "excluded" column is where the real design lives — what a customer can't do on the cheaper plan is what makes them upgrade. Price comes last, anchored to the fence.

Prompt-craft patterns that make pricing defensible

Score the metric, don't assume it. The single highest-leverage move is refusing to let the model default to per-seat.

For each candidate metric, score 1-5:
  Alignment | Understandable | Gaming-resistant | Budget-fit
Pick the highest composite, and name the runner-up's trade-off.

Design the fence as an exclusion, not an inclusion. Models list what's in each tier by default. Flip it: ask what's excluded from the lower tier and why that exclusion drives an upgrade. A fence you can't explain is a fence a customer will resent.

Variables you'll set

The two required inputs are things a founder can write from memory. The optional ones sharpen the value metric — bring {{usage_data}} if you have it, because a metric chosen without consumption data is a hypothesis, not a decision.

Where one prompt stops and a system begins

A single prompt scores the metric and sketches tiers well. It's thinner on the follow-through: designing fences that hold, reasoning price points per segment, and planning the migration so a reprice doesn't churn your base. Those are distinct jobs that reuse the same product and segment inputs, which is where a structured pack earns its price over a lone prompt.

For the reprice itself, the migration is the risky part — the same discipline that ranks your workflows also ranks your repricing steps, and the product roadmap prioritization prompt shows that scored-sequence habit applied to a backlog. If you're validating whether your current price is even in the right band first, the saas pricing prompt covers that narrower check.

Copying a competitor's pricing page copies their assumptions about their customers, not yours. Score your own value metric, fence your own tiers, and the price point stops being a guess you defend nervously and becomes a decision you can explain in one sentence. Start with the value metric, or browse the full catalog of prompt packs for the strategy work that surrounds a reprice.