7
7 Comments

I just launched v2 of my side project Newsletter Spy

Hey,

I finally pulled the trigger. Newsletter Spy 2.0 is live on Product Hunt right now. Here's the link.

Even though I've launched 10+ projects by now, I'm still not immune to the fear of launching.

The project was ready three weeks ago.

But I kept postponing the launch for no good reason, really. I added all kinds of features only to remove them again because they were confusing and added no value. I was waiting for early user feedback that never came. I invented all kinds of excuses why it might make sense to wait a bit longer.

Luckily, two days ago I was on a call with Ty Frankel and when I told him about Newsletter Spy he bought it on the spot. Even though I offered him free access, he insisted on paying for it and told me that this is incredibly useful for him as he's about to start a paid newsletter himself.

This reminded me that Newsletter Spy can be genuinely useful to some people, and it's really stupid to not share it with others.

It's definitely not perfect yet. I fixed some very embarrassing bugs just this morning. But it's usable.

I'm already using it myself to find newsletters I can book ad slots in.

Pete Davies is using it to find Substack users with a podcast that he can invite to his new platform Jam.ai.

Ty Frankel is using it to find partners for his new newsletter.

So the product is definitely already providing value and I can always improve the product later based on feedback by paying users, as I always do.

Anyway, enough of my self-doubts. Let's talk about Newsletter Spy itself.

I launched the first version of Newsletter Spy 9 months ago. At the time, I was inspired by a tweet by Mike Rubini who handed the problem over to me. I finished the project over the course of a weekend. So it was literally just a weekend project.

But it got far more attention than I expected and was used by some of my favorite writers and even researchers from Harvard.

Unfortunately, quickly after the launch, Substack changed their website in a way that made it impossible to fetch subscriber counts. As a result, I was no longer able to provide updates and the project fell into hibernation.

To my surprise, people kept buying access to Newsletter Spy even though I added a big warning that the dataset was outdated and no longer updated. Also at least once a week someone would reach out to me and ask for an update.

Thanks to these conversations, I quickly learned that Newsletter Spy could be useful to many people even without exact subscriber counts. So I decided to revive the project.

Here's what's new:

  • The Substack database now contains 50,000+ newsletters. Instead of subscriber counts, it now contains metrics like the category rank and the average number of reactions, which usually give a good idea how big a given newsletter's audience is. Also, in contrast to v1, the database is now updated daily.
  • In addition to the Substack database, there's now also a Revue database. This database contains exact subscriber counts for all newsletters that share this number publicly.
  • Finally, a third database contains information on newsletters from other major email service providers like ConvertKit, MailChimp, etc. I started experimenting with a machine learning model that predicts the subscriber count, but the results are still meh and should be taken with a grain of salt. However, the database also contains columns like "Fame" (how well known is a given newsletter), "Buzz" (how much are people talking about the newsletter online), "Traffic", Traffic Change" (growing, stagnating, declining) which are more accurate and make it possible to estimate a newsletter's audience size.

If you want to check it out, you can do so here.

And of course, if you have any comments, questions or feedback, I’d love to hear it!

Best,

Jakob

posted to Icon for group Product Launch
Product Launch
on September 2, 2021
  1. 2

    Gratulations to the launch!
    As part of my "Free backlinks for IndieHackers" initiative I've [turned your set of documents into a relational database] (https://database-modelling.com/exercise/newsletter-spy). You can reuse it, if you ever want to turn your document templates into a SaaS app :-)

  2. 2

    Bought (and also upvoted) this yesterday, massive list of companies.

  3. 2

    Great business! I'll definetively use for my still small newsletter :)

  4. 2

    Hi, can you please share how many emails in the list ?

  5. 1

    This is pretty neat. Is my newsletter on the list? (the emails come from @johncrestani dot com). I have a mailing list of 500k people, and am using ActiveCampaign. I could use something like this in prospecting for new partnership/promotion deals for my products, but am concerned because my audience is mostly using ESPs like infusionsoft, ontraport, activecampaign, sendgrid, and others.

    1. 1

      Hey John, I just checked and your newsletter is currently not in the database. i think the reason is that there's no signup form on your website (at least when I checked your website today).

      But I'll expand the database over time and add ESPs like infusionsoft, ontraport, activecampaign, sendgrid

  6. 1

    Fun fact: v1 of Newsletter Spy was featured in a recent Indie Hackers podcast 😊

Trending on Indie Hackers
I'm a lawyer who launched an AI contract tool on Product Hunt today — here's what building it as a non-technical founder actually felt like User Avatar 151 comments Never hire an SEO Agency for your Saas Startup User Avatar 81 comments A simple way to keep AI automations from making bad decisions User Avatar 65 comments “This contract looked normal - but could cost millions” User Avatar 54 comments 👉 The most expensive contract mistakes don’t feel risky User Avatar 41 comments We automated our business vetting with OpenClaw User Avatar 34 comments