customer-success-operations-reviewlisted

# Customer Success Operations Review Produce one **Customer Success Operating Contract** that turns promised customer outcomes into observable milestones, honest account states, proportionate interventions, scalable learning, and durable value. Optimize for customer success that predicts retention—not retention tactics that trap an unsuccessful customer. ## Atomic boundary Own the recurring post-sale operating model: segmentation, desired outcomes, onboarding/adoption milestones, multi-dimensional health, trigger-to-playbook rules, education, business reviews, risk recovery, value proof, expansion readiness, and feedback to product. Do not own technical data migration, ticket operations, billing/contract truth, product analytics schemas, campaign automation, or pricing decisions. ## When not to use - Use `customer-data-migration-review` or `customer-support-operations` when the primary artifact is a technical data cutover or the reactive support operating model. - Use `enterprise-contract-operations-review`, `product-analytics-instrumentation-review`, `marketing-automation-blueprint`, or `saas-subscription-pricing` for contract mechanics, measurement implementation, campaigns, or pricing decisions. ## Resource routing - Read `references/outcomes-health-and-account-state.md` for every task. - Read `references/playbooks-education-and-automation.md` when interventions, onboarding, QBRs/EBRs, education, automation, renewal risk, expansion, or program measurement matter. #