SaaS Pricing Strategy vs Pricing Model Picker: Two Engines

Run the SaaS Pricing Strategy Calculator first to set the price floor, then the Pricing Model Picker to choose the structure that delivers at or above it: on the sample inputs the strategy calculator returns a $110 monthly floor and the picker recommends hybrid (seat plus overage). Founders collapse these into one decision, but they answer different questions: "what should my price be" (cost, margin, payback) versus "how should I charge it" (flat, per-seat, usage, hybrid). This article compares the two engines, names which question each answers, and recommends the workflow that gets both decisions right.

1. Two engines, two questions

The SaaS Pricing Strategy Calculator answers the price-floor question. Inputs: COGS per user, target gross margin, target CAC payback months, customer acquisition cost, competitor price. Outputs: recommended monthly price (the floor), margin floor, payback floor, gap vs competitor, competitor gross margin under your COGS. The output is a number with a warning system if competitor pricing is incompatible with target margins.

The Pricing Model Picker answers the structure question. Inputs: average seats per account, average usage units per seat, gross margin per usage unit, monthly account churn, and the competitor's seat and usage prices. Outputs: recommended pricing model (flat, per-seat, usage, hybrid), recommended monthly revenue per account, retention-adjusted projections for each model. The output is a model recommendation with comparative revenue projections.

The two engines are not redundant — they answer different questions in sequence. Madhavan Ramanujam's Monetizing Innovation^[3] framework articulates this clearly: price discovery (what should I charge) and packaging (how should I structure the offer) are separate decisions and should be sequenced as price first, then package.

2. What the strategy calculator returns

Run the strategy calculator with the scenario: $22 COGS per user per month (typical for a B2B SaaS with moderate compute and AI-token usage), 80% target gross margin, 8-month CAC payback target, $380 CAC (loaded with founder time, advertising, content production), $79 competitor price.

The recommended monthly price is $110 (the higher of margin floor and payback floor). The margin floor is $110 (COGS $22 / (1 − 80%)), and the payback floor is $69.50. The gap vs the competitor is $31 ($110 your floor minus $79 competitor), and the competitor's gross margin under your COGS is 72.15% — lower than your 80% target if they operate at your cost structure. The engine raises the warning: "Competitor price is below your target margin floor under current COGS."

The strategic information: the competitor is pricing below the math required for your cost structure and target margin. Three explanations: (a) the competitor has lower COGS than you do, (b) the competitor operates below 80% gross margin, (c) the competitor under-prices to acquire market share. Each calls for a different response. The methodology behind the strategy calculator is documented at the SaaS Pricing Strategy Calculator methodology page^[4].

3. What the model picker returns

Run the model picker on the same product: it takes the average seats per account, the average usage units per seat, your gross margin per usage unit, the monthly account churn, and the competitor's seat and usage prices. From those it scores four structures — flat monthly, per-seat, usage-based, and hybrid (seat + overage) — and recommends the one with the highest retention-adjusted revenue per account.

For a B2B AI tool with meaningful tail consumption, the picker typically lands on hybrid: the seat fee covers predictable baseline access and the usage charge captures the variable consumption that flat or pure per-seat pricing would give away. The decision-relevant output is the comparison itself — whichever structure the picker recommends, its per-account revenue has to clear the $110 floor the strategy calculator set, or the structure breaks unit economics regardless of how elegant the packaging is.

The methodology behind the picker is documented at the Pricing Model Picker methodology page^[5]. The pricing model picker per-seat vs usage article covers the picker's outputs in detail.

4. When to run the strategy calculator first

Strategy first is the default workflow. Run the strategy calculator first when:

• You have not yet shipped pricing. A new product needs the floor before the structure. Running the picker first creates a model based on guessed prices, which is reverse engineering.
• You are repricing an existing product. Repricing decisions need to clear the new margin floor (which may have moved due to COGS or CAC changes), then choose the right structure.
• Competitive pressure is forcing a price change. The strategy calculator will flag whether the competitive price is below your margin floor — critical information before reacting.
• Your CAC is unstable. A rising CAC raises the payback floor. The strategy calculator surfaces this; the picker is silent on it.

Patrick Campbell's research at Paddle/ProfitWell^[1] consistently shows that SaaS companies under-price by 30% to 50% relative to value when they skip the floor calculation. The skipping happens because the founder picks a model first ("our competitor uses per-seat, so we should too") and then anchors the price to the competitor without checking margin viability.

