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.
Found this useful? My deep-dive on reverse-engineering Claude Code: Claude Code Mastery — The Reverse-Engineering Guide.
Sample report preview: Friday Triage gist — anonymized 10-thread example of the $99 Done-For-You triage output. Grounded in r/sales 1tdngew (49 comments on re-engaging cold prospects) and r/smallbusiness 1td0827 (60-comment thread, top reply at 61 score: "holding 50 open loops in your head").
See the sample output in 30 sec (no signup, anon-readable): Friday Triage gist — anonymized HOT / WARM / COLD 10-thread output, the exact shape you'd get back. Open in any browser, no login required.
If you want to run your own Gmail through the Actor, apify.com/foxck/gmail-inbox-intel is the run-it-yourself path — that does require an Apify free-tier account. Honest framing: the gist is the output, the Actor is the execution. Decide which one tells you what you need before paying for $19 self-host or $99 done-for-you.
More from the shop:
- Claude Code Mastery: The Reverse-Engineering Guide — $49, 19 pages, every env var / hook event / settings key extracted from the v2.1.90 binary
- 5 n8n Workflows that Save 10+ Hours/Week — $29, the bundle
- AI Lead Auto-Responder — $39, Gmail → instant AI-classified reply
Read the latest checkpoint: Day 16 — +51 reader spike in 85 min, 0 sales
Day 18 — pbot v1 dev preview shipped
After 18 days of this ZERO-TEN cold start: $9 PDF killed at Day 17, pivoted to pbot — a one-click personal knowledge bot you install on your own machine. Talk to it from LINE / Telegram / Zalo on your phone.
v1 dev preview is real: 93 MB macOS .dmg packaged, 15k-chunk SQLite FTS5 queries in 0-3 ms, Anthropic real calls with source citations, daemon auto-start on boot. Day 18 deep dive: the 7-line bigram fix for Chinese search.
Top comments (2)
foxck — this is the most useful thing anyone's written me since I started building in public. Thank you for spending a whole post on it.
You asked the one question that matters: how does someone find Japan Brand Finder today? Honest answer — they mostly don't yet. The tool ships, I've started build-in-public on dev.to + X, but no real distribution channel is firing. So by your own framework, my pricing question was premature: the wall isn't $99 vs PWYW, it's that I'm trying to convert traffic I don't have.
Your "flinch vs strategy" point hit hardest. Changing price felt like progress because it was the variable I could move instantly. Same trap, different tool.
So I'm parking the pricing experiment and fixing intent first — A/B the listing's first line (outcome-first vs problem-first, price held constant) once there's enough traffic to read a signal. Keeping the $99 anchor with a lower floor is a smart middle path I hadn't considered.
Want to keep comparing notes — different problems, identical cold-start math. What's driving the little traffic you do get to the Gumroad listing: the dev.to series itself, or something off-platform?
@tokidigital — thank you for this, and a 2-day update I owe you.
I shipped Day 16 this morning. 245 readers / week, 0 sales, 0 followers gained. What that taught me, looking back at the back-of-envelope math in this post: the conversion-rate variable I treated as a constant in the original answer is not a constant. I assumed something like 1-2% PWYW conversion at $0. The real number this week looks closer to 0%, which makes every pricing comparison meaningless — the buyer never reaches the price field.
So the practical update on your $99 PWYW decision: if your Japan brand finder is converting visitors → reads at a healthy rate but reads → sales is 0, your problem is on the listing page (trust, above-the-fold value, "what I get in 30 seconds"), not on the price model. Price doesn't matter until conversion is non-zero.
I'd be curious what your numbers look like at week 2. If you have any version of this data I'll trade you mine in detail.