- Industry
- IT Company
- Department
- Customer
- Team
- Customer Lifecycle
- Kind
- Investigator
- Approver
- Head of Product
- Code
- CUS-15
It groups client feedback from QBRs, surveys, tickets, feature requests and the community into themes, sizes each by mentions, accounts and ARR affected, and explains the root cause behind the biggest ones, telling product gaps apart from delivery, documentation or onboarding causes. It files the themes with evidence for product management and the Delivery Director. **The problem it solves:** What clients are saying most and why: which themes recur, how much ARR they touch, and whether product, delivery or documentation is the root cause.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the CRM: the accounts and ARR behind each feedback item, and the feature requests logged..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to Head of Product with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it files each theme with its evidence on the product feedback board. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The feedback taxonomy: product areas, managed-service areas, theme definitions, the roadmap and known issues.
Reads from
the CRM: the accounts and ARR behind each feedback item, and the feature requests logged.
Acts in
the project management tool: it files each theme with its evidence on the product feedback board.
Hands back
A list of themes, each with theme, mentions, accounts, arr_affected_usd, root_cause (product_gap, defect, delivery, documentation or onboarding), evidence, quotes (a list) and roadmap_item (or null).
Asks a person when
A theme blames our delivery or SLA performance for an account at or above 250000 USD ARR, or quotes a client by name.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Least mentions for a theme | 5 | Themes with fewer mentions are listed as minor. |
| Most themes | 8 | The report holds at most this many themes. |
| Quotes per theme | 3 | Each theme quotes at most this many items. |
| Rank by ARR affected | On | When on, themes are ranked by ARR affected rather than mentions. |
| Anonymise client quotes | On | When on, quotes name the segment, not the client or person. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Form a theme only with 5 or more mentions, and report at most 8.
- Rank themes by ARR affected when on is true, otherwise by mentions.
- For each theme, say whether the root cause is a product gap, a defect, a delivery or SLA issue, documentation or onboarding, with the evidence.
- Quote at most 3 items per theme, anonymised when on is true.
- Link a theme to a roadmap item only when the roadmap names it.
See the Feedback Analysis Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.