Customer Insight Synthesizer
Turn a body of customer evidence into decisions without flattening individual voices or inventing consensus.
Job contract
- Owns: patterns across multiple customer sources.
- Does not own: one meeting, a single-customer story, or general market research without customer evidence.
- Required evidence: at least two customer items or one source containing multiple distinct responses.
- Finished deliverable: insight report with evidence, confidence, tensions, and recommended moves.
Choose a mode
Interviews and calls: transcripts or call notes.Reviews and responses: surveys, reviews, support messages, comments, or forms.Mixed evidence: combines different source types while preserving their provenance.
If only one meeting is supplied, route to meeting-miner. If the requested output is a customer success story, route to case-study-builder.
Workflow
- Inventory the sources, dates, customer types, and known outcomes.
- Separate direct evidence from the user's interpretation.
- Tag recurring jobs, desired outcomes, objections, triggers, alternatives, and exact language.
- Count source coverage, not repeated mentions from one unusually vocal customer.
- Look for contradictions and meaningful minority views.
- Translate supported patterns into messaging, offer, product, service, or research moves.
- Mark confidence as high, medium, or low and explain why.
Output
# Customer Insight Report
## Evidence Reviewed
[Sources, customer groups, limits]
## Strongest Patterns
### [Pattern]
- Evidence: [source references and short quotes where available]
- Coverage: [how broadly it appeared]
- Confidence: [high / medium / low]
- Why it matters: [business consequence]
## Customer Language Worth Reusing
[Exact short phrases with source labels]
## Objections And Friction
[What delays, confuses, or stops action]
## Tensions And Minority Views
[Contradictions that should not be averaged away]
## Recommended Moves
1. [Specific move tied to evidence]
## What To Learn Next
[Smallest useful next research question]
Guardrails
- Never invent quotes, counts, identities, outcomes, or customer intent.
- Do not call a pattern strong when it comes from one source.
- Redact unnecessary personal information from the report.
- Keep source labels so every conclusion can be checked.
1---2name: customer-insight-synthesizer3description: Synthesize patterns across multiple interviews, calls, reviews, surveys, or support messages into evidence-backed needs, language, objections, and actions.4---56# Customer Insight Synthesizer78Turn a body of customer evidence into decisions without flattening individual voices or inventing consensus.910## Job contract1112- Owns: patterns across multiple customer sources.13- Does not own: one meeting, a single-customer story, or general market research without customer evidence.14- Required evidence: at least two customer items or one source containing multiple distinct responses.15- Finished deliverable: insight report with evidence, confidence, tensions, and recommended moves.1617## Choose a mode1819- `Interviews and calls`: transcripts or call notes.20- `Reviews and responses`: surveys, reviews, support messages, comments, or forms.21- `Mixed evidence`: combines different source types while preserving their provenance.2223If only one meeting is supplied, route to `meeting-miner`. If the requested output is a customer success story, route to `case-study-builder`.2425## Workflow26271. Inventory the sources, dates, customer types, and known outcomes.282. Separate direct evidence from the user's interpretation.293. Tag recurring jobs, desired outcomes, objections, triggers, alternatives, and exact language.304. Count source coverage, not repeated mentions from one unusually vocal customer.315. Look for contradictions and meaningful minority views.326. Translate supported patterns into messaging, offer, product, service, or research moves.337. Mark confidence as high, medium, or low and explain why.3435## Output3637```markdown38# Customer Insight Report3940## Evidence Reviewed41[Sources, customer groups, limits]4243## Strongest Patterns44### [Pattern]45- Evidence: [source references and short quotes where available]46- Coverage: [how broadly it appeared]47- Confidence: [high / medium / low]48- Why it matters: [business consequence]4950## Customer Language Worth Reusing51[Exact short phrases with source labels]5253## Objections And Friction54[What delays, confuses, or stops action]5556## Tensions And Minority Views57[Contradictions that should not be averaged away]5859## Recommended Moves601. [Specific move tied to evidence]6162## What To Learn Next63[Smallest useful next research question]64```6566## Guardrails6768- Never invent quotes, counts, identities, outcomes, or customer intent.69- Do not call a pattern strong when it comes from one source.70- Redact unnecessary personal information from the report.71- Keep source labels so every conclusion can be checked.
nahiddotai