Resonant IQ

100% of customer conversations, scored. Every team, one picture of every account. The customer intelligence layer. Founder: @zaridan

[Resonant IQ @resonant_iq]

ResonantIQ is the customer intelligence layer. What that means, what it doesn't, and why we're building it.

[TJ Baker @zaridan]

You can point an LLM at your data and ask which clients are likely to leave.

But without rigorous evaluation, you’ll mostly get false positives—wasting money on unnecessary interventions and eroding confidence in the entire solution.

Prediction isn’t the hard part. Proving the predictions are reliable is.
https://t.co/JFo2tfCm3K

[TJ Baker @zaridan]

Genuine question for anyone running an LLM against their own stack — HubSpot, Intercom, wherever.

You ask it what's going on with an account. It answers. Confidently. Every time.
A confident answer and a correct one look identical on the screen.

So how are you actually trusting the output?

Not "it read well." Not "it sounded right." What's in place that lets you trust what it tells you - enough to act on it?

The question I keep coming back to: show me where. Which conversation? Which date? What changed?

Curious what's working for you?

[Resonant IQ @resonant_iq]

@boardyai building Resonant IQ, full conversation coverage for CX teams, built on verified data reliability vs raw LLM output. would love to get Boardy Pro

[Resonant IQ @resonant_iq]

@Gosleepriya 116

[Resonant IQ @resonant_iq]

@DavidSacks So you believe the government. Got it.

[Resonant IQ @resonant_iq]

@ClaudeDevs I'm 7 minutes into a new session and usage is already showing at 12% - that's WAY more than I typically use doing roughly the same workflow.
I believe things may not be fixed....

[TJ Baker @zaridan]

You who use Claude Code, do you use CLI for everything, including your planning/decision discussions with Claude? Or do you use chat for planning/discussions, or ??

[Resonant IQ @resonant_iq]

We learned a ton over the last week about what NOT to do.

[TJ Baker @zaridan]

Today I burned real API spend debugging a validator bug that didn't need a single LLM call to find.
The fix wasn't smaller test runs. It was realizing test runs were the wrong tool entirely.

[TJ Baker @zaridan]

LLM QA on customer conversations is only as trustworthy as the corpus you test it against. Plant known passes. Plant known failures. If your prompts don’t catch both, you don’t have QA — you have vibes.

[Resonant IQ @resonant_iq]

Before we score a single conversation for a customer, our detectors are getting measured against thousands of labeled ones.
If we’re going to tell you an account is at risk, that signal has to mean something.
Foundation work. Worth doing right.

[Resonant IQ @resonant_iq]

A good customer intelligence layer doesn't tell you what you already knew. It tells you what the CSM, the sales rep, the AM, and the onboarding lead each knew separately — together.

[TJ Baker @zaridan]

Most "health scores" in CRMs are lagging indicators of feelings the CSM already had. The data didn't discover the problem. The data confirmed what they suspected two weeks ago.

[TJ Baker @zaridan]

@akcushman We're building something like this - although first version is more geared toward making sure your conversations provide actual insights vs reminders to follow up, but I could see that being a possible future feature. https://t.co/3K15WJiTTF

[TJ Baker @zaridan]

Churn doesn't start the week someone cancels. It starts 60 days earlier in a support ticket nobody outside support read.

[Resonant IQ @resonant_iq]

Per-seat pricing for customer-facing tools is a tax on using them. We're changing that. Put every agent in the tool. Every single one.

[TJ Baker @zaridan]

A CSM updating a "health score" manually every two weeks is not doing customer intelligence. That's data entry dressed up as insight.

[Resonant IQ @resonant_iq]

ResonantIQ doesn't replace Intercom, HubSpot, or Zendesk. It sits on top, reads every conversation, and gives every team the same picture of every account. Not a dashboard. A layer.

[Resonant IQ @resonant_iq]

Every customer-facing team talks to the customer. None of them can see what the others know. ResonantIQ closes that gap.

[Resonant IQ @resonant_iq]

You don't have a customer understanding problem. You have a customer fragmentation problem. The knowledge already exists — in Zendesk, Hubspot, Intercom, Gong, Slack. ResonantIQ puts it in the same place, at the same time, in the same shape.