# Pay What You Want Pricing for SaaS and Digital Products: When It Works

> Strategic guide to Pay What You Want pricing. When PWYW outperforms fixed pricing, the math behind minimum and suggested prices, real-world results, and implementation patterns.
- **Author**: Ayush Agarwal
- **Published**: 2026-05-08
- **Category**: Pricing, SaaS, Billing
- **URL**: https://dodopayments.com/blogs/pay-what-you-want-pricing-saas

---

Pay What You Want (PWYW) sounds like a gimmick. Set a minimum, let buyers choose the price, hope they pay more than the floor. In practice, it is one of the more interesting pricing experiments digital businesses can run, with measurable advantages over fixed pricing in specific scenarios.

This guide is the strategic framework: when PWYW wins, when it fails, the math behind minimums and suggested prices, and the implementation patterns that protect revenue while maximizing customer participation.

## What Pay What You Want Actually Is

PWYW is a pricing model where the customer decides what they pay, within boundaries you set. The standard structure has three numbers:

1. **Minimum price** - The floor. Customer cannot pay below this.
2. **Suggested price** - The anchor. A recommended amount displayed at checkout.
3. **Customer-chosen price** - What they actually pay, between the minimum and any reasonable maximum.

Think of it as auction-style pricing for buyers, with a reserve price you control.

> Pay What You Want only looks like price-setting freedom. In practice, the minimum and suggested price you choose determine 80 to 90 percent of revenue distribution. The customer's "freedom" is bounded by the anchors you set.
>
> - Ayush Agarwal, Co-founder & CPTO at Dodo Payments

