Reddit + Notion: the buyer-intent thread tracker that doesn't rot

Most founder Notion workspaces I've seen look like a graveyard of good intentions. There's a page called "Reddit Leads 2025" that was last touched in April. There are five columns, three of which nobody can define. Someone added an emoji.

A working buyer-intent tracker is boring on purpose. It has four or five fields, one owner per row, and a status that moves. If you can't glance at it on a Tuesday morning and know which three threads need a reply today, it's decorated stationery, which is roughly how Notion skeptics on r/Notion describe their own setups once the novelty wears off.

Here's the workflow I actually run, and the one I set up for every founder I help with Reddit distribution.

What the tracker needs to do

A buyer-intent thread is any Reddit post where someone is either (a) asking for a tool recommendation you fit, (b) complaining about a competitor, or (c) describing a workflow problem your product solves. Those threads have a shelf life of roughly 24 to 72 hours before the OP stops reading replies.

So the tracker has exactly three jobs:

1. Capture the thread the moment it appears, with enough context that you don't have to re-read it later.
2. Assign one human to reply.
3. Record what happened so you can learn from the hit rate.

That's it. No vision boards, no quarterly OKRs linked to the thread database, no nested sub-pages for "content ideas inspired by this thread." Every extra field is a reason the system rots.

The Notion database schema

Create one database. Call it Reddit Intent. Give it these properties and no others:

Property	Type	Purpose
Thread title	Title	The post title, verbatim
URL	URL	Direct link to the Reddit thread
Subreddit	Select	r/SaaS, r/startups, etc.
Signal type	Select	asking, complaining, describing
Owner	Person	One human, not a team
Status	Status	New, Replying, Replied, Dead
Captured at	Created time	Automatic
Outcome notes	Text	One sentence after you reply

That's eight fields. If someone on your team tries to add a ninth, make them delete two first.

Status discipline matters. "New" means nobody has read it. "Replying" means someone has claimed it and will post within 6 hours. "Replied" means the comment is live. "Dead" means the thread aged out, got locked, got removed by a filter (which happens often, see why posts vanish from subs), or OP already picked a competitor. Dead rows do not get deleted. You review them weekly.

The pipe from Reddit to Notion

You have three realistic options for getting threads into the database. I'll rank them from least to most sustainable.

Option A: manual, via a browser bookmarklet

Works until you hit roughly 5 relevant threads a week. Beyond that, the ritual of copy-paste eats your morning.

Option B: Zapier or Make, polling Reddit search

Reddit exposes a JSON endpoint for any search query. For example, https://www.reddit.com/search.json?q=%22alternative+to+pipedrive%22&sort=new returns a feed of recent matching posts. Zapier can poll that, filter by subreddit, and create a Notion page via the official Notion create-a-page API.

The cost of Option B is maintenance. Reddit rate-limits unauthenticated requests, your Zap breaks silently when a sub goes private, and you end up tuning keyword regex at 11pm. It's fine for one or two queries. It falls over at ten.

Option C: a dedicated monitor that pushes to Notion

If scanning subs for buying intent is a daily job and not a hobby, hand it to something built for it. Bazzly watches the subs you care about for the signals you define and sends matching threads straight into Notion (or Slack, or both) with the subreddit, score, and timestamp already filled in. The point of outsourcing this isn't laziness, it's that keyword monitoring is a solved problem and your attention is better spent writing the actual reply.

Whatever you pick, the ingestion step produces one Notion row per thread. The row arrives with Status = "New" and Owner empty.

The end-to-end flow

Rendering diagram…

The triage step is the one most teams skip. Someone has to look at the "New" rows every morning and either claim them or mark them Dead. Fifteen minutes. If nobody owns triage, the database turns into exactly what the r/Notion skeptics are complaining about: a pretty surface over a dead workflow.

Writing the reply (not in Notion)

Don't draft Reddit replies inside the Notion row. Draft them wherever you draft, paste them into Reddit, and come back to Notion only to flip Status to "Replied" and drop one sentence in Outcome notes. The sentence is for the weekly review and should answer: did OP respond, did you get upvoted or downvoted, did anyone DM you.

If you're worried your replies read like a pitch deck, the general rules for not getting removed on Reddit are covered in the how-to-sell-on-Reddit guide. The short version: lead with the specific advice, mention the product once if at all, and never link in the first comment on a sub that doesn't explicitly allow it.

The weekly review (the part that keeps it alive)

Every Friday, filter the database to rows where Status = Replied or Status = Dead from the past 7 days. Look at three things:

1. Reply-to-DM rate. Of the replies that got engagement, how many turned into a DM or a signup? If it's zero across 10+ replies, your reply template is off and the keywords are fine. If you're getting zero replies at all, the keywords are too broad.
2. Dead reasons. If half your "Dead" rows say "filter-removed," you have an account health problem, not a Reddit problem. The filter-removal explainer covers how to diagnose that.
3. Subreddit mix. Which subs produced the signals that actually converted? Prune the keyword rules in subs that produce noise. Add more coverage to the subs that produce buyers. The founders I know with the best Reddit pipelines monitor three to six subs deeply, not thirty subs shallowly, which matches the pattern in the 4-week Reddit playbook for B2B design partners.

What to avoid building

I've watched teams add fields for "persona," "ICP tier," "intent score 1-5," "linked HubSpot contact," and "follow-up cadence." Every one of those fields was abandoned within two months. The tracker's value is operational, not analytical. You're not building a CRM. You're building a to-do list that happens to be filled by Reddit's firehose.

If you can keep the schema at eight fields and the status discipline at four states, the tracker will still be alive next quarter. That's the whole bar.