Do I need to know customer willingness to pay before choosing a pricing model?

Yes. Survey 20+ target customers about price sensitivity, budget approval chains, and payment preferences. This determines if you can charge $19/mo (individual) or need $500+/mo (enterprise). If you skip this, you'll either price too low (can't cover support costs) or too high (nobody buys).

When should I use usage-based pricing vs. subscription pricing?

Use usage-based if usage varies 10x month-to-month (e.g., SMS sending, API calls, transactions). Use subscription if usage is predictable (same customer uses the same way each month). Hybrid (base subscription + overage) works when core usage is predictable but spikes are possible.

What's the minimum price I should charge?

Minimum = (Total cost to onboard one customer ÷ 50 months) × 2-3x. If onboarding costs $1K, minimum is $1K÷50 = $20/mo, but price at $60-100/mo to have margin. Don't go lower or you'll lose money on each customer.

Should I offer freemium or free trial?

If you have a growth bottleneck ('nobody's trying us'), go freemium. If people try but don't convert, go 14-day free trial (time pressure). Not both. Freemium is unlimited access with feature limits; free trial is full access for N days.

SaaS Founder's Pricing Decision Framework: 7 Questions to Get It Right

Updated May 16, 2026 • 12 min read • By PricePulse

The hardest pricing decision isn't optimizing your unit economics. It's choosing between fundamentally different models.

Do you go freemium or free trial? Subscription or usage-based? Flat-rate or tiered? Each choice locks you into a different customer acquisition path, revenue pattern, and support burden.

This framework walks you through 7 critical questions that will narrow down which model fits your business, your customers, and your growth stage.

Question 1: Do You Know Your Customer's Willingness to Pay?

Before choosing a pricing model, you need baseline data on what customers will actually pay.

Decision Factors:

Have you surveyed 20+ target customers about price sensitivity?
Do you know if your customer pays you or their manager does?
Can you segment customers by company size and industry?

Why This Matters

If you build subscription pricing for customers who need a $5K/year budget approval, you'll starve to death at $49/month.

If you build usage-based pricing for customers with unpredictable workloads, they'll churn the month they hit a surprise bill.

Action: Spend 1 week interviewing 20 target customers. Ask:

"What's the budget threshold for this software?" (i.e., does it need executive approval?)
"How would you pay?" (annual, monthly, per-usage, per-seat?)
"What's the price that feels too cheap vs. too expensive?"

Red flags: If 80% of answers are "I don't know," your target market is not urgent enough yet. Consider freemium first to build usage data.

Question 2: Is Usage Predictable or Highly Variable?

This question alone narrows your model choice dramatically.

Usage Pattern Best Model Why Predictable
(same customer uses it the same way every month) Subscription (fixed-rate or tiered) Customers budget predictably. You have predictable revenue. Highly variable
(usage spikes unpredictably, 10x swings) Usage-based (per-API-call, per-message, per-analysis) Fixes misalignment. Heavy users pay more. Light users pay less. Bimodal
(core features used predictably, add-ons used variably) Hybrid: Base subscription + usage overage Customers get baseline predictability + fair upside pricing.

Examples

Predictable usage: Figma. A design team opens the file, works 6-8 hours/day, saves. Usage is consistent month-to-month. Subscription model works perfectly.

Highly variable usage: SendGrid. A customer might send 1K emails in February and 50K in November (Black Friday campaign). Usage-based pricing ($0.10 per 1K emails) lets them pay for what they use.

Bimodal usage: Stripe. Base feature (payment processing) is high-volume and variable. But chargebacks and refunds are occasional overhead. Stripe charges fixed % (subscription-like) on processing + flat fee for refund handling (usage-based for add-on).

Question 3: Who Is Your Buyer? (And Who Feels the Price?)

This determines where price sensitivity lives in the organization.

A. Does an end-user pay directly? (e.g., Figma for freelancers, Notion for students)

→ Go Subscription + Free Trial
Users need to evaluate before paying. Friction must be minimal. Freemium works if trial is limited enough.

B. Does a company buyer pay for many users? (e.g., HubSpot for 50-person sales teams, Figma for design departments)

→ Go Tiered by Seat or ROI
They need to show ROI to finance. Pricing tied to team size ($99/mo × 5 people) or value ($X per customer acq) makes the business case clear.

C. Does the buyer never see the end-user? (e.g., Twilio - app developers integrate, end-customers never know)

→ Go Usage-Based
The buyer cares about cost per unit (per SMS, per API call). A startup sending 100K SMS/day shouldn't subsidize one sending 1K/day.

D. Is the buyer risk-averse and security-conscious? (e.g., enterprises buying compliance tools)

→ Go Annual Subscription + Custom Tiers
They need budget certainty and multi-year commitments. Usage-based pricing feels risky. Usage spikes = bill shocks = buyer gets fired.

Question 4: How Much Onboarding Does the Customer Need?

High-onboarding products have different pricing dynamics than self-serve products.

Onboarding Style Implication for Pricing Self-serve only
(docs, templates, YouTube) Can go lower-priced and broader appeal. Freemium works. Usage-based attracts experimentation. Needs 1-2 hour setup call
(common for B2B SaaS) Minimum $500-1K/mo price tier else your support cost exceeds customer LTV. Freemium doesn't work. Needs custom implementation
(3+ days of consulting) Charge implementation separately from subscription. E.g., Salesforce: $150/user/mo + $50K setup fee.

Why?

If a customer needs a 2-hour onboarding call and you're charging $29/mo, you lose $1-2K just getting them live. You'll go out of business. You must price higher, or the onboarding is unsustainable.

Rule of thumb: Monthly price should be at least 1-2% of your full-loaded cost-to-acquire. If onboarding costs $1,000, minimum pricing is $1,000 ÷ 50 months = $20/mo. But that's break-even. Price at $100-300/mo to have margin.

Question 5: Can You Tier by Value or Are You Stuck With Tier-by-Feature?

The best SaaS pricing tiers by value delivered. The lazy approach tiers by features.

Value-based tiering (Figma):

Free: Single project, read-only sharing
Pro: Unlimited projects, real-time collab (the value) = $12/mo
Organization: Team management for 50+ people (the value) = $144/mo

Each tier unlocks a job the customer actually needs to do. Price correlates to the problem solved.

Feature-based tiering (lazy approach):

Basic: Dashboard access, 10 users
Pro: Dashboards + Reports, 50 users
Enterprise: Dashboards + Reports + Alerts, unlimited users

This works but feels arbitrary. Customers don't buy features; they buy outcomes. If "Alerts" doesn't save them time/money, they skip it.

How to think about tiers:

Free/Trial: Solves core problem at baseline (1-2 people, 1 project, limited integrations)
Tier 2 (Growth): Adds 1 critical job-to-be-done (team collaboration, advanced analytics, automation)
Tier 3 (Scale): Adds another job (compliance, SSO, API access, SLAs)

Question 6: What's Your Growth Bottleneck Right Now?

Early-stage pricing should remove your bottleneck, not optimize for MRR.

Bottleneck: "Nobody's trying our product"

→ Go Freemium
Free tier with usage limits gets 10x more signups. You need volume first. You'll optimize pricing later.

Bottleneck: "People try us but don't convert to paid"

→ Go Free Trial (14 days)
Same problem. But time pressure (trial expires) creates urgency that freemium doesn't. Remove feature limits; remove by time instead.

Bottleneck: "We have paying customers but our LTV is too low"

→ Test Tiered Pricing
You've proven PMF. Now optimize revenue. Add higher tiers. Implement upsell sequences. Charge for add-ons.

Bottleneck: "Customers are churning because of price"

→ Go Usage-Based or Add a Lower Tier
Customers don't want to kill service; they want fair pricing. "Pay for what you use" reduces churn. Or add a $9/mo tier for power users who only need one feature.

Question 7: Can You Monitor and Change Pricing Later?

Your pricing in Month 1 doesn't need to be perfect. But you need to be able to change it.

Things that make pricing changes easier:

Month-to-month billing: You can raise prices next month for new customers
Grandfather existing customers: Keep current customers at old price; new signups pay new price
Usage-based pricing: You can adjust per-unit costs more easily than tier thresholds
Annual contracts: Price only changes on renewal (every 12 months)

Avoid: Multi-year contracts at fixed pricing for early-stage SaaS. You don't know your unit economics yet.

The Complete Decision Framework

Use this flowchart to pick your starting model. Remember: You will change this later. This is just your starting point.

START HERE: Does usage vary unpredictably month-to-month (10x swings)?

YES → Go Usage-Based Pricing

Per-API-call, per-message, per-transaction
Include a free tier or monthly cap for safety
Example: Twilio ($0.0075 per SMS)

NO (usage is predictable) → Does your customer need a sales call?

YES (B2B, complex setup) → Subscription + Custom
$500-2K/mo minimum. No freemium. Enterprise gets custom tiers.
NO (self-serve) → Does the buyer need to show ROI to finance?
- YES (team of 5+ at $X/yr budget) → Tiered by Seat or Value
  E.g., $99/mo × team size OR $X per revenue generated
- NO (individual user pays) → Subscription + Freemium or Free Trial
  Low friction entry. Free tier or 14-day trial. Then $19-99/mo.

Real-World Pricing Decisions (5 SaaS Examples)

1. Figma ($12/mo Pro, $144/mo Organization)
Decision framework: Predictable usage (design teams work same hours daily) + end-user payer + high onboarding (needs tutorials). Result: Subscription + Tiered. Free tier with single project teaches the tool.

2. Intercom (usage-based $0.99 per conversation resolution)
Decision framework: Highly variable usage (some companies get 100 chats/day, others 5,000) + embedded customer success tool + buyer never directly interacts. Result: Usage-based. Charges for the job done (resolutions), not seat count.

3. Notion ($10/mo, no free tier initially)
Decision framework: Predictable usage (people work same way daily) + end-user payer + self-serve + no mandatory onboarding. Result: Freemium (added free tier in 2022 because growth bottleneck). Then tiered for teams.

4. Salesforce (per-user seat pricing $150-300/mo + custom enterprise)
Decision framework: Highly variable adoption (some teams use it 8 hrs/day, others as CRM-only) + company buyer needs ROI justification + complex onboarding (typically requires consultant). Result: Per-seat subscription + custom pricing for large deployments. Per-seat makes the business case simple ("$150/mo × 50 reps = $7.5K/mo").

5. GitHub Copilot ($19/mo or $200/yr per developer or per-organization)
Decision framework: Variable usage (junior devs might use 5 hrs/week, seniors 30 hrs/week) + developer pays directly + self-serve + no onboarding needed. Result: Subscription (per-user) + free trial. Switched from $10 to $19 in 2025 because market demanded the tool; pricing power increased.

Implementation Checklist

Once you've chosen your model, implement it with these steps:

Set minimum price: (Onboarding cost ÷ 50 months) × 2-3x margin. Don't go lower; you'll starve.
Set maximum price: 10-20% of your customer's annual savings from using your tool.
Set up trial or free tier: 14-day trial (time pressure) or freemium (feature limit). Not both.
Plan upgrade path: How does Free → Pro → Enterprise happen? Is it automatic or sales-assisted?
Set review cadence: Every quarter, review churn by price tier and cohort. Adjust if 10%+ monthly churn from pricing complaints.
Grandfather existing customers: New pricing applies to new signups only. Existing customers keep old price or given 30 days notice.

How Are Your Competitors Pricing?

Use PricePulse to track pricing changes across your entire SaaS stack. Know when your competitors move first.

Check Your Tools → Calculate Stack Cost →