Brex needed feedback tied to accounts, not another report

Brex had customer feedback coming from sales calls, Slack submissions, CRM data, Snowflake context, and manual reporting workflows.

The problem was not a lack of feedback. The problem was making that feedback clean, attributable, and usable across product, CX, GTM, and marketing workflows.

BuildBetter helped Brex connect feedback to customers and companies, extract useful clusters from messy data, answer questions with AI chat, and move signals toward workflows like Slack updates, reports, and product follow-up.

4

departments sharing account-attributed customer signal

3

source systems tied to account context: Gong, Slack, and CRM / Snowflake

3

decision paths from feedback: reports, Slack updates, and product follow-up

The Pull

Brex was trying to make customer feedback useful across revenue, product, and GTM workflows.

Their current setup blocked them because customer conversations did not automatically become account-level signal. A sales call might contain a feature gap, a Slack post might hold frontline feedback, and CRM/Snowflake might hold company context — but those pieces still had to be connected.

BuildBetter unblocked them by tying feedback to customers and companies, grouping repeated themes, and creating a path from raw feedback to reports, Slack updates, and product action.

The Catalyst

The pull was account attribution. Feedback only mattered if teams could see the customer and company behind it.

Customer feedback lived in calls, Slack, and CRM. The work was tying it to accounts and sending it somewhere useful.

Before BuildBetter

Brex had customer signal across:

Gong calls,
/bb-feedback Slack posts,
CRM records,
Snowflake customer/company context,
manual reports,
Cycle-style workflows,
Qualtrics-style reporting.

Each system held part of the customer story. None made feedback reliably attributable and routable.

The Blocker

The problem was routing, not dashboards.

A sales call might include a feature gap, but the account context lived elsewhere.
A Slack post might hold frontline feedback, but ownership and routing were weak.
Noisy call imports and early-funnel attribution gaps made trust harder.
A useful signal still had to become a Slack notification, report, account view, or product follow-up.

“I'm most excited about associating feedback with customers easily — that's the most valuable feature.”

— James Wallis, Brex

The BuildBetter Workflow

Sales call or Slack feedback
    ↓
BuildBetter signal
    ↓
Customer / company attribution
    ↓
Cluster or report
    ↓
Slack update, account prep, product follow-up, or future Linear handoff

What Changed

Brex moved toward a more operational feedback workflow.

The clearest changes:

sales calls can become structured customer signal,
Slack feedback has a path into the system,
feedback can be associated with customers and companies,
clusters can group related feedback with impacted people and companies,
AI chat and reporting can help teams answer questions from the feedback base,
Slack and future Linear workflows give signals a path toward action.

“The cluster output is already very valuable because it clearly describes the problem and shows impacted people and companies — it's more purposeful and manageable than older, larger reports that previously took much more manual effort.”

— James Wallis, Brex

“BuildBetter's chat AI experience is better than others I've seen — I consider using chat answers as sufficient for report generation.”

— James Wallis, Brex

Next case study

Orah

Get started