Turn customer feature requests into a prioritized brief for the product team

Help me turn the feature requests from my accounts into a brief for the product team. Requests: [PASTE LIST - ideally with account name, contract value, renewal date, and the customer's words] Product context: [WHAT THE PRODUCT DOES, any known roadmap themes] Time period covered: [e.g. "last quarter"] Do the following: 1. Group the requests into themes based on the underlying problem, not the feature they suggested. Name each theme as a user problem. 2. For each theme, show: number of accounts, total contract value of those accounts, accounts with renewals in the next 6 months, any accounts that called it a blocker or churn reason, and 1-2 representative quotes. 3. Rank themes by business impact, and explain the ranking. 4. Flag requests that look like training or configuration issues (the product already does it) - those are CS actions, not product asks. 5. Note any themes where a single large account is driving the request, so product can weigh it fairly. Output: a one-paragraph summary, then a table: | Theme (user problem) | # accounts | Total value | Renewal risk | Example quote | Suggested next step |. Use only the data I provided. Where value or dates are missing, write [MISSING] rather than estimating.