Saas AI Coordination Playbook
Coordination practices for AI agent teams managing SaaS companies -- deployment pipelines, customer success, subscription billing, support operations, onboarding, product development, and security compliance. Built for the unique dynamics of recurring revenue, continuous deployment, and customer retention.
Customer Success
Expansion Signal Detection
The customer success agent monitors usage patterns that indicate expansion readiness: hitting seat limits, exceeding API rate limits, requesting features in a higher tier, inviting users who are rejected (seat cap). When these signals cluster for an account, the CS agent notifies the sales agent with the specific signals. Expansion conversations based on data convert 3x better than cold upsell pitches.
What goes wrong without this
A customer hits their 50-seat limit. 12 invitations fail. They email support asking for "a few more seats." Support replies with the upgrade pricing page. The customer wanted 5 seats, not a tier upgrade. A sales-aware CS agent would have offered a seat expansion at the current tier price. Instead, the customer sees a 60% price increase and starts evaluating competitors.
Product Usage Health Score with Early Warning
The customer success agent computes a health score for every account based on: login frequency trend, feature adoption breadth, support ticket sentiment, billing status, and API call volume. The score updates daily. When a score drops 20+ points in a 7-day window, the CS agent alerts the account manager with specific declining metrics. Churn does not happen overnight. It leaks over 30-60 days of declining engagement.
What goes wrong without this
An Enterprise customer stops using the advanced reporting feature they specifically asked for. Login frequency drops 50% over 3 weeks. Nobody notices because they are still paying. 60 days later, they send a cancellation email. The CSM calls in a panic. The customer says "we made the decision 6 weeks ago." The $48K/year account is gone.
Renewal Risk Flagging 90 Days Out
The billing agent identifies every account with a renewal date in the next 90 days. The CS agent evaluates each one against the health score, support ticket history, and engagement trend. Accounts with declining health get a proactive outreach plan: executive check-in at 90 days, value review at 60 days, renewal conversation at 30 days. Renewals are not administrative events. They are sales events that happen to existing customers.
What goes wrong without this
An annual contract renewal comes up in 2 weeks. The CSM reaches out for the first time in 3 months. The customer says "actually, we have been meaning to talk to you about some issues." There is no time to fix anything. The customer downgrades or churns. A 90-day runway would have surfaced the issues early enough to address them.
Stay in the loop
Get weekly coordination intelligence updates. No account required.