Built for a real book of business.

Why it exists

Customer Success Managers are asked to know their accounts. In practice they manage dozens of them, and the things that most change a relationship happen outside the product, where no dashboard is watching.

A funding round. A reorganisation. A new executive. A round of layoffs. None of it shows up in usage data, and all of it changes the conversation.

The information isn't hidden. It's published, publicly, in places anyone could read. The problem is that nobody has three hours a week to read it for fifty companies — and raw headlines aren't much use anyway.

What a CSM needs isn't the news. It's what the news means for their renewal, phrased so they can say it out loud on a call.

That gap is the entire product.

How it's built

CX Signals runs a pipeline, not a chatbot. For each account it gathers external developments, filters them to the company you actually mean, classifies each one against a customer-success taxonomy, scores it, labels it a risk or an opportunity, and writes a talking point with the source attached.

Two decisions shape everything else. First, every output is traceable to a source you can open and read — nothing is asserted on the system's own authority. Second, interpretation is tuned to what you sell: the same hiring surge means something different to a payroll vendor than to a security vendor, and the system is told which one you are.

Where it is today

CX Signals is a working product running against real accounts on a schedule, not a prototype. We are opening it to Customer Success teams through a pilot programme, onboarding a few at a time so that each team gets set up properly.

If that sounds like your team, join the pilot and we'll talk.