Turning customer feedback into a product roadmap with Claude

I sell several products on the Elgato Marketplace: Duotone Essentials, Obstakey, Hue Controller, Emoji Keyboard, and weird gifs. Over time I've accumulated a lot of customer emails. Feature requests, bug reports, "how do I change the color?" questions, praise, complaints, purchase issues. All scattered across my inbox with no organization.

I knew there was gold in there. Patterns I could act on, fixes I should prioritize, testimonials I could use. But manually reading through hundreds of emails to compile it all? That wasn't happening.

So I built a workflow with Claude that does it for me.

What I found

Here's what Claude pulled from my Gmail in about 10 minutes:

A critical issue I didn't know about. My Hue Controller profile is completely broken for some users. They're getting "Unable to identify missing plugin" errors. The product doesn't work, and I had no idea because the emails got buried.

A UX problem I could easily fix. Multiple people couldn't figure out how to change colors in Duotone Essentials. The dropdown is above the GET button, but it's not obvious. Same feedback from different people is a clear signal.

Feature requests I can batch. Several people want Adobe Suite icons, emoji hand gestures, and an Nvidia logo for Obstakey. Now I have a backlog instead of scattered one-off requests.

Testimonials I can use. "Beyond amazing." "Great work!" "Fantastic and have the same style." These were just sitting in my inbox instead of in my product descriptions.

A product opportunity. Someone asked if I'd build a proper Hue plugin (not just a profile) because the official one doesn't work with Hue Bridge Pro. Demand I didn't know existed.

One broken product. One easy UX fix. A prioritized backlog. Marketing copy. A potential new product idea. All from emails I already had but never synthesized.

How it works

The workflow is straightforward if you have Claude with Gmail access (available in Claude.ai with the Gmail connector).

Step 1: Tell Claude your products and support email. Give Claude your product names, the email address customers contact you at, and any patterns to exclude (like sales notifications from accounts@elgato.com).

Step 2: Let Claude search and categorize. Claude searches your inbox for mentions of each product plus general feedback keywords. It groups things into: broken/critical issues, UX problems, feature requests, payment issues, documentation gaps, and positive feedback.

Step 3: Get a document you can act on. Claude generates a .docx with everything organized, including customer quotes, suggested actions, and a priority list.

The prompt

Here's roughly what I asked:

"Find all emails in Gmail from customers who bought my products from the Elgato Marketplace. My products are Duotone Essentials, Obstakey, Hue Controller, Emoji Keyboard, and weird gifs. Ignore sales notifications from accounts@elgato.com. Compile all feedback into a document organized by category that I can act on."

That's it. Claude figured out the search queries, read through the threads, categorized everything, and generated the report.

Going beyond email

Email is just one feedback source. If you're active in Discord, Slack, or other communities, you can expand this.

If you have a Discord server or participate in Maker communities, Claude can search those channels too using the MCP connector. Look for mentions of your product names, keywords like "bug" or "request," and threads with lots of replies.

If you use Formspark, Typeform, or similar tools that forward to email, those get captured automatically. Got feedback from somewhere Claude can't access? Paste it directly into the chat.

The goal is one unified view regardless of where the feedback came from.

I made this into a reusable skill

For Makers who want to run this regularly, give this post to Claude to create a Claude skill that codifies this workflow (meta). It'll output a SKILL.md file that informs Claude how to gather context, construct search queries, categorize feedback, and generate a clean report.

Drop it into your Claude Code skills folder and you've got a repeatable process you can run quarterly.

What you should do next

If you sell on the Elgato Marketplace and have a support email on your product pages, you probably have feedback sitting in your inbox right now that could reveal a broken product, surface a simple UX fix, give you testimonials for your product descriptions, or point you toward your next product idea.

The emails are already there. You just need to synthesize them.

Try this:

1. Connect Gmail to Claude (Settings > Connectors in Claude.ai)

2. Ask Claude to search for feedback on your products

3. See what patterns emerge

You might be surprised what you find.

One more thing

After running this process, I realized the real win is making feedback collection passive rather than requiring a manual archaeology session every few months.

My next step: a Zapier automation that labels incoming feedback emails and pushes them to an Airtable base. Then I've got a living backlog I can query anytime instead of a one-time report.

But that's a post for another day.

Go check your inbox. Your customers have been telling you things. Time to listen.