I ran the scan. The content calendar needed a lie down.

The brief was a website. The useful bit was outside it.

I took a consumer web platform already used by a Redtail customer and ran its website through the research tool. I wanted to see which questions its product could help answer, and where those conversations were happening.

The finished report returned 23 matched threads, a shortlist of 10 communities, five questions to answer, five recommended actions and three content briefs. The returned threads spanned 15 communities; the watchlist narrowed that to 10.

That is a much better starting point than opening a blank content calendar and asking everyone to have a thought by Thursday.

People were describing a decision. The brand was describing a product.

The repeated need was practical: help me find an option that suits my situation and works with what I already use. The wording varied, but the underlying decision kept coming back.

The report’s strongest-ranked threads scored 61 out of 100 on Redtail’s fit measure. That gave me a place to start reading. I wanted to know which constraints kept appearing, what people had already tried and which answers left them asking another question.

The shortlist also included a product-showcase thread. I separated that from the question-led evidence. A founder introducing a product and a person asking for help are useful in different ways. Lumping them together would make the brief worse.

Three briefs. Mercifully few thought-leadership emergencies.

The report generated three content briefs. I’d develop them around the decision, the recurring scenario and the practical coordination problem that appeared in the scan.

First, a comparison page organised around the constraints people actually mentioned. It should explain how to choose, where each option fits and when the product is useful. The feature list can wait its turn.

Second, a focused answer to a recurring question, with a worked example. I’d put the answer near the top, explain the assumptions and link to the relevant product detail.

Third, a practical guide to the adjacent problem people were trying to solve. The scan made that a concrete subject to investigate. I’d check the product’s capabilities before turning it into a recommendation.

• Comparison: help someone make the choice.
• Focused answer: resolve the recurring question.
• Practical guide: explain the adjacent task clearly.

Reddit supplied the brief. The website still has homework.

Reddit’s immediate value here was customer research. The threads exposed the language, constraints and follow-up questions a polished product description can miss. I’d use that to improve the website’s comparisons, FAQs and examples.

There is also a participation opportunity: read the full discussion, check whether it is still active and answer where there is something useful to add. I’d disclose any connection to the brand and follow the community’s rules.

For GEO/AEO, I want the same clear answer to hold up across the website, a useful demonstration, relevant community discussion and independent coverage. Each has a job. In this scan, Reddit showed me where to start.

The next move is pleasantly specific.

I’d start with the strongest recurring question, build the comparison and answer page, then demonstrate the difficult part. The community watchlist becomes a way to see which questions keep coming back and whether the explanation needs work.

I’d measure the pages against a fixed set of buyer questions, record mentions and citations across answer engines, and check qualified visits and enquiries. That would show which part of the work deserves more time.

The result of this run is a focused research shortlist and a content plan with actual questions behind it. I came in with a website. I left with three briefs and a considerably less mysterious Monday.