What customers say about a topic
Best for: Product managers, founders
What are customers saying about [onboarding friction]? Pull the strongest quotes and link each one to the meeting or document it came from.
- search
- read_source
Copy a prompt, paste it into Claude, Cursor, or ChatGPT, and get an answer grounded in what your customers actually said. Each one runs on the Evermuse MCP.
23 prompts shown
Search every call, interview, email, and document in your workspace, and get answers tied to real quotes.
Best for: Product managers, founders
What are customers saying about [onboarding friction]? Pull the strongest quotes and link each one to the meeting or document it came from.
Best for: Sales, customer success
Summarize my last call with [customer]. List their needs, their pain points, and anything we said we would follow up on, with citations.
Best for: UX researchers, product managers
What are the top five pain points for [enterprise] customers? For each one, give me two direct quotes and the conversation they came from.
Best for: Product managers, UX researchers
Find every conversation from the last 90 days where a customer brought up [SSO]. Group them by theme and tell me which themes come up most.
Best for: Founders, product leaders
I believe [small teams churn because setup takes too long]. Search our customer evidence for anything that supports or contradicts this, and tell me how strong the case really is.
Run research and writing workflows where every requirement links back to a customer.
Best for: Product managers
Write a PRD for [bulk export], grounded in what customers have asked for. Every requirement should link back to a real customer quote.
Best for: Engineers in Cursor or Claude Code
Before I build [saved filters], pull the customer context behind it: who asked for it, what problem they are solving, and the edge cases they mentioned. Then write a feature spec I can implement from.
Best for: Product managers, engineers
Turn the plan for [team workspaces] into user stories with acceptance criteria. Cite the customer evidence behind each story.
Best for: UX researchers
Run customer research on this question: why do [trial users] stop before [inviting a teammate]? Show me the evidence for each finding.
Best for: UX researchers, designers
Build user personas from our interviews with [mid-market admins]. Base every goal and frustration on something a customer said, and cite it.
Best for: Product leaders, founders
Write a one-page brief on what we learned from customers this week: new needs, recurring pain points, and the quotes worth sharing with the team.
Load your product context, size up competitors, and check both against what customers say.
Best for: Anyone starting a new chat
Load our product context and play it back to me: mission, segments, personas, features, and current projects. Flag anything that looks out of date.
Best for: Product leaders, product marketing
Where are we most exposed to [our top competitor], and what do customers say about it?
Best for: Product managers, sales
List our competitors and compare their [reporting] capabilities with ours. Where do customers tell us we are behind?
Best for: Founders, product leaders
Which things are customers asking for that none of our competitors do well? Rank them by how often they come up.
Review the opportunities Evermuse surfaces, then create and update shaping notes from the conversation.
Best for: Product managers, product leaders
Show me the top product opportunities Evermuse has surfaced. Rank them by strength of customer evidence and tell me which one you would shape first, and why.
Best for: Product leaders
Which shaping notes are still in the PRD stage? Summarize where each one stands and what is blocking it.
Best for: Product managers
Turn the top [onboarding] opportunity into a new shaping note with the problem, the supporting evidence, and the open questions.
Best for: Product managers
Update the shaping note for [bulk export] with what we learned from this week’s customer calls.
Save transcripts and notes to the right project, and record or correct the signals in them.
Best for: Sales, customer success
Save this transcript to the [Q2 discovery] project and log the pricing pushback as a pain point.
Best for: Anyone who talks to customers
Here are my notes from today’s call with [customer]. Add them to the [onboarding research] project and record the needs and quotes as signals.
Best for: UX researchers
The signal about [export limits] is recorded as feedback, but it is really a pain point. Correct it.
Best for: Research ops, product ops
Draft a custom signal type called [churn risk] for moments when a customer hints they might leave. I will review and approve it in Evermuse.
Replace anything in [square brackets] with your own feature, customer, segment, or project. The tool names under each prompt are the Evermuse MCP tools your assistant typically calls. You never have to type them.
Four habits that make any prompt on this page work harder.
“Enterprise customers in the last 90 days” gets a sharper answer than “customers”. The narrower the question, the more relevant the evidence.
Add “with citations” or “link each quote to its meeting”. Your assistant will show which conversation backs each claim, so you can check it yourself.
Ask for a PRD, a feature spec, user stories, personas, or a brief by name. Your assistant loads the matching Evermuse skill and follows its template and checklist.
Start with the evidence, then ask for the spec, then file a shaping note. Each step builds on what the assistant already pulled.