Log in

Customer Success

Renewals at risk, flagged 90 days out

At-risk renewals are flagged 90 days out, scored from your Salesforce pipeline, Stripe payment behavior, and PostHog usage trends, with specific risk factors and a suggested intervention plan for each account.

Integrates with:

What changes

Before
With ZeroTwo
Risk assessment method
CSM intuition at QBR time
Scored from usage, billing, and sentiment data weekly
Signal coverage
Whatever the CSM remembers to check
Usage + billing + sentiment combined
Renewal tracking time
Hours of manual pipeline review each week
Automated weekly report
Intervention planning
Reactive scramble at renewal time
Proactive plan with specific risk factors and recommended actions

Risk assessment method

Before

CSM intuition at QBR time

With ZeroTwo

Scored from usage, billing, and sentiment data weekly

Signal coverage

Before

Whatever the CSM remembers to check

With ZeroTwo

Usage + billing + sentiment combined

Renewal tracking time

Before

Hours of manual pipeline review each week

With ZeroTwo

Automated weekly report

Intervention planning

Before

Reactive scramble at renewal time

With ZeroTwo

Proactive plan with specific risk factors and recommended actions

Renewal surprises cost more than anything else

The renewal is 30 days out. The CSM sends the standard check-in email. The customer responds: 'Actually, we've been evaluating alternatives.' Your stomach drops. Where did this come from? The account looked fine in the last QBR. But 'fine' was based on a gut check, not data, and the signals were there for months.

Usage had been declining since Q2. Three power users left the company. Support tickets spiked with increasingly frustrated tone. And the billing team flagged a failed payment that turned out to be the customer removing their credit card. Each signal lived in a different system, and nobody connected the dots until it was too late.

How ZeroTwo monitors renewal risk

1

Pulls every renewal due in the next 90 days

Salesforce

ZeroTwo found 14 renewals in the window. Two lost their champion last month, one has an unresolved escalation, and three have no QBR scheduled.

2

Flags payment warning signs like downgrades and disputes

Stripe

One account downgraded mid-cycle, another has two consecutive failed payments, and a third disputed their last invoice.

3

Measures engagement trajectory over the past quarter

PostHog

Four accounts show sustained usage decline. The worst dropped from 85 daily active users to 22 since last quarter.

4

Reads support sentiment and escalation patterns

Intercom

Two accounts show escalating ticket frequency with increasingly negative tone. One has an open P1 unresolved for 11 days.

5

Cross-references all signals and drafts a save plan per account

Google

ZeroTwo ranked all 14: 3 critical with converging risk factors, 5 moderate, 6 healthy. Each critical account gets a tailored intervention like exec outreach or re-onboarding.

6

Delivers the Monday renewal risk report to CS leadership

Slack

Critical accounts surface first with risk reasons, renewal dates, and the recommended next step for each.

Runs every Monday at 7:00 AM · Posts to #renewals in Slack and updates Salesforce pipeline

Get started in under 10 minutes

1

Connect your tools

One-click OAuth for each integration. No API keys, no engineering.

2

Describe what you need

Every Monday, score all renewals coming up in the next 90 days by combining usage decline in PostHog, failed payments in Stripe, and open escalations in Intercom. Flag anything critical to #renewals with a save plan.

3

It runs on schedule

Every Monday morning, the renewal risk report posts to your CS leadership channel.

Frequently asked questions

ZeroTwo combines signals from Salesforce (stakeholder changes, NPS trends, support escalations), Stripe (payment patterns, downgrade signals), and PostHog (usage decline, reduced feature breadth, fewer active users). Each signal contributes to a weighted risk score that flags the most at-risk accounts.

Each at-risk account gets a recommendation based on the specific risk signals. If usage is declining, the plan suggests a re-engagement workshop. If the champion left, it recommends executive sponsor outreach. If support frustration is the driver, it suggests a product feedback session. Actions match the risk type.

Yes. You configure which signals matter most for your customer base. For product-led companies, usage metrics might carry 50% of the weight. For enterprise accounts with low daily usage, stakeholder engagement and support sentiment might matter more. The model adapts to your churn patterns.

You set the lead time per contract type during setup. Annual contracts typically use 90 days, quarterly uses 45, monthly uses 30. ZeroTwo adjusts the monitoring window and intervention urgency accordingly.

Accuracy depends on data quality and how many signals are connected. With Salesforce, Stripe, and PostHog all feeding in, ZeroTwo catches most at-risk accounts 60-90 days before renewal. Early warning with some false positives is far more useful than finding problems at renewal time. You can tune sensitivity up or down.

Yes. After an intervention is initiated, ZeroTwo monitors the same signals to see if the trend improves. If usage rebounds, support sentiment improves, or engagement increases, the risk score decreases accordingly. You get a clear view of which interventions are effective.

ZeroTwo updates Salesforce renewal opportunities with risk scores and flags. Your existing renewal pipeline reports gain an additional data layer showing risk levels, making it easy for CS leadership to prioritize their pipeline review without switching tools.

Stop doing the work your tools should do for you.

Set it up once. ZeroTwo runs it every time.