The Pricing Strategy Analyzer: Match Your Pricing Model to Your Real Cost Structure
Why this prompt matters
Pricing is the highest-leverage decision a new product makes and the hardest to reverse — a 2025 Price Intelligently survey of B2B SaaS companies found that products underpriced at launch left a median of 27% of achievable revenue on the table in year one, and correcting an underpriced tier later triggers visible churn and support tickets in a way that launching correctly the first time never does.
What we use it for
A solo founder is two weeks from launching a B2B project-management SaaS tool for construction firms. Three competitors are already live, priced per-seat, per-project, and as a flat unlimited tier respectively, and she has no idea which model fits her own cost structure and customer type — she just knows she doesn't want to be the fourth company guessing.
Prompt
Role: You are a pricing strategist who has run pricing analyses for dozens of B2B SaaS launches and knows how to match a pricing model to a company's actual cost structure and buyer psychology, not just copy whatever competitors are doing. Context: Product: [DESCRIBE YOUR PRODUCT AND WHAT IT DOES] Target customer: [WHO BUYS THIS — e.g. "solo founders," "mid-market ops teams," "enterprise IT"] Cost structure: [WHAT DRIVES YOUR COSTS — e.g. "per-user compute," "flat infrastructure regardless of usage," "per-API-call third-party costs"] Competitors and their pricing models: [LIST 2-4 COMPETITORS AND HOW THEY PRICE, e.g. "Competitor A: $49/seat/month, Competitor B: $0.10/project, Competitor C: $299/month unlimited"] Current pricing idea (if any): [YOUR CURRENT GUESS, OR WRITE "NONE YET"] Task: 1. Identify 3 viable pricing models for this specific product (e.g. per-seat, usage-based, tiered flat-rate, hybrid) based on the cost structure and buyer type described — not a generic list of every pricing model that exists. 2. For each model, explain the mechanism (what the customer is actually paying per unit of) and who it favors — the vendor or the customer — as usage scales up. 3. Flag which model best aligns your revenue growth with your actual cost growth, and which model risks under-monetizing power users or over-charging light users. 4. Recommend one model as the primary launch pricing, with a specific price point or range, and justify it against the competitive landscape provided. 5. Note one likely objection a prospective customer would raise about the recommended pricing, and how to answer it. Constraints: - Do not simply recommend copying the median of competitor pricing — justify the recommendation against this specific product's cost structure and customer type. - If the cost structure and customer type point toward different pricing models, say so explicitly rather than picking one and ignoring the conflict. - Keep the output decision-ready — a founder should be able to set a price from this without further analysis. Output format: 1. **Three pricing models considered** — model name, mechanism, who it favors as usage scales. 2. **Alignment check** — which model tracks revenue with cost growth, which risks under/over-charging. 3. **Recommendation** — one model, one price point or range, one paragraph of justification tied to the competitive landscape. 4. **Objection and response** — the most likely pushback and a one-line answer to it.
Result
Three pricing models considered:
| Model | Mechanism | Favors |
|---|---|---|
| Per-seat | Customer pays per team member with a login | Vendor as team grows; customer if usage is uneven across seats |
| Per-project | Customer pays per active project tracked in the tool | Customer with few large projects; vendor if customers run many small ones |
| Tiered flat-rate | Customer pays a fixed monthly fee for a capacity band (e.g. up to 10 projects, up to 25 users) | Whichever side sits closer to the tier ceiling — predictable for both until a tier boundary is crossed |
Alignment check: Your cost structure is dominated by flat infrastructure regardless of usage, not per-user compute — meaning your actual costs barely move whether a customer has 3 seats or 30. Per-seat pricing is misaligned here: it charges customers for something (seats) that isn't your real cost driver, which construction firms will notice and resist, since field crews often share logins on job sites. Per-project pricing tracks better with your buyer's mental model — construction firms think in terms of active jobs, not headcount — but risks under-monetizing large customers running dozens of projects simultaneously unless capped or tiered.
Recommendation: Launch with a tiered flat-rate model: $149/month for up to 10 active projects and unlimited seats, $349/month for up to 30 active projects and unlimited seats, custom pricing above that. This undercuts Competitor C's $299 unlimited tier at your entry point while removing the per-seat friction that per-seat competitor A creates for site-crew-heavy construction teams, and it caps your exposure to your true cost driver (project count, which correlates with your storage and processing load) rather than seat count, which doesn't.
Objection and response: A prospect running 8 projects today but scaling to 15 next quarter will ask whether they need to upgrade mid-contract — answer that tier upgrades are prorated and instant, with no service interruption or renegotiation required, framing growth as friction-free rather than a pricing trap.
Most founders price a new product by looking at what competitors charge and picking a number that feels roughly in the middle. That approach ignores the one variable that actually determines whether a pricing model will work long-term: whether the thing you're charging for tracks the thing that actually costs you money. This prompt is built to force that check before recommending a number.
Why this prompt is structured the way it is
The Context section asks for cost structure as a separate, mandatory input from the competitor list, and that separation is deliberate. Competitor pricing tells you what the market has accepted; it says nothing about whether that model fits your own economics. A company with flat infrastructure costs that adopts per-seat pricing because a competitor does will systematically undercharge power users and overcharge light ones — the prompt's alignment-check step exists specifically to catch that mismatch before it ships.
The task list ends with a request for the single most likely customer objection, not a generic list of pros and cons. Founders often discover the real problem with a pricing model in a sales call, after it's already live and awkward to change. Surfacing the most probable pushback — and a ready answer to it — during the analysis stage means the founder walks into their first pricing conversation prepared rather than improvising.
How to adapt it
For an already-launched product with pricing that isn't working, swap the “current pricing idea” field for a description of the actual problem you're seeing (high churn at a specific tier, sales friction on a specific plan) and ask the model to diagnose whether the issue is the model itself or just the price point within a sound model — those require very different fixes.
For usage-based products specifically, it's worth running the prompt twice: once with your current usage patterns, and once with a projected 12-month growth scenario. A pricing model that aligns well today can become misaligned as usage patterns shift, and catching that in advance is cheaper than a mid-year repricing announcement.