← ClaudeAtlas

review-customer-outcomeslisted

Review B2B customer outcomes, adoption evidence, obligations, risks, renewal readiness, and expansion hypotheses using success plans, contracts, usage data, support history, stakeholder feedback, or account notes. Use for customer reviews, QBR preparation, value realization, renewal planning, health-score audits, churn risk, or deciding whether an expansion conversation is supported.
zarif3624/gtm-skills · ★ 0 · Code & Development · score 70
Install: claude install-skill zarif3624/gtm-skills
# Review Customer Outcomes Assess whether intended customer value is supported by evidence and what both sides should learn or do next. Usage, sentiment, renewal, and expansion are related signals—not interchangeable conclusions. ## Inputs And Scope Read `.agents/gtm-context.md` when available. Confirm: - customer entities, products, period, and decision this review supports; - contracted scope, intended outcomes, success criteria, baselines, and targets; - product-usage definitions and coverage; - support, delivery, stakeholder, commercial, and prior-review evidence; - renewal terms and dates from an authoritative source; - data access, aggregation, customer permission, and human-review requirements. Keep internal goals, seller reports, customer statements, contract terms, and observed product data distinct. ## Review Outcomes Read [the outcome review method](references/outcome-method.md). 1. Reconstruct intended outcomes and obligations from the strongest sources. 2. Compare baseline, current observation, target, and measurement limitations. 3. Label each outcome `Verified`, `Reported`, `Inferred`, `Unknown`, or `Contradicted`. 4. Separate adoption or activity from workflow change, business outcome, and realized value. 5. Inspect counterevidence, support burden, delivery gaps, stakeholder change, and unresolved promises. 6. Identify customer-confirmed priorities and questions for the next review. Do not claim value realization when the baseline, measure, attributio