The Content Radar: An AI Employee That Finds What to Post on X, Reddit, Instagram and TikTok

Why this only works after the context layer

A generic “find trending topics” bot returns what is trending. That is not useful; it is a news feed. The radar is useful because it knows three things a generic bot does not: what your product does and who it is for (the persona file), what your customers have been asking for and complaining about (the support tally — 114 rows at Pocket Clear), and how you write (the drafts you have sent and the ones you edited). With that loaded, “rising topic” becomes “rising topic that intersects with the second-most-requested thing in your inbox, drafted in your voice.” Without it, you get listicles. The context layer is described here.

What it watches

• X. Keywords, your competitors’ mentions, the accounts your customers follow. A Grok bot is the natural agent here because it lives where the conversation is.
• Reddit. The three to five subreddits where your customers actually ask for help — for a finance app that is personal-finance and budgeting communities, not r/startups. New posts and rising comments, not the front page.
• Instagram and TikTok. Hashtags and creators in your category, read for the questions in captions and comments rather than the videos. “Does anyone know an app that…” is a content brief written by a customer.
• Your own inbox and reviews. The tally is the ground truth. A topic that is rising outside and already has votes inside is the one to write.

What it produces, weekly

1. A ranked list of five to ten topics, each with the outside signal (where it is rising, how fast), the inside signal (tally rows it matches), and a one-line angle.
2. A draft per platform for the top three: a thread for X, a comment or post for the relevant subreddit that answers the question rather than pitching, a caption and hook for Instagram or TikTok. In your voice, because the persona and your past posts are loaded.
3. A “do not post” note: topics that are rising but where the honest answer is that your product does not do that yet — with the tally row it would become if enough people ask.

What it must never do

• Post. Nothing goes out without a person. The radar writes to a drafts folder, exactly like the support pipeline.
• Reply in communities as if it were you. Reddit in particular punishes this correctly. Drafts for community replies are written to be read, edited, and posted by a human who is actually a member.
• Invent traction. Every number in a draft comes from the metrics source in the context layer, or it is not there.
• Chase volume. Five topics that intersect your tally beat fifty that are merely trending. The ranking weights inside signal above outside signal on purpose.

How it connects to the rest

The radar is not a separate product. It is the reading half of the pipeline — Hermes or a Grok bot classifying and tallying — pointed at public feeds instead of the inbox, with the same workhorse (Claude Code or ChatGPT) drafting on the same persona. That is why it is cheap once the layer exists and why it does not work before. It is included in the Growth package and switched on in the last two weeks of setup, after the support drafts have taught the teammate how you write.

Frequently asked questions