Churn shows up in Stripe before it shows up in a board deck. Every week, an Orkeste agent lists the subscriptions that were cancelled or are past due, groups them by plan and posts a short summary to finance and customer success with the customers to call.
The problem
Cancellations are counted at month end, after the chance to talk to the customer has passed.
How the workflow runs
Runs: Every week on the day and hour you set.
List subscriptions: The agent lists recent subscriptions in Stripe with their status.
Find the changes: It keeps those cancelled or past due.
Add context: If the customer is in HubSpot, it looks them up and mentions the account owner.
Summarise: It groups the cases by plan and writes who to call first.
Post: The summary is posted to the finance and customer success channel in Slack.
The team decides: Customer success decides who to contact and what to offer.
The agent reports; any outreach, discount or plan change is decided and made by a person.
Who does what
Churn tracker: Lists and summarises subscription changes.
Customer success (human): Decides on any outreach or offer.
What this workflow does not do
Lists recent subscriptions; it does not compute MRR or a churn rate.
Read only in Stripe: no discount, pause or cancellation.
Knows why a customer left only from what it can read, such as a reason recorded in Stripe.