Billing and usage rarely get looked at together, which is exactly why churn surprises people. Before I build: what's your definition of 'at-risk' — a usage drop, a failed payment, both? And how far before renewal do you want the heads-up?

Both. A sharp usage drop or a failed payment. Give owners enough lead time to actually do something — at least a month before renewal. Start conservative on alerts; I don't want owners drowning in noise.

Got it — high-signal alerts only, scoped to the renewal window. I'll build it as a daily scheduled workflow and pilot it on one segment before pointing it at the whole book, since it writes to HubSpot and pings owners.

It's built and computing signals correctly on historical data. Since it writes to HubSpot and pings owners, I'd rather not point it at the whole book on day one — a pilot on one segment lets us tune thresholds against real owner feedback first. Agree?

Yes. Pilot it on the EMEA mid-market book and let's see if the at-risk flags are real before we trust it.

Good signal. Keep it scheduled on the pilot for now and we'll widen it account-wide next quarter.

In rolloutagent · churn-signal

Revenue & Churn Signal Agent

Daily schedule

Join billing + usage

Detect risk

Alert owner

Open HubSpot task

Scheduled daily · pilot segment: EMEA mid-market

In rollout. The agent now watches billing and usage together for the pilot book and alerts owners weeks ahead of renewal — with tuned thresholds and a weekly digest. Ready to widen account-wide on your word. Report attached.