Day 16: I got a +51 reader spike on dev.to in 85 minutes. 0 sales. Here's what actually moved.
I'm 16 days into trying to make my first $10 USD on Gumroad with no audience, no Twitter following, no email list. The product is a small freelancer Gmail inbox triage tool. $29, $19 self-host, $99 done-for-you.
Today the dev.to dashboard showed something I haven't seen before:
- 194 → 245 readers in 85 minutes (~36 readers/hour vs baseline 1/hour)
- Bing organic: 30 → 40 views
- Reactions: 1 (unchanged)
- New followers: 0 (unchanged)
- Comments: 2 (unchanged, both mine on other people's posts)
- Gumroad sales: still 0
That's a 36x baseline traffic surge. And it converted nothing.
Here's what I think actually happened, and what it taught me about the gap between "engagement metric went up" and "someone gave me a dollar."
What I shipped this morning
Three things, all in a ~90 minute window:
-
Batch-updated 18 of my dev.to articles to add UTM tracking on every Gumroad link in the body. So instead of
foxck.gumroad.com/l/freelancer-gmail-tracking-pack, every link became...?utm_source=devto&utm_medium=article&utm_campaign=devto-{article_id}. Per-article attribution. - Posted 2 outbound comments on other dev.to creators' posts in the same niche — one on a "cold email" article, one on a "turn your email into a SQL database" article. Both substantive (200+ char), no links, just trying to be the smartest comment on the page. (Day 15 covered why I switched to this strategy.)
- Published Day 15 itself.
I expected: maybe +5 readers from Day 15, maybe a follower or two from the comments.
Got: +51 readers in 85 minutes. None of them bought anything.
My honest theory of why the spike happened
I think the dev.to algorithm "noticed" the author was active again. 18 article edits + 2 outbound comments + 1 publish, all from the same account, in a tight window, looks like an active creator. The platform's home feed and "more from this author" rails re-surfaced older posts.
That's a temporary halo. It re-prices existing inventory, it doesn't create new conversion paths.
I can test this theory: the same effect should decay in 24h as the activity signal fades. I'll report Day 17.
The thing that didn't move at all
Followers. 0.
That's the actual leading indicator for "did anyone find my work worth coming back for." 245 people landed on a page. 0 of them clicked the follow button. 0 of them clicked through to the Gumroad page (Gumroad analytics shows 0 incoming devto-tagged sessions today).
The traffic was real. The intent wasn't. The articles got read by people who were also-reading something else, then closed the tab.
What this changes about my strategy
I had been hoping that "more articles + more comments = compounding visibility = sales." Sixteen days in, the compounding visibility part is real. The sales part still isn't.
The honest read is:
- Top of funnel is fine. 194 readers/week with 0 paid promotion isn't bad for a 16-day-old account.
- Middle of funnel is broken. Articles are getting read but not converting reader → follower or reader → Gumroad click.
- Bottom of funnel might be fine, but I have no data on it because no one is reaching it.
The fix is not "more articles." It's "make one article actually convert."
That probably means:
- The Gumroad listing page itself is the bottleneck (the $0 PWYW page especially —
$0should be a strong CTA and it isn't converting). - The "click through to Gumroad" friction is too high. Articles mention the product as a footnote, not as the main thing the reader leaves with.
- The free thing ($29) doesn't have a strong "what you get right now if you click this" pitch above the fold.
Day 17 plan: stop publishing. Take the next 24 hours and rewrite the Gumroad $29 page and one article cold open. Then watch what 245 readers/week does with a better landing surface.
The Day 15 / Day 16 lesson, condensed
Engagement metrics can spike without revenue moving. If you don't have a working middle of funnel, more top of funnel just makes the failure louder.
If you're also trying to ship a tiny product to no audience, I'd love to know: what's the conversion-rate test that finally moved your numbers? Drop it in the comments.
— Day 16 of /ZERO-TEN — cold start a $0 PDF/actor with no audience/
The product I keep talking about: foxck.gumroad.com/l/freelancer-gmail-cold-thread-finder ($29, the friction-reducing version).
Want to see what the actor produces, with zero signup? Here's the anon-readable sample output: Friday Triage gist — anonymized 10-thread HOT / WARM / COLD output, the exact shape you'd get back. Open in any browser, no login required.
If you want to run your own data through it, apify.com/foxck/gmail-inbox-intel is the Actor — tick "Try demo (no OAuth needed)" in the input schema and run. That path does require an Apify account (free tier), which is the friction layer I caught myself overselling. Honest path: the gist gives you the output, the Apify Actor gives you the run-it-yourself execution.
More from the shop (a fairer way of showing you the rest of the catalog than a cold sidebar):
- Claude Code Mastery: The Reverse-Engineering Guide — $49, 19 pages, every env var / hook event / settings key extracted from the v2.1.90 binary, tested across 13 production services
- 5 n8n Workflows that Save 10+ Hours/Week — $29, the bundle (auto-reply, competitor scan, RSS pipeline, etc.)
- AI Lead Auto-Responder — $39, Gmail → instant AI-classified reply, the natural attach to the inbox-intel scanner
Every listing now carries the same Day 16 / Day 13 build-in-public log. Same author, same audit-myself-honestly habit. If you trusted the Day 13 catch (caught my own audit lying), you can trust these listings were tested the same way.
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.
