Author: onetwothreeadmin

Gumroad’s pay-what-you-want (PWYW) pricing looks like a generous experiment until you run the numbers. The feature lets buyers name their own price above a floor you set—or no floor at all. The pitch is that generosity builds goodwill, increases conversions, and unlocks buyers who’d never pay full price.

The reality is messier. PWYW can work, but only in narrow conditions. Most operators who flip the switch see average transaction values drop between 40% and 70% compared to fixed pricing, even when they set a suggested price. The question isn’t whether PWYW lowers your per-sale revenue—it does—but whether the volume increase offsets the loss.

What buyers actually pay when you let them choose

Three anonymised operators shared their Gumroad dashboard data after running PWYW experiments on digital products priced between $15 and $49. Here’s what happened:

• Operator A: A $29 Notion template. Fixed price averaged $29 (obviously). PWYW with a $15 floor and $29 suggestion averaged $18.40 over 200 transactions. Conversion rate increased 22%, but total revenue dropped 18%.
• Operator B: A $49 course bundle. PWYW with no floor and a $49 suggestion averaged $12.60 over 180 sales. Conversion rate doubled, revenue increased 9%. The operator considered it a win but switched back after realising most new buyers never purchased again.
• Operator C: A $15 guide. PWYW with a $10 floor averaged $11.30. Conversion rate increased 8%, revenue dropped 31%. Switched back to fixed pricing within two weeks.

The pattern: PWYW reliably increases conversion rate, but average order value collapses. The floor matters—Operator A’s $15 minimum kept the average above $18, while Operator B’s lack of a floor invited $5 and $7 payments on a product originally priced at $49.

When PWYW makes sense (and when it doesn’t)

PWYW works best as a short-term acquisition tool, not a permanent pricing strategy. The clearest use case is launching a new product to an untested audience. You’re optimising for feedback and social proof, not revenue. A $0 floor with a reasonable suggestion—say, $19 on a product you plan to price at $39—gets you early buyers, testimonials, and usage data you can fold into the final version.

It also works for products with near-zero marginal cost and high repeat-purchase potential. If you’re selling a lightweight template or checklist and you have a clear upsell or backend offer, PWYW can fill the top of your funnel cheaply. But if the product is your only offer, or if you’re selling something that required weeks of work to build, PWYW usually just trains your audience to expect discounts.

Where it fails: evergreen products with established audiences. If people already know your work and trust your pricing, PWYW doesn’t increase conversions meaningfully—it just gives existing buyers permission to pay less. Operator C’s 8% conversion lift didn’t justify a 31% revenue drop because the audience was already warm.

The non-obvious cost: anchoring your own pricing

The hidden risk of PWYW is psychological, not financial. Once you’ve let buyers pay $10 for something you later price at $39, you’ve anchored their perception of value. If they see the same product—or something similar—at the higher price later, they’ll assume you’re overcharging, not that they got a deal earlier.

This is particularly painful if you run PWYW as a launch discount and then switch to fixed pricing. The buyers who paid $8 will tell others they paid $8. The new buyers who see $39 will Google your product, find Reddit threads or tweets mentioning the lower price, and wait for another sale. You’ve effectively turned a one-time experiment into a permanent discount expectation.

The fix: if you use PWYW, frame it explicitly as a beta, a launch window, or a limited-time test. Set a public end date and stick to it. Don’t let it drift into your evergreen offer.

Gumroad’s PWYW settings: what to toggle

Gumroad gives you three levers: minimum price, suggested price, and whether to show the suggestion. The minimum is a hard floor—buyers can’t pay less. The suggested price is what Gumroad displays in the checkout field by default. If you hide the suggestion, the field is blank and buyers have to decide with no anchor.

Showing the suggestion raises the average payment by 30–50% compared to hiding it, based on the data above. Operator B’s $12.60 average with a $49 suggestion would likely have dropped below $10 with no suggestion shown. If you’re going to use PWYW, always show a suggestion—and set it at 60–70% of your intended fixed price, not 100%. A $49 suggestion on a product you plan to sell for $49 just makes buyers feel like they’re being manipulated into paying full price anyway.

