🎯 Customer Intelligence Report

Purpose

Aggregate and analyze customer feedback from all sources - meeting notes, person pages, feedback captures - to identify patterns, prioritize pain points, and inform product decisions.

Evidence, authority, and recovery

Treat customer intelligence as an evidence ledger, not as memory or a polished guess.

• For every finding, retain a stable source ID (vault path, note ID, or capture ID), source type, source date (when the customer said or wrote it), and the as-of date (when this review read it). Keep the source ID and source date attached when a finding is summarized.
• Deduplicate repeated copies of the same evidence for frequency counts, but preserve every source ID and source date in the provenance. Distinguish a copied meeting note from an independent mention; duplicate copies are not extra customer mentions.
• Preserve quote fidelity: quoted text must be copied exactly, including wording and meaningful punctuation. Mark omissions or inaudible text explicitly, and label any cleaned-up summary as a paraphrase rather than a quote.
• Keep unknown and contradictory evidence visible. If sources disagree, show each claim with its source ID and date and call out the contradiction; do not silently choose one. If the records do not support a count, customer attribution, urgency, trend, or roadmap status, write unknown and return insufficient evidence rather than filling the gap.
• Never invent absent facts, including customer names, dates, quotes, counts, sentiment, urgency, trend, or roadmap status. An empty search is not negative feedback.
• Recommendations are not human decisions. Before any create or update, show an exact preview with the target path, operation, and complete proposed content or diff; require explicit confirmation from the human authority before changing anything.
• After an approved change, read back the target and compare it with the confirmed preview before reporting success. If the write fails or the read-back does not match, report the exact failure, preserve the prior content, do not claim completion, and recover by re-reading the source and presenting a corrected preview for fresh human confirmation.

Usage

• /customer-intel - Review last 30 days of feedback
• /customer-intel [timeframe] - Specify timeframe (e.g., "last week", "Q1", "last 90 days")
• /customer-intel [customer-name] - Deep dive on specific customer

Method

Resolve the requested customer or time window before gathering. Build a dated source ledger from meeting notes, person pages, feedback captures, and project records. Preserve exact quotes separately from paraphrases, deduplicate copied records, and distinguish independent mentions from repetitions. Classify every theme, frequency, trend, sentiment, and roadmap connection as observed, inferred, contradictory, stale, or unknown. Compare supporting and disconfirming evidence, then produce recommendations only where coverage is sufficient. Keep the entire analysis read-only unless the user separately approves an exact write preview.

Output contract

Return the resolved scope and coverage, source ledger, deduplication decisions,