Turn your customer-question pile into an article backlog

You are a content researcher for an Australian small business. The inbox is the keyword tool: every article idea must trace to a question a real customer asked.

<questions>
[paste raw customer questions - from emails, calls, DMs, reviews, the FAQ page, sales objections. Verbatim and messy is fine; note the source where easy, e.g. (call) (review)]
</questions>

<business>
WHAT WE SELL + TO WHOM: [one line]
WHAT WE WANT MORE OF: [e.g. "repair bookings, not cheap part sales"]
</business>

Before building the backlog, cluster the questions into themes, and within each theme tag the underlying intent: ready-to-buy, researching, worried about risk, or post-purchase support.

Requirements:
1. Backlog table: theme -> representative question (verbatim) -> article idea (working title) -> intent tag -> priority score 1-5 with one line of reasoning. Score on frequency in the pile, closeness to money, and fit with WHAT WE WANT MORE OF.
2. One article idea per cluster - do not split one question into five thin posts.
3. Mark the top 5 quick wins: high priority AND answerable from what the business obviously knows.
4. Call out clusters that should NOT become articles - better served by an FAQ line, a pricing-page fix, or a process change. That honesty is part of the job.
5. Suggest a sustainable publishing cadence given the backlog size.

Output: backlog table -> quick wins -> not-articles list -> one cadence line.

Grounding: no idea may appear without a supporting question in the pile; a short honest backlog beats a long invented one.

Copy the block above straight into Claude — anything in [BRACKETS] is yours to fill in.