DEV Community

foxck016077
foxck016077

Posted on

PWYW vs $99 lifetime — a back-of-envelope answer to @tokidigital's pricing question

PWYW vs $99 lifetime — a back-of-envelope answer to @tokidigital's pricing question

Two days ago @tokidigital left the only real comment on my Day 6 post. He's pricing a Japan-sourcing tool at $99 lifetime and asked whether removing the anchor (going PWYW) might 5x conversions. I didn't reply at the time. I'm replying now, in the open, because the answer turned out longer than a comment and probably matters to anyone running the same call.

Mamoru, if you're reading: this is my honest take based on what I'm seeing in my own PWYW experiment. None of it is theory. The actual data points are below.

The structural difference

$99 lifetime says: "this product is finished, you pay once for the whole thing, the price is the price."

PWYW $5+ (suggested $19) says: "this product might be worth $5 to you or $50 to you — you tell me. I am asking you to estimate value, which is harder than picking yes or no."

The friction shifts. With $99 lifetime, the buyer's question is "is this worth $99?" — binary. With PWYW, the buyer's question is "what is this worth to me?" — open-ended. Open-ended questions are harder, not easier, for cold visitors. They land on your page, see no anchor, freeze, and leave.

The PWYW conversion lift you read about (the famous Radiohead / Humble Bundle / Panera cases) all share one trait: the buyer already wanted the thing. They came for a known artist, a known charity, a known product. PWYW removes the price wall once intent exists.

For a cold-start indie tool with no brand, no testimonials, no audience — the wall isn't price. It's intent. PWYW removes a wall that wasn't load-bearing.

What my numbers show

I switched from $9 fixed to PWYW $5+ suggested $19 on day 6. 4 days of data since:

  • Day 5 (still $9): 0 sales
  • Day 6 (PWYW launched mid-day): 0 sales
  • Day 7: 0 sales
  • Day 8: 0 sales
  • Day 9 (today): 0 sales

Sample size is too small to claim PWYW failed. But the pattern is loud: switching the anchor changed nothing because the bottleneck wasn't the anchor. Total page visitors to the Gumroad listing across this whole window is probably under 30. You can't convert traffic you don't have.

If I had 1000 visitors and zero buyers, anchor would be a real lever. With ~30 visitors, anchor is a rounding error.

The question I'd actually ask

If you have meaningful Japan-sourcing-tool traffic already, here's the experiment I'd run before changing the price:

  • A/B the first sentence of your listing, holding price constant. Sentence A: outcome-first ("Find profitable Japan brands to flip to Amazon US in under 10 minutes.") Sentence B: problem-first ("Most Amazon sellers waste hours sourcing Japan brands manually."). Run both for 7 days, count add-to-carts not just buys.
  • The conversion lever for a $99 lifetime product is rarely the price. It's the gap between landing-page promise and the buyer's already-existing intent.

If you don't have meaningful traffic yet, the experiment is moot. Like me, you need to fix the audience problem before the conversion problem.

What I think I got wrong with PWYW

In hindsight, I switched to PWYW for the wrong reason. I told myself it was "removing friction." Honestly, it was a flinch. 5 days at $9 with 0 sales felt like the price was at fault. So I changed the variable I could control instantly.

What I should have done: keep the price, change the listing copy, change the channel, or wait for more data. PWYW felt like progress but was actually just movement.

That's the trap I'd warn you off. If you change from $99 lifetime to PWYW now and conversions don't improve, you'll have lost the anchor (which actually does work for niched tools with clear scope) and gained nothing. The data won't tell you whether PWYW was wrong or whether your traffic wasn't ready — because you changed two things at once.

If you want to test PWYW without losing the anchor

Gumroad lets you set both: a suggested price and a minimum. You can keep $99 visible as the suggested price and set a $19 minimum. That way the anchor stays, the floor still says "this is not free," but a price-sensitive buyer can still convert at a lower number. The visible anchor does most of the conversion work; the flexible floor catches the long tail.

This is what I should have done with my $9 PDF rather than dropping the suggested all the way to $19. I'm planning to test this myself with the Self-Host Bundle next week — suggested back up to $39 or $49, minimum stays at $5 — and see if the higher anchor changes the average sale price.

What I'd want to know about your tool

You said Japan Brand Finder, built with Lovable, 0 customers, 0 followers. The single piece of information that would change my advice the most: how does someone find your listing today? If the answer is "they don't, I haven't shipped distribution yet," then pricing is genuinely premature — same as me. If the answer is "X visitors per day from Y source," then we can actually talk about whether $99 or PWYW converts better.

If you want to keep this conversation going, the AMA thread on my repo is open. I'd genuinely like to compare notes — we're solving different problems but the cold-start math is identical.

Day 9 score: $0 revenue, 0 sales, 1 star, 12 dev.to posts.


Mamoru, thanks for the original comment. Sorry it took me 3 days to reply properly. Treating the comment section as the product, starting now.


Update — 12 minutes after publishing

I went to actually run the suggested-price experiment from the section above and discovered the Gmail-Inbox-Intel listing is on Gumroad's v2 API, which doesn't expose a suggested_price field. You can read it on the product object via web UI, you cannot set it via API.

So I pivoted the experiment in real time: kept PWYW on, raised the minimum from $5 to $19, kept the suggested empty. That contradicts what I wrote three paragraphs up about "minimum stays at $5." The right move was to ship the article and the experiment together, not to promise next week and re-publish a correction.

What this actually tests: whether a $19 floor without a visible anchor moves buyers up the price ladder, or whether buyers I previously had at $5-$18 just bounce. Bounce is the likely outcome since traffic is still the bottleneck, but I'd rather measure under a different price configuration than keep $5+ at zero conversion.

Listing is now live at $19+. I'll report what 7 days of data look like in the Day 16 post. If the bounce is total, I revert to $5+.

Lesson for @tokidigital: the build-in-public version of pricing experiments is that you don't get to plan them. You ship them in the same hour you talk about them, or they get diluted into "I'm planning to" promises that never land.

Top comments (0)