2
1 Comment

Newsletters are everywhere - but inboxes are not built for them

One thing that became very obvious while building Newsletter Reader by Bilig (App Store):

The newsletter market doesn’t really have a discovery problem anymore.
It has an engagement problem.

People already subscribe to a huge number of high-quality newsletters across AI, startups, investing and tech. The issue is that inboxes are optimised for processing communication quickly, not for consistently consuming long-form content.

Over time, unread issues pile up and engagement drops, even when the content itself is genuinely valuable.

And that’s the core thesis behind Bilig. If newsletters are increasingly becoming a primary information source for professionals, they probably need a dedicated consumption layer separate from email.

Still early, but interesting to see how quickly people resonate with the problem once framed that way.

posted toAvatar for product Bilig
Bilig
  1. 1

    The positioning is strong because you are not really selling “another newsletter app.” You are pointing at a bigger behaviour shift: newsletters have become a serious information source, but email is still designed for communication, not intentional reading.

    That distinction is probably the sharpest angle for Bilig. The product should feel less like inbox cleanup and more like a dedicated knowledge layer for people who already depend on newsletters for AI, startups, investing, and tech.

    One thing I’d pressure-test is the brand frame. Bilig is short and clean, but for a product built around attention, reading habits, summaries, highlights, and professional information consumption, the name may need to carry the workflow value faster for a cold user.

    Xevoa .com would fit this broader direction better if the product becomes a serious reading and knowledge workflow layer, not just a newsletter reader. It keeps the product on your side: same idea, same user problem, but with a name that feels more scalable if you expand into saved insights, AI summaries, notes, research feeds, or team knowledge later.

    Since you are already repeating the same thesis across multiple posts, this is probably the right time to tighten the brand before more users and App Store memory lock around the current frame.