For broader pricing context, see our companion guides on [SaaS pricing strategy](https://dodopayments.com/blogs/saas-pricing-strategy-guide) and [pricing psychology](https://dodopayments.com/blogs/pricing-psychology).

## When PWYW Works

```mermaid
flowchart TD
    A[Pricing Decision] --> B{Product Type}
    B -->|Digital, near-zero marginal cost| C{Use Case}
    B -->|Physical, real COGS| D[Skip PWYW]
    B -->|SaaS subscription| E[Skip PWYW for sub itself]
    C -->|Templates / E-books| F[Strong PWYW fit]
    C -->|Open source / Creator support| G[Strong PWYW fit]
    C -->|Beta launch / Experiment| H[Strong PWYW fit]
    C -->|Bundle / Charity tier| I[Good PWYW fit]
    F --> J[Set minimum, anchor with suggested]
    G --> J
    H --> J
    I --> J
```

PWYW is the right pricing model when:

1. **Marginal cost is near zero.** Digital templates, e-books, online courses, plugins, music, and software downloads have minimal per-unit cost. PWYW lets customers self-select while you keep margin on every sale.
2. **Customer base has high willingness-to-pay variance.** Some customers value the product at $10, others at $100. PWYW captures both ends of the curve, where fixed pricing forces you to choose one segment.
3. **Community or supporter dynamics exist.** Open-source maintainers, indie creators, charities, and educators all benefit from PWYW because some customers actively want to pay more to signal support.
4. **You want to lower the barrier to entry.** PWYW with a $0 or near-$0 minimum dramatically increases participation. Helpful for early-stage products that need usage data.
5. **The product is a one-time purchase.** PWYW pairs well with one-time purchases. It is rarely appropriate for subscriptions, where customers want predictable pricing.

## When PWYW Doesn't Work

Skip PWYW when:

- **You are selling a subscription.** Customers do not want to renegotiate price every billing cycle. Use tiers or [usage-based pricing](https://dodopayments.com/blogs/usage-based-billing-saas) instead.
- **Marginal cost is real.** Physical products, services that consume engineer hours, anything with meaningful cost-of-goods will lose money if customers pay near the minimum.
- **Your customers are enterprise.** Procurement teams want fixed pricing they can compare. PWYW reads as unprofessional in B2B contracts above ~$500.
- **The product is "table stakes" software.** Customers paying for essential business software have no patience for choosing prices. Just set the price.
- **You don't have a clear minimum-price calculation.** Without knowing your floor, you will set the minimum too low and lose money or too high and kill participation.

## The Math: Setting Minimum and Suggested Price

The two numbers that determine PWYW success.

### Minimum Price

The minimum is your protection floor. Calculate it as:

```
Minimum = Direct cost per sale + Payment processing fee + Refund risk buffer
```

For a digital template selling at $10 minimum:

| Component | Amount |
|---|---|
| Direct cost (asset hosting, support, ops) | $0.50 |
| Payment processing (4% + $0.40 with Dodo) | $0.80 |
| Refund risk buffer (5% of expected revenue) | $0.50 |
| Minimum protection floor | $1.80 |
| Minimum sale price (with margin) | $5 to $10 |

The minimum should be at least 2 to 3x the protection floor. Below that, you make negligible margin on minimum-priced sales.

### Suggested Price

The suggested price is the anchor. Behavioral pricing research consistently shows it captures 60 to 80 percent of customer choices.

Set the suggested price at 1.5 to 3x the minimum:

| Minimum | Suggested | Customer Distribution |
|---|---|---|
| $5 | $10 | 20% pay $5, 60% pay $10, 20% pay >$10 |
| $5 | $15 | 30% pay $5-7, 50% pay $10-15, 20% pay >$15 |
| $10 | $25 | 25% pay $10-12, 55% pay $20-25, 20% pay >$25 |

These distributions are starting heuristics. Your actual numbers will depend on customer base, value proposition, and visibility of the suggested price.

### Average Revenue Per Customer

PWYW typically generates 60 to 90 percent of fixed-price revenue per customer. The trade-off is participation: PWYW often increases unit volume by 50 to 200 percent.

The math:

- Fixed price at $20: 100 customers buy at $20 = $2,000
- PWYW with $5 minimum, $20 suggested: 250 customers, average $13 = $3,250

PWYW wins on volume in this scenario, even though average revenue per customer is lower.

## Real-World PWYW Examples

| Company / Use Case | Strategy | Result |
|---|---|---|
| Humble Bundle | PWYW for game bundles with charity tier | Multi-million dollar revenue, 40-60% above suggested |
| Radiohead "In Rainbows" album | $0 minimum, no suggested | Average paid: $6, 1.2M paid downloads |
| Indie game devs (itch.io) | $5 minimum, $15 suggested | 15-25% pay above suggested |
| Open-source maintainers | $0 minimum, $25 suggested | 60% pay $5-15, 5% pay $50+ |
| Educational courses | $20 minimum, $99 suggested | Most pay $50-99, 5% pay full |

The pattern: PWYW excels when customers have a relationship with the creator/cause, or when the product is positioned as supportable rather than transactional.

## Implementation: PWYW in the Billing Stack

PWYW adds specific complexity to your payment infrastructure.

### Customer Input Validation

Customers can enter any number above the minimum. Your checkout must:

- Block submission below the minimum with a clear error
- Handle "$0" attempts gracefully if you allow them
- Respect maximum reasonable amounts (PWYW does not mean unlimited)
- Validate currency and decimal precision

### Payment Processing

Each PWYW transaction is unique in amount. Your payment processor must:

- Accept dynamic amounts at checkout (most do)
- Handle partial refunds correctly (refund the actual paid amount, not the suggested)
- Issue receipts that show the customer's chosen price
- Calculate tax on the actual paid amount, not the suggested

### Tax Calculation

This is where PWYW gets tricky for global sellers. If a customer in Germany pays $20 instead of the suggested $15, the VAT base is $20, not $15. Your tax engine (or [Merchant of Record](https://dodopayments.com/blogs/merchant-of-record-for-saas)) must calculate tax on the actual amount.

For global digital sales, see our companion guides on [VAT compliance for digital products](https://dodopayments.com/blogs/vat-compliance-digital-products) and [VAT vs sales tax for SaaS](https://dodopayments.com/blogs/vat-vs-sales-tax-saas).

### Analytics and Reporting

Track these metrics for any PWYW product:

- **Distribution of paid prices** - histogram of what customers chose
- **Conversion rate** - PWYW vs your previous fixed pricing
- **Average revenue per customer** - the actual payment, not the suggested
- **Refund rate** - PWYW often has lower refund rates because customers self-selected price
- **Repeat purchase rate** - PWYW often improves repeat rates because customers feel ownership

## Common PWYW Mistakes

Patterns that destroy PWYW programs:

- **Minimum set too low.** $0 minimums work for charity but rarely for commercial products. Set the minimum where it covers cost plus margin.
- **No suggested price.** Without an anchor, customers default to paying the minimum. The suggested price is what makes PWYW work commercially.
- **Suggested price way too high.** A $5 minimum with $50 suggested feels manipulative. Customers either pay $5 in protest or skip the product.
- **Using PWYW for subscriptions.** Customers want subscription pricing to be stable. PWYW for monthly recurring is friction at every renewal.
- **No tax handling.** Selling globally without proper tax on the actual paid amount creates compliance gaps that grow rapidly with volume.
- **Treating PWYW as "free."** PWYW means "customer chooses, but pays." It is not free distribution with optional payment.
- **No analytics.** Without tracking distribution and conversion, you cannot tune the minimum and suggested prices.

> Pay What You Want is most successful when used for one-time purchases of digital products with clear value but variable customer willingness to pay. Use it as a strategic experiment, not a default. Every PWYW success story has tight control over the minimum and the suggested price.
>
> - Rishabh Goel, Co-founder & CEO at Dodo Payments

## Pricing Tests Before Going All-In

Before launching PWYW broadly, run these tests:

1. **A/B test against fixed pricing** for one product over 30 days. Measure: total revenue, customers, average order value, refund rate, repeat rate.
2. **Test minimum price levels** at 50%, 75%, and 100% of your fixed price. Find the floor that doesn't kill volume.
3. **Test suggested price anchors** at 1.5x, 2x, and 3x the minimum. Find the anchor that maximizes average payment.
4. **Test with different customer segments.** PWYW often performs differently for new vs returning customers, or by traffic source.

For more on pricing experimentation, see our companion guides on [pricing page conversion optimization](https://dodopayments.com/blogs/pricing-page-conversion-optimization), [psychological pricing](https://dodopayments.com/blogs/psychological-pricing), [SaaS pricing calculator](https://dodopayments.com/blogs/saas-pricing-calculator), and [tiered pricing model guide](https://dodopayments.com/blogs/tiered-pricing-model-guide).

## How Dodo Payments Handles PWYW

Dodo Payments has native Pay What You Want support for one-time products:

- **Native PWYW toggle** on any single-payment product
- **Customer-defined price** at checkout with built-in minimum enforcement
- **Optional suggested price** displayed prominently to anchor customer choice
- **Per-transaction tax calculation** on the actual paid amount across 220+ countries
- **Accurate receipts and invoices** showing the customer's chosen price
- **Webhook events** triggered on PWYW payment success with the actual amount
- **Refund handling** at the actual paid amount, not the suggested
- **Full Merchant of Record coverage** so global tax stays accurate regardless of paid amount
- **Transparent pricing** at 4% plus 40 cents per transaction with no monthly fees

For implementation patterns, see the [Pay What You Want feature documentation](https://docs.dodopayments.com/features/pay-what-you-want), [checkout sessions documentation](https://docs.dodopayments.com/features/checkout-session), and [refunds documentation](https://docs.dodopayments.com/api-reference/refunds/post-refunds).

## FAQ

### What is Pay What You Want pricing?

Pay What You Want (PWYW) is a pricing model where customers choose how much to pay, within boundaries the seller defines. The standard structure has a minimum price (floor), a suggested price (anchor), and customer-chosen amount above the minimum. PWYW works best for digital products with low marginal cost, high willingness-to-pay variance, and supporter dynamics.

### When does PWYW outperform fixed pricing?

PWYW outperforms fixed pricing when product marginal cost is near zero, customer willingness to pay varies widely, and a community or supporter dynamic exists. Common winners are digital templates, e-books, courses, indie games, open-source software, and creator-supported content. PWYW is rarely the right choice for subscriptions, enterprise software, or physical products.

### How do I set the minimum and suggested price?

The minimum should cover direct cost plus payment processing plus a refund buffer, then add 2 to 3x as margin. The suggested price should be 1.5 to 3x the minimum. Run A/B tests with different anchor levels to find the combination that maximizes average revenue per customer for your specific product and audience.

### What is the average revenue impact of PWYW?

PWYW typically generates 60 to 90 percent of fixed-price revenue per customer, but increases unit volume by 50 to 200 percent. Net effect is usually 1.5 to 2x total revenue when applied correctly to the right product type. Wrong product or wrong anchors can cut revenue significantly versus fixed pricing.

### Can a Merchant of Record handle PWYW?

Yes. A Merchant of Record like Dodo Payments handles PWYW natively, including tax calculation on the actual paid amount, refunds at the chosen price, and webhook events with accurate transaction data. This is especially important for global digital sales where tax must be calculated on what the customer actually paid, not the suggested price.

## The Takeaway

Pay What You Want is a powerful pricing tool when applied to the right product (digital, near-zero marginal cost) with the right structure (clear minimum, well-anchored suggested price). Used incorrectly (subscriptions, enterprise, physical goods, no anchor) it destroys revenue while feeling generous.

The right approach: identify products where customer willingness-to-pay varies widely, set a minimum that protects cost, anchor with a suggested price 1.5 to 3x the minimum, run A/B tests against fixed pricing, and tune based on real distribution data.

If you want a billing platform that handles PWYW natively with tax on actual paid amounts, dynamic checkout, and accurate refunds, [Dodo Payments](https://dodopayments.com) ships it as part of the one-time payment engine. See the [pricing page](https://dodopayments.com/pricing) and [Pay What You Want feature documentation](https://docs.dodopayments.com/features/pay-what-you-want).
---
- [More Pricing articles](https://dodopayments.com/blogs/category/pricing)
- [All articles](https://dodopayments.com/blogs)