3
3 Comments

97 days building an automated GitHub-idea newsletter — 72 subscribers, 0 revenue, here's everything I learned

Back in early May I started GitPulse Weekly — a pipeline
that scans 500+ trending GitHub repos weekly and turns
open-source traction into commercialization ideas,
delivered every Saturday.

97 days later: 14 issues sent, zero missed Saturdays,
72 subscribers, 0 paying customers.

Here's the honest breakdown.

What I built

A fully automated pipeline — GitHub API scanning across
5 languages, 3 detection rules (fast-rising repos,
clustered themes, under-productized tools), AI enrichment
with a 3-layer fallback chain so it never silently fails,
and permanent deduplication so no idea repeats.

Started as plain text emails through Gmail. Ended as a
branded HTML email + a 13-page designed PDF report for
Pro subscribers, complete with execution roadmaps,
validation strategies, and a scoring system.

What actually worked

Personal outreach. Every single subscriber who mattered -
replies, feedback, engagement came from a direct message,
not a community post. Cold posting in Discord/Reddit/IH
brought almost nothing. Warm, one-on-one outreach brought
everything.

Showing up every week. Even with zero revenue, sending
something real every Saturday for 14 weeks straight built
more trust than any single feature I shipped.

Growth velocity over raw stars. "Gained 50,000 stars in
11 days" is a completely different signal than "50,000
stars total." This became the product's real differentiator.

What didn't work and what people told me directly

Three separate people, unprompted, told me some version
of the same thing: "I don't believe idea-givers without
proof." Not implied. Said outright, more than once.

That's the real blocker. Not pricing (someone outside my
target audience told me ₹299/month "sounds reasonable as
an outside judge"). Not the format. Trust.

I responded by adding Market Proof (show a real company
that already validated the gap) and Validation Strategy
(how to test demand before building) to every idea. Whether
that's enough, I don't know yet — too early to tell.

The mistakes

  • Spent too long polishing the pipeline before doing enough
    outreach. The engine was solid by day 30. Distribution
    didn't get serious focus until much later.
  • Sent from a personal Gmail for way too long — landed in
    spam for a real chunk of subscribers before I diagnosed it
    and moved to a proper email service.
  • Chased Discord servers and community posts that had almost
    zero conversion, when the data was telling me the whole
    time that personal outreach was the only thing working.

Where it stands

Real infrastructure. A product I'm not embarrassed by.
Zero revenue. That's the honest scoreboard at day 97.

Not stopping — but the next phase isn't "add another feature."
It's finding the 15-20 people who are actually my target
audience and giving them something worth paying for,
directly, one at a time. Same thing that worked from day one,
just more deliberate about it.

If you're building something similar, or have thoughts on
the trust problem — genuinely want to hear them.

on August 10, 2026
  1. 1

    Love the honest breakdown. The real insight is that the bottleneck is trust, not another feature.
    The growth-velocity signal sounds genuinely useful—now I’d focus on 15–20 ideal users and learn exactly what proof would make them pay. 14 issues without missing a week is strong execution.

  2. 1

    The personal outreach result is interesting. 72 subscribers from 14 issues with almost all meaningful engagement coming through direct conversations says a lot about how different the two acquisition channels are. Curious what happens when you double down on that instead of adding more features.

  3. 1

    Milestones hit (of my journey):

    Day ~5: first 12 subscribers via personal outreach
    Day ~14: first Vistanova/Peter engagement — first "real company" signal
    Day ~30: 50 subscribers
    Day ~45: caught claw-code (a fake/art repo) before it went to 50 subscribers — a real save
    Day ~50: growth velocity feature shipped after weeks of you pushing me to prioritize it
    Day ~55: Razorpay + Gumroad both live
    Day ~65: found and fixed the "only 3 of 5 languages" bug — the root cause of repeated ideas
    Day ~70: first Pro trial sent free to all subscribers
    Day ~80: switched from Gmail to Brevo after diagnosing the spam problem
    Day ~90: full HTML redesign + PDF report shipped — the biggest single upgrade in the whole project
    Day 97: 14 issues sent, zero missed Saturdays, 72 subscribers, 0 paying customers

Trending on Indie Hackers
I built an AI that finds the right product for your customers User Avatar 45 comments I built a tool to find people already talking about problems your product solves User Avatar 34 comments The easiest version of generation history was probably the least useful one User Avatar 32 comments What 100B+ Claude tokens actually look like inside a tiny company User Avatar 26 comments 4 months to go. Chrome extension live. Web search integrated. 4 users. $0 revenue. Still here. User Avatar 18 comments Two-way is not the same as symmetric User Avatar 15 comments