I rebuilt DriftNote’s website and added podcast following 🎧

Quick DriftNote update 🚀

Over the last few days I’ve been working on two things: a cleaner website design and a new podcast follow feature.

The website update was needed because the first version explained the product, but not clearly enough. DriftNote sits between two audiences: podcast listeners and podcast creators. That made the messaging a bit messy at first.

The new site makes the split much clearer.

🎧 Listeners can summarise episodes, save key insights, ask questions about episodes, follow their favourite podcasts, and revisit ideas later.

🎙️ Creators can generate transcripts, show notes, key quotes, timestamps, episode titles, and repurposed written content from their episodes.

The bigger product update is the follow feature.

Instead of only using DriftNote when you already have a specific episode link, users can now follow their favourite podcasts and keep track of new episodes more easily.

This matters because podcast discovery and retention are still weirdly broken. People subscribe to shows, save episodes, and then still forget to listen or lose track of the best ideas.

For creators, this opens up a more interesting direction too. If listeners are following podcasts inside DriftNote, the product becomes more than a one-off summariser. It starts becoming a place where episodes are easier to revisit, search, and actually use after publishing.

The lesson for me has been simple: a useful AI feature is good, but a repeatable workflow is better.

The first version of DriftNote helped people summarise a podcast. This version is starting to feel more like a podcast knowledge layer 🧠

Still early, still building, but the product is getting clearer.

Building at driftnote.net

Curious for other founders: what small feature made your product feel more “real”?