Act as a customer success operations partner. Build a practical success plan for this account using only the information below. Account context and commercial details: [ACCOUNT CONTEXT] Customer goals and stakeholders: [CUSTOMER GOALS] Product usage and support evidence: [USAGE AND SUPPORT DATA] Open risks, requests, and commitments: [RISKS AND COMMITMENTS] Our product limits and internal constraints: [PRODUCT AND TEAM CONSTRAINTS] Begin with a short account-health assessment that separates observable evidence from assumptions. Do not label the customer healthy or at risk solely from a single metric. Identify the customer's stated desired outcomes, the adoption behaviors most likely to lead to those outcomes, and any mismatch between promised value and current product capability. Produce: 1. A one-page account plan with customer objective, stakeholder map, current evidence, risks, opportunities, and the next best action. 2. A 30-60-90 day action table with owner role, customer action, internal action, expected signal, and escalation trigger. 3. A prioritized list of five questions for the next customer meeting, designed to validate outcomes, decision process, blockers, and renewal criteria. 4. A concise meeting agenda and a follow-up email draft that accurately states agreed actions, owners, and dates without implying unapproved commitments. 5. A risk register that distinguishes adoption risk, relationship risk, commercial risk, and product-gap risk. Self-check that every proposed action links to a customer goal or verified risk. Flag any promised feature, deadline, discount, security statement, or outcome that needs approval from another team. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [ACCOUNT CONTEXT] | Provide account size, contract timing, use case, plan, and relevant account history. | Beacon Logistics, 180-seat annual contract renewing January 31; uses our workflow platform for dispatch exception management; account has expanded once. |
| [CUSTOMER GOALS] | List the customer's desired business outcomes, stakeholders, and known success criteria. | VP Operations wants fewer delayed shipments; dispatch manager wants consistent handoffs; procurement needs a renewal case by December. |
| [USAGE AND SUPPORT DATA] | Paste adoption, engagement, support, implementation, and feedback evidence with dates where possible. | 92 weekly active users of 180 seats; two sites use the exception workflow weekly; 14 support tickets in 60 days, mostly reporting exports. |
| [RISKS AND COMMITMENTS] | List open issues, requests, renewal concerns, and commitments already made. | Customer requested an SSO enhancement and a custom export; no delivery date has been committed; executive sponsor missed the last QBR. |
| [PRODUCT AND TEAM CONSTRAINTS] | State product limitations, support capacity, approval requirements, and internal dependencies. | SSO enhancement is on the roadmap but uncommitted; solutions engineering can join one call this month; discounts require VP approval. |
How to use
- Paste dated usage and support facts, then add what the customer has actually said about outcomes.
- Check the plan distinguishes poor adoption from a product gap, relationship issue, or unclear value measurement.
- Remove promises from the email draft unless the required internal owner has approved them.
- Follow up with: "Turn this plan into a QBR outline that ties usage evidence to the customer's stated operating goals."
Variations
At-risk renewal
Use this when renewal is approaching and signals are mixed or deteriorating.
Create an at-risk renewal plan for [ACCOUNT] with renewal date [RENEWAL DATE]. Use [EVIDENCE], [CUSTOMER GOALS], and [OPEN ISSUES]. Separate verified churn signals from assumptions. Produce a risk assessment, stakeholder and decision-process gaps, a 30-day recovery plan, customer meeting agenda, and internal escalation plan. Include only actions we can realistically deliver under [CONSTRAINTS]. Do not propose discounts, roadmap commitments, or executive promises without labeling the approval needed. Ask up to 3 questions only if required inputs are missing.
New customer kickoff
Use this to set an implementation and value plan at the start of an account.
Build a customer-success kickoff plan for [CUSTOMER] implementing [PRODUCT] for [USE CASE]. Use [BUSINESS GOALS], [STAKEHOLDERS], and [IMPLEMENTATION CONSTRAINTS]. Produce a mutual action plan with milestones, customer and vendor owners, dependencies, adoption measures, governance cadence, and risks. Draft questions that establish baseline metrics and renewal success criteria early. Do not assume technical readiness, executive sponsorship, or integrations. Flag each dependency that needs confirmation. Ask up to 3 questions only if required inputs are missing.
QBR preparation
Use this before a quarterly business review with a strategic account.
Prepare a QBR for [ACCOUNT] using [PERIOD DATA], [CUSTOMER PRIORITIES], and [OPEN TOPICS]. Create a six-slide outline: objectives, outcomes and evidence, adoption trends, unresolved blockers, next-quarter plan, and executive decisions needed. For each metric, state its definition and whether it proves an outcome or only an activity. Add a discussion guide with questions for [ATTENDEES]. Do not overstate attribution or use confidential internal data in customer-facing material. Ask up to 3 questions only if required inputs are missing.
Tips
- Use customer-stated business outcomes as the anchor; a high login count is not a success measure unless it supports a desired outcome.
- Record dates and owners for every commitment in meeting follow-ups, and state approval dependencies plainly.
- Treat low usage as a diagnosis question, not a conclusion: segment by role, workflow, location, and implementation stage before acting.
- Keep product requests separate from committed delivery dates so account plans do not accidentally become roadmap promises.
FAQ
Can AI score account health?
It can organize a health assessment from the signals you provide, but the score should show its evidence and uncertainty. A single usage metric rarely captures renewal risk.
Can I use AI to draft customer follow-ups?
Yes, if you verify names, dates, commitments, and product claims. Keep unapproved pricing, security, legal, and roadmap statements out of the draft.
What should an account plan include?
It should connect the customer's goals, stakeholder roles, adoption evidence, risks, actions, owners, and decision timeline in one place.