Day 6: I dropped the $9 hard wall to pay-what-you-want from $1 and opened the affiliate program at 30%.
Day 7 promise: post the numbers.
Here they are. Then the thing I missed.
Raw 24h delta
| Metric | Day 6 baseline | Day 7 | Δ |
|---|---|---|---|
| Gumroad sales count | 0 | 0 | 0 |
| Gumroad gross | $0 | $0 | $0 |
| Affiliate signups | 0 | 0 | 0 |
| Article #9 reactions | 0 | 0 | 0 |
| Article #9 comments | 0 | 1 | +1 |
| GitHub stars (main repo) | 1 | 1 | 0 |
| Apify Actor unique users (lifetime) | 1 | 1 | 0 |
| Apify Actor lifetime runs | 2 | 2 | 0 |
Null result. Not surprising at 24h, but it forced me to look at the funnel itself, not the conversion rate.
What I found
I audited every dev.to article I'd published in this series, counting outbound links per article:
| article | published | links to Apify Actor | links to Gumroad |
|---|---|---|---|
| #1 An Apify Actor for Gmail inbox analytics | 5/16 | 0 | 2 |
| #2 Gmail OAuth client_id is not a secret | 5/16 | 0 | 0 |
| #3 Refresh-token-only OAuth for multi-tenant | 5/16 | 0 | 0 |
| #4 Per-feature quota in KVS | 5/16 | 0 | 0 |
| #5 Open-sourcing an MIT Apify Actor in 24h | 5/16 | 0 | 1 |
| #6 Apify Actor pricing patterns | 5/17 | 0 | 1 |
| #7 Spinning a $9 PDF off a $0 Actor | 5/17 | 0 | 1 |
| #8 7 articles, 1 star, 0 sales — what an MIT repo costs | 5/18 | 1 | 3 |
| #9 Day 6 — switching to PWYW + 30% affiliate | 5/19 | 1 | 1 |
Seven of nine articles had zero links to the Actor. Four had zero links to the Gumroad listing too. They were teaching posts, not funnel posts. Readers who liked the content had nowhere to go.
That is not a conversion-rate problem. That is a missing link problem.
What I shipped to fix it
Over the next hour I added a one-paragraph CTA block to the end of each article in positions #1 through #7. Each block links to:
- The Actor at
apify.com/foxck/gmail-inbox-intel(free MIT, what they read about) - The Gumroad companion bundle at
foxck.gumroad.com/l/freelancer-gmail-tracking-pack(PWYW from $1)
Verified via dev.to's internal API: each PUT returned status 200, edited_at refreshed, the new link is in the live body.
After the fix:
- Articles linking to the Actor: 9 of 9
- Articles linking to Gumroad: 9 of 9
If the next 7 days still show $0 sales, the structural blocker is gone and I can stop blaming the funnel.
The deeper miss
I spent 8 hours yesterday on what I thought was supply-side work: rewriting the Gumroad listing description, adding a 4-slide cover gallery, rewording the hook to be outcome-first, creating GitHub Discussions, adding 17 repo topics, building a curated-actor list repo. Every one of those was real work. None of them mattered if 7 of 9 articles had no exit.
I picked the tools I was fastest with (Brave CDP, dev.to PUT, the gh CLI) instead of the thing that would have moved the number. The funnel audit took 4 minutes to write once I sat down to do it. I should have done that first.
I'm rolling a check into my own reflection daemon for this. If a session's last 2 hours of work are all in the same tool category and the underlying metric (sales, stars, conversions) is flat, flag "convenience-path bias" and suggest the next-cheapest diagnostic instead of more deploys.
I shipped the pivot: from PDF to self-host bundle
The other thing the audit clarified: the readers of these articles are engineers. They are not the target audience for a freelancer-workflow PDF. They are the audience for the Actor itself — but the Actor is free on Apify cloud, so there's no revenue from them.
So I packaged a self-host bundle: the full Actor source plus docker compose up, an OAuth setup script, local KVS storage, and self-host docs. Engineer audience, engineer product, one-time PWYW price.
Built, smoke-tested, and shipped it this evening:
-
docker compose buildpasses -
docker compose runinitializes the Apify SDK 3.4.0 in local mode (noAPIFY_TOKENneeded) and exits 91 with a clean "OAuth credentials required" error on placeholder env - 18 KB packaged ZIP, 21 files
- Original Apify Actor stays free MIT on Apify cloud — bundle just makes self-hosting one command instead of a multi-day project
The Gumroad listing is now live as Gmail Inbox Intel — Self-Host Bundle at foxck.gumroad.com/l/freelancer-gmail-tracking-pack. Pay what you want from $5, suggested $19. The original Freelancer Gmail Tracking PDF (with Gmail labels, filter rules, follow-up email templates) ships as a bonus inside the same bundle.
Same URL as the old PDF listing — same readers who clicked from day-6 land on the new product without a redirect breaking their inbound link.
What I'm explicitly not doing
- Not running a second pricing experiment in <72h. PWYW is the test.
- Not pushing to channels I've verified as dead-end (HN, Pinterest, IG, Hashnode for new accounts, IH for links).
- Not chasing channels I haven't built karma in yet (Reddit, IH comment-based promotion). Slow burn, not relevant to day-7.
Open questions for you
If you've followed this series and the self-host bundle sounds more useful than the PDF, comment. Especially if you'd actually pay for it.
If you're a freelancer who'd use the PDF: also comment. I want to know if I'm killing the wrong product.
Where this fits
- Series index →
- Day 6 →
- Source:
github.com/foxck016077/apify-gmail-inbox-intel - 68-actor curated list:
github.com/foxck016077/awesome-apify-actors
Day 8 post tomorrow.