About
Why Ebb exists.
Ebb started after the third time I watched a customer cancel and thought, I could have seen that coming a month ago. I had the data. I had the Stripe account. I had the support inbox. The signals were all there. I just wasn't looking at them in the right shape.
The off-the-shelf options were either reporting tools (great at telling me what already happened, useless at preventing what was about to) or full Customer Success platforms designed for teams of ten with six-figure budgets. For a founder running a few-hundred-customer SaaS, neither fit. So we built the thing that did.
Ebb is opinionated about three things. One, churn is a behavioural problem before it's a billing problem — and behavioural signals show up weeks before the cancel button. Two, a founder should be able to operate the whole thing in 15 minutes a week. Three, software at this size should explain itself: every score breaks down into the signals that produced it. No black boxes.
Built in Aotearoa New Zealand by a small team of people who have shipped subscription products and felt this exact pain.
Scope
What Ebb won't be.
Not enterprise
No SAML-by-default, no implementation consultants, no annual contracts in the five figures. If your org chart needs a procurement workflow to buy us, we're probably the wrong tool.
Not Customer Success
No accounts, no playbooks-as-CRM, no ‘health scores’ that take three weeks to configure. Ebb does one thing: tells you who's about to leave and why.
Not a CRM
We don't track deals, pipelines, or contacts. We integrate with the tools that do. If you're looking for HubSpot, please look for HubSpot.
If any of this resonates, the best thing you can do is join early access or email hello@ebb.nz. We read every reply.