Find the feature request you've been ignoring for a quarter

The problem. No single support ticket or call convinced you to build a specific thing — but if you’d been counting instead of just reading, a pattern might have been staring at you for months.

The play. Hand Claude everything you have — support tickets, call notes, interview transcripts, even scattered Slack mentions — and make it count occurrences across all of it, not just summarize any one source.

Setup (10 min). Gather what you actually have into one folder: exported tickets, meeting notes, interview transcripts, anything with real user language in it. Don’t filter first — let the workflow do the filtering.

The prompt:

Read everything in this folder — support tickets, call notes, interviews,
whatever's here. I'm looking for a pattern I might have been dismissing
because no single instance felt urgent enough to act on.

1. Pull out every distinct request or complaint, merging near-duplicates
2. Count how many separate sources raised each one, and over what time span
3. Rank by (count × how long it's been recurring) — something raised six
   times over four months should rank above something raised twice this week
4. For the top 3, quote the clearest example of each, with its source

Don't invent a pattern that isn't actually there — if nothing recurs
meaningfully, say so plainly.

What you get. Whichever request has been quietly compounding in the background, with the receipts to prove it’s real rather than a feeling.

What to watch for.

• Recency bias runs the other way here too — a genuinely new, urgent issue can look unranked next to something that’s recurred for months. Use this as one input, not the only one.
• “Count × how long it’s recurring” is a heuristic, not a law — read the actual quotes before deciding something’s worth building.

Make it repeatable. Run this quarterly, feeding it whatever accumulated since last time. If the same request keeps reappearing at the top two quarters running, that’s a strong signal it’s earned a place in your roadmap.