The minimum should be at least 30–40% of your target price, unless you’re explicitly using PWYW as a free-plus-reputation play. Operator A’s $15 floor on a $29 product kept the average at $18.40. Operator B’s $0 floor tanked the average to $12.60 on a $49 product. Floors work.

Want more pricing breakdowns, tool comparisons, and operator data? Subscribe to One Two Three Send and get one article like this every day.

Stripe payment links let you sell anything without building a checkout page. You generate a URL, share it, and collect money. Simple. But buried in the link settings is an expiration option most operators never touch—and that’s a mistake.

Payment link expiration does two things: it creates urgency for time-sensitive offers, and it prevents confusion when pricing or terms change. Set correctly, it can lift conversions. Set carelessly, it kills them.

How payment link expiration works

When you create a Stripe payment link, you can set an expiration date and time. After that point, the link returns a message telling the buyer it’s no longer available. The product, price, and subscription settings remain unchanged in your Stripe dashboard—only the link stops working.

Stripe gives you three expiration options:

• No expiration — the link works indefinitely
• After a specific date and time — you pick an exact cutoff
• After a certain number of uses — the link deactivates after X successful payments

The third option is rarely useful unless you’re selling a fixed number of spots (a cohort course, a live workshop, a limited consulting package). The first two are where most operators make their choice—and where most get it wrong.

When to set an expiration date

Use expiration when the offer itself has a deadline. Launch pricing that ends Friday. Early-bird tickets for an event. A discount code you’re running for 72 hours. A beta program with a cap on participants.

In these cases, expiration reinforces the urgency you’re already creating in your messaging. If your email says “price goes up Sunday at midnight,” the payment link should expire Sunday at 11:59 PM in your time zone. Otherwise, someone who bookmarks the link can return three weeks later and pay the old price—or worse, pay the old price for a product that no longer matches the description.

Expiration also prevents billing confusion. If you raise your subscription price from $15 to $25 per month, every old payment link still floating around the internet will charge $15. Someone clicking a six-month-old tweet can subscribe at the wrong price, and you won’t know until you audit your transactions. Setting expiration on price-change announcements cleans this up automatically.

When NOT to set expiration

If the offer is evergreen, don’t add artificial urgency by setting a deadline you don’t intend to honor. Operators sometimes set a 30-day expiration “just in case,” then regenerate the same link with a new expiration date when it runs out. This creates busywork and breaks inbound links.

Permanent products—courses, memberships, one-time purchases with stable pricing—should use non-expiring links. You can always deactivate a link manually in Stripe if you need to pull it, but starting with an arbitrary countdown adds friction without benefit.

The exception: if you’re testing messaging or pricing and want to force yourself to revisit the offer in 90 days, expiration can act as a forcing function. Just be clear with yourself that it’s an internal deadline, not a customer-facing one.

The non-obvious tactic: expiration as a segmentation signal

Here’s a use case most operators miss. If you send the same payment link to two audiences—your email list and a Reddit post—you can’t tell which source drove the sale unless you use UTM parameters or create separate links.

Creating separate links with different expiration dates lets you segment behavior without touching your analytics stack. Send a 48-hour expiring link to your email list and a 7-day expiring link to social. When you check Stripe’s payment link analytics, you’ll see which link performed and when it stopped converting.

This isn’t a replacement for proper attribution tracking, but it works when you need a quick answer and don’t want to spin up a Zapier flow or tag every URL.

A few operational notes

Stripe doesn’t send you a notification when a payment link expires. If you set a date, add a calendar reminder to check performance and decide whether to extend, replace, or retire the offer.

Expired links return a generic Stripe error page. You can’t customize the message, so if you want to redirect visitors somewhere else—an updated offer, a waitlist, an apology—you’ll need to remove the old link from circulation and replace it with a redirect or new page. Don’t rely on the Stripe expiration page to do marketing work for you.

Finally, expiration applies to the link, not the product. If someone starts a checkout session before expiration and completes it five minutes after, Stripe still processes the payment. The cutoff happens at the moment someone clicks, not when they submit payment details.

Set expiration when the offer has a real deadline. Skip it when the product is evergreen. And if you’re testing, use expiration to force a review date instead of letting old links quietly underperform.

Want more tactical breakdowns like this? Subscribe to One Two Three Send—one article every day, no fluff, no filler.