Customer feedback,
carried into the build

Brief connects what customers say in Slack and on calls to the ticket that gets built, with their need and the outcome attached.

Book a demo Talk to us about a pilot

Reads from

and more

0:46

Trusted by

Follow the customer’s words

One customer sentence, from Slack to the agent that ships it.

Feedback in Slack
The PM relays what Northstar’s account manager is dealing with.

# customer-feedbackMessages

Product Manager 5:40 PM

Northstar’s AM is still building the benchmark section by hand before every QBR. Pulling the numbers and reformatting the table is taking longer than the actual account review.

Can we get relevant peer comparisons straight into the export? Their $900k expansion is in negotiation, and this came up again on today’s call.

Today

Account Manager 1:51 PM

I’m spending most of my QBR prep pulling peer benchmarks into a spreadsheet and fixing the table. Can we put those comparisons straight into the export?
The customer call
The sponsor asks for eight peers and an industry filter.

BriefDocument

Meridian sourcesAugust customer advisory board

Choosing the right peers

02:18 · Executive sponsor, Northstar Manufacturing
Twelve benchmarks is noise. Give me eight and let me filter by industry.

Taking the export into the meeting

03:05 · Customer success lead
Keep the table readable in the PDF. We reformat it before every customer review.
The research signal
Brief records who is affected and the message it came from.

BriefResearch signal

Account managers need less manual benchmark preparation

Source excerpts

Northstar’s AM is still building the benchmark section by hand before every QBR…

#customer-feedback · Product Manager

Source
Slack

Urgency
High

Status
Planned
The feature record
The signal informs the feature, next to its standing decisions.
BriefFeature

Benchmark table in QBR export
Planned
Related Research Signals2
- Eight relevant benchmarks with
  industry filtersInforms
- Account managers need less manual benchmark preparationInforms
Built for2
- Account managerImpacts
- Executive sponsor
The build ticket
The customer problem and outcome, with criteria tied to decisions.
SpacesMeridianMER-1

Build benchmark table in QBR export
To Do
Description

Customer problem

Account managers currently spend more time manually reformatting the benchmark table than conducting the actual account review, pulling numbers and adjusting the export by hand before every QBR.

Slack source · #customer-feedback
Northstar’s AM is still building the benchmark section by hand…
Acceptance criteria

The benchmark table defaults to 12 peer benchmarks per export, per the active default decision D-041. The eight-peer-plus-industry-filter default proposed in D-043 is NOT implemented; it remains pending Product Manager approval.
D-041D-043 pending

All table and chart rendering uses Compass v2 components, per D-040.
D-040
The coding agent
The agent hits D-039 and gets the reason and the approved path.

meridian-qbr · coding agent

● Searching for 2 patterns, reading 8 files…

└ src/design/compass-v2.mjs

● Write(src/qbr.mjs)

└ Error: PreToolUse:Write hook error: Blocked by the current Meridian decision ledger. The proposed edit would introduce a recorded shortcut.

D-039: Customer data must come through the approved cdp service. Do not query the warehouse directly or call third-party enrichment APIs.

Owner: Data Governance Lead

Use src/services/cdp.mjs for account-scoped peer data.

Use the approved alternative and retry the edit.