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.
Billing
Billing Event Coordination with Product State
The billing agent must verify product state before processing any charge: Is the account active? Is the feature being billed for actually provisioned? Has the plan changed since the last invoice? The product agent and billing agent synchronize state daily. Charging for features a customer does not have access to is the fastest way to generate support tickets and chargebacks.
What goes wrong without this
A customer downgrades from Enterprise to Pro on the 15th. The billing agent charges the Enterprise rate on the 1st because the plan change did not propagate. The customer disputes the charge. The support agent issues a refund. But the billing agent charges Enterprise again next month because the root cause (sync failure) was never fixed.
Dunning Sequence with Product Access Coordination
When a payment fails, the billing agent owns a multi-step dunning sequence: Day 0 retry + email, Day 3 retry + urgent email, Day 7 final notice with grace period warning, Day 14 downgrade to free tier. The product agent must coordinate: features are not removed until the billing agent confirms the grace period has expired. No customer should lose access to their data because of a credit card expiry.
What goes wrong without this
A payment fails on a Tuesday. The billing agent sends emails. But the product agent independently revokes access on Wednesday because it detected an unpaid invoice. The customer was mid-presentation using the product. Their screen goes blank in front of their team. They had every intention of updating their card. Now they are humiliated and furious.
Plan Change Proration Transparency
When a customer changes plans mid-cycle, the billing agent must calculate the proration, show the math to the customer before charging, and coordinate with the product agent to activate/deactivate features at the exact moment the billing change takes effect. The support agent must have access to the proration calculation to answer "why was I charged this amount?"
What goes wrong without this
A customer upgrades from $49/mo to $99/mo on day 15. They expect to pay ~$50 for the remaining half-month. The billing agent charges $99 for the full next month plus a $50 proration they did not expect. The customer contacts support. The support agent cannot explain the math because they cannot see the billing agent's calculation. Three agents, zero coordination.
Usage-Based Billing Reconciliation
For usage-based pricing (API calls, storage, compute), the metering agent and billing agent must reconcile daily. The metering agent reports raw usage. The billing agent applies pricing tiers, committed minimums, and overage rates. Discrepancies greater than 5% trigger an alert before any invoice is generated. Customers on usage-based plans check their bills carefully.
What goes wrong without this
The metering agent counts 1.2M API calls. The billing agent calculates based on 1.4M due to a timezone mismatch in the aggregation window. The customer is overcharged $800. They catch it because they track their own usage. One billing error on a usage-based plan erodes all trust in the billing system permanently.
Stay in the loop
Get weekly coordination intelligence updates. No account required.