I shipped a small MIT-licensed Apify Actor four days ago. Open-source repo, public Store listing, FUNDING.yml, a Gumroad companion PDF, seven dev.to write-ups across OAuth design / pricing patterns / build-log narrative. Standard "launch on dev.to" playbook from every indie-hacker thread.
Here's what the cold-start funnel actually did in 96 hours, with the numbers exposed for anyone running the same checklist.
The pipeline I built
- GitHub repo (MIT): a Gmail inbox-analytics Actor — thread search, reply tracking, SLA breach detection, unread digests. Refresh-token-only OAuth, async per-feature router.
- Apify Store listing: public, isPublic=true, categories AUTOMATION / DEVELOPER_TOOLS, source code visible, free tier.
- 7 dev.to articles spanning a build log, OAuth design notes, KVS quota pattern, pricing patterns, multi-tenant client_id design, async router, and a build-log of spinning out a $9 manual companion PDF.
- Gumroad listing for the $9 PDF companion (12 pages + 30 labels + 12 filters + 5 follow-up templates + Apps Script).
- README cross-links pointing the GitHub reader at the Gumroad page.
The numbers at hour 96
| Channel | Result |
|---|---|
| GitHub stars | 1 (organic — a user named kuerdy starred on day 4) |
| GitHub forks | 0 |
| GitHub real-user issues | 0 (6 dependabot PRs, no human issue) |
| Apify Store total runs | 2 (both my own dry-runs) |
| Apify Store 7-day users | 0 |
| Apify Store bookmarks | 0 |
| Apify Store reviews | 0 |
| dev.to articles published | 7 |
| dev.to total reactions across 7 articles | 1 |
| dev.to comments received | 0 |
| Hacker News submission | 1 point, then dead: True (mod-flagged) |
| Gumroad sales (all-time) | 0 |
| Gumroad revenue (all-time) | $0.00 |
What the launch playbooks oversell
- "Just ship and the open-source community shows up." They don't, not for niche utility actors. A dependabot PR is not a signal. A single organic star at day 4 is the actual baseline you should expect from a quiet shipped MVP.
-
"Write a dev.to launch post." A 5-minute single article gets buried in a feed of 800 daily posts. 7 articles spread across 4 days got 1 cumulative reaction. The article that mentions a paid product in the title (
$9 PDF) got the only reaction. - "Cross-link everything." Cross-linking is correct but the conversion math is unforgiving — even with a 7-article portfolio, you are talking about single-digit profile clicks, not the implied 10x audience compounding.
What I'd change if I were the past-me at hour 0
Submit to Hacker News only once, with the right URL. I submitted the dev.to write-up; it went to 1 point and then died. The link should have been the GitHub repo with a story-shaped README, not the dev.to article. dev.to URLs on HN have a worse base-rate than direct GitHub links.
Treat dev.to as a comment platform, not a publishing platform, for the first 14 days. A thoughtful comment on someone else's
#apifyor#automationpost in the same week as your launch reaches more relevant eyes than a 7th article on your own profile.Don't strip the contextual CTAs out of your own build-log posts. I had a phase where I scrubbed every Gumroad link out of every article to avoid looking promotional. The result is an article literally titled "$9 PDF off a $0 actor" with zero way for the reader to buy the $9 PDF. The corrective is one contextual link, not seven banner CTAs.
Apify Store discoverability does not exist at this volume. With 0 reviews, 0 bookmarks, and a Store search index that prioritizes incumbents, the Store page is a landing page reached only by people you sent there. Treat it as a landing page, not a discovery channel.
The Gumroad companion does not need a separate marketing push. It is a footnote in the actor's README. People who want a self-host avoidance path will find it from there; people who do not, will not pay $9 because of a banner.
The funnel shape after one corrective pass
Two hours after writing this, I had:
- Restored a single contextual Gumroad CTA in two of seven articles (the two that are explicitly about the paid companion path — anywhere else, the CTA reads as stuffing).
- Posted four thoughtful comments on
#apifyand#automationposts from other actor builders in the last 48 hours, on questions I genuinely wanted answers to. - Set up a 5-minute Gumroad sale watcher so the next 0→1 sale event hits a Telegram push instead of being noticed days later.
If the next 96 hours produce more than 1 reaction, 1 star, and 0 sales, I'll post the updated table. If they don't, I'll post the updated table.
Honest disclosure
- Actor: foxck/gmail-inbox-intel on Apify (free, MIT, open-source repo at foxck016077/apify-gmail-inbox-intel).
- Manual companion: Freelancer Gmail Client Tracking Pack — $9 on Gumroad. Refund link on the listing if it doesn't help.
- Discussion forum: also live on the repo at GitHub Discussion #10 for anyone preferring that surface to comment threads.
- Discussion question: if you have shipped an MIT open-source utility actor or library that pairs with a paid companion, which of the five corrections above changed your conversion rate the most? I'd rather hear the one that backfired than the one that worked.
Top comments (0)