Kuzu is being built to find revenue you've already won and are losing anyway — before it's gone.
I'm Alex. Twice now I've gone looking for revenue a company had already lost — in their own CRM and their own billing data — and found it. I'd rather be corrected now than after I've built the wrong thing.
A card expires on renewal. Stripe retries, gives up quietly two weeks later, and the subscription lapses. Nobody in HubSpot ever knew that account was at risk, and the CSM finds out at QBR.
A lead fills in the form on a Friday afternoon. It routes to an owner who's away, and there's no rule for what happens next. By the time anyone opens it on Wednesday, they've booked with someone else.
A champion changes their email domain in HubSpot, which is how you find out they've left. Nobody connects it to the renewal three months out, and the first conversation with their replacement is the renewal conversation.
HubSpot and Stripe are where Kuzu starts, because that's where the money and the relationship already are. The leaks aren't specific to them.
Automation runs the work you already know about. Kuzu is being built to find the work you don't.
You won't tell it what to look for. It's being built to read HubSpot and Stripe, work out what should have happened, and bring you the cases where it didn't — with the records it used, so you can check its working. Nothing gets sent or changed without your approval.
Drawn, not captured. Kuzu is being built to hand you one of these. There is no product to screenshot yet, so the company, the figures and the dates below are invented.
Meridian Freight halved their subscription on 9 June. HubSpot has forecast the renewal at the old number ever since, and nobody has spoken to them about it.
$15,600 / yr of forecast that isn't there
What this is based on
Why nobody caught it
Nothing failed, so nothing alerted. The downgrade was self-serve, so no human was ever in the loop. Both systems are individually correct — they only disagree with each other.
What to do
Correct the renewal amount to $15,600, and find out why Meridian cut back — before 1 October decides it for you.Kuzu would propose the corrected value with the before and after · the write needs approval
I've done this the slow way, twice. I copied both systems into one place so the records finally sat next to each other — which mostly meant arguing with myself about whether two rows were the same company — and then ran the same question at them from every angle until the disagreements fell out. Both times there was real money in there. It took weeks, went stale the moment I stopped feeding it, and nobody else at either company could have run it. That's the part I'm trying to automate — not the finding, the cost of it.
— Alex, building Kuzu
I said at the top that I'd rather be corrected now. This is where you do it. One sentence is plenty, and I don't want a meeting.
Kuzu isn't ready to look at. Leave an email and I'll come back to you when it is — nothing else.
The address goes into our HubSpot. It isn't shared, and it isn't used for anything else.
The privacy notice has the rest.
Think I've picked the wrong problem altogether? That's the most useful message I could get, and it comes straight to me — hello@trykuzu.com.