Expansion trigger finder
Name the accounts where usage, headcount, or a new project points at more business, and route one to the account owner with a reason attached.
Tools
Stripe, Shopify, Zendesk, Salesforce
Outcomes
Every expansion trigger has an owner • No growth signal noticed after the fact • Conversation opened before the customer asks • Account plan updated with the change
Documentation
Instruction-ready detail below
An account doubles its seats over a quarter and sales finds out from the customer's support team, because the signal sits in product analytics while the account plan stays unchanged. This workflow keeps a watch list and checks it on a schedule. It compares usage against the level the account was bought at, new teams appearing in the product, hiring signals, invoices that stopped being routine, and support tickets that concentrate on one problem. Each crossing is written as a dated trigger with the number behind it, so the account owner can see the change rather than take an opinion. Triggers are grouped by account rather than fired one at a time, which stops a fast-growing account generating six separate alerts. An account already covered by an active expansion conversation is marked covered instead of being handed to a second rep. A human still decides whether the change is worth a real conversation, what to propose, and whether the timing suits the renewal sitting underneath it. The workflow spots the moment; it does not judge whether the moment is good.