5. When to run the model picker first

Picker first is the right workflow in two narrow contexts:

Repricing the structure but not the price level. If you are confident in your price level (because you have data from existing customers) and the question is purely "should I switch from per-seat to usage-based," the picker is the right starting point. The strategy floor is already cleared; only the structure is uncertain.

Designing a new packaging within an established product line. If you have a $99 flat product and you want to add a $30 starter tier or a $250 enterprise tier, the picker helps decide the right structure for the new tier. The strategy floor for the main product is already set; the new tier is a packaging extension.

Outside these two contexts, picker-first is structurally vulnerable to choosing a packaging that does not clear the margin floor. A meaningful share of small SaaS companies operate below their stated margin targets — an illustrative estimate is roughly a third of companies under $5M ARR — with pricing-model mismatches a primary cause^[2].

6. The combined workflow that prices SaaS correctly

The combined workflow is a 4-step sequence:

1. Run the strategy calculator to set the price floor. Output: minimum monthly revenue per account that clears margin and payback targets.
2. Run the model picker with multiple candidate inputs (per-seat at $X, usage at $Y, hybrid at $Z). Output: which model delivers the most revenue per account at viable inputs.
3. Verify the picker output exceeds the strategy floor. If yes, the model is viable. If no, the model is broken — either adjust the inputs (raise per-seat price, raise overage) or pick a different model.
4. Stress-test for churn sensitivity. Re-run the picker at 6% monthly churn and 10% monthly churn. If the recommended model collapses (negative unit economics), the structure is fragile and should be revisited.

In the worked scenario, strategy returns $110 floor and picker returns $169.75 hybrid revenue. The picker output (169.75) exceeds the floor (110) with ample margin, so the hybrid model is viable. The strategic answer: hybrid pricing at the input rates ($25/seat × 4 seats + $35 overage), positioned against a competitor priced at $79 with a margin disadvantage they will eventually have to fix.

7. Common errors when using only one

Strategy-only errors: founders run the strategy calculator, get $110 as the floor, ship at $110 flat-monthly. Outcome: revenue is $110 per account, but the picker would have shown hybrid at $169.75 captures additional value. Founders leave 35% to 50% of revenue per account on the table by skipping the picker.

Picker-only errors: founders run the picker, get hybrid $169.75 as recommendation, ship hybrid. Outcome: revenue is $169.75 per account but COGS at $22/user × 4 users = $88/account. Gross margin is 48% instead of the 80% target. Unit economics are quietly broken; the founder discovers it when fundraising or selling and has to reprice.

Both errors are large enough to materially affect the trajectory of the business. The combined workflow prevents both by enforcing the sequence: floor first, structure second, verification third.

8. Which to start with

Decision rule:

• New product, no pricing yet: strategy first.
• Existing product, repricing the level: strategy first.
• Existing product, considering structure change at established price: picker first.
• Designing a new tier within an existing product line: picker first.
• Competitive pressure forcing a response: strategy first, to determine whether your floor can match competitor pricing without breaking margin.

The broader lesson from cloud-pricing research is that pricing discipline compounds^[6]: teams that run a deliberate strategy step and a deliberate model-selection step, in sequence, tend to leave less margin and expansion on the table than teams that skip both. Running both is a quiet competitive advantage.

Frequently asked questions

What is the difference between SaaS pricing strategy and pricing model picker?

Strategy answers 'what should my price be' — a floor derived from COGS, target margin, and CAC payback. Picker answers 'how should I charge that price' — flat, per-seat, usage, or hybrid. The strategy calculator returns $110/month as the floor; the picker decides whether $110 should be billed as one flat monthly fee, $25 per seat × 4 seats, or hybrid.

Which engine should I run first?

Strategy first. The floor price has to clear margin and payback requirements; the model picker is downstream of that. Founders who pick a pricing model first (hybrid, per-seat, etc) and back into a price often end up below the margin floor and discover months later that their unit economics are broken.

Can the two outputs conflict?

Yes, and the conflict is informative. If the strategy calculator says $110/month and the picker recommends a hybrid model at $169.75/month, the hybrid model wins — it captures more value per account while still clearing the floor. If the picker recommends a model below the floor, the model is wrong.

How do CAC and payback fit into the model picker?

They do not directly. The model picker assumes the price is already set; it just chooses the best structure for that price. CAC and payback are inputs to the strategy calculator, which sets the floor. The two engines decouple the 'how much' question from the 'how to charge' question.