Customer Success Workflow

Build a complete customer success management system via OpenClaw Ultra. From sales-to-CS handoff and structured onboarding to health monitoring, value reviews, renewal management, expansion, and churn intervention, run your entire customer success operation from a single chat interface.

Core System Overview

INFO

This is a closed-loop customer success workflow. OpenClaw Ultra handles account handoff, onboarding execution, health scoring, business reviews, renewal management, expansion identification, and churn intervention, so you can retain and grow your book of business without jumping between your CRM, CS platform, and inbox.

System Layer	Core Function	Final Output
Handoff Layer	Sales-to-CS transition, account setup, success plan creation	Onboarded account with documented success criteria
Onboarding Layer	Kickoff execution, implementation tracking, training, milestone management	Customer at first value with active engagement
Health Layer	Health score calculation, usage monitoring, risk signal detection	Scored portfolio with risk-ranked accounts
Value Layer	Outcome tracking, ROI documentation, QBR preparation	Documented value evidence and executive summaries
Renewal Layer	Pipeline management, stakeholder mapping, negotiation, contract processing	Signed renewals (ideally with expansion)
Expansion Layer	Opportunity detection, business case development, cross-sell coordination	Qualified expansion pipeline
Intervention Layer	Churn signal response, save plan creation, escalation management	Executed save plans with outcome tracking
Optimization Layer	Portfolio analysis, playbook refinement, process iteration	Improved retention and expansion rates

Prerequisites

Item	Requirement
OpenClaw Ultra	Installed and running
CRM Account	Active account with API access (HubSpot, Salesforce, Pipedrive, or similar)
CRM API Credentials	API key or OAuth token with read/write permissions
Customer Portfolio	List of managed accounts with contract terms and renewal dates
Product Usage Data	(Recommended) Access to product analytics or usage logs for health scoring
Support Ticketing	(Recommended) Access to support platform (Zendesk, Intercom, Freshdesk) for ticket volume data

Step 0 — Initialize Your Customer Success System

Set up OpenClaw Ultra as your dedicated customer success manager.

Operation Steps

1. Open OpenClaw Ultra new chat session
2. Gather your CRM credentials, portfolio data, and any CS platform integrations
3. Paste the initialization prompt

Ready-to-Use Prompt

Act as my customer success manager.

My company:
- Product: [product name]
- Industry: [industry]
- CRM platform: [HubSpot / Salesforce / Pipedrive / other]
- CRM credentials: [API key or token]
- CS platform: [Gainsight / ChurnZero / Totango / none]
- Support platform: [Zendesk / Intercom / Freshdesk / none]

My portfolio:
- Number of accounts: [count]
- Typical contract value: [$ range]
- Renewal cycle: [monthly / annual / multi-year]
- Average time-to-first-value: [days or weeks]

My biggest operational pain points:
- I manage [40-80+] accounts and spend most afternoons firefighting instead of doing proactive work
- Account context is scattered across CRM, support tickets, product analytics, billing, and spreadsheets
- I often build relationships with daily users but miss the executive sponsor who controls the renewal
- I own renewal and expansion targets but get little commercial training or negotiation support
- My current health score feels unreliable — it misses churn risks or cries wolf too often

Build a complete customer success management system that directly addresses these pain points. The system must:
- Surface only the accounts that actually need my attention this week (no noise)
- Pull fragmented data into one place so I don't have to check five tabs before every call
- Map executive sponsors and renewal decision-makers, not just friendly users
- Generate renewal and expansion packages with concrete talking points and counteroffers
- Use a health score built mostly on leading behavioral signals, not gut feel or lagging surveys

Step 1 — Onboard New Customers

Bring new accounts into the system and get them to first value fast.

1.1 Execute Sales-to-CS Handoff

Prompt

I have a new customer that just closed. Run a sales-to-CS handoff.

Customer details:
- Company: [customer name]
- Contract value: [$ amount]
- Term: [length]
- Stakeholders: [names and roles]
- Champion: [name]
- Implementation deadline: [date]

From the sales notes, I need:
1. What was promised during the sales cycle — features, timelines, support level
2. Their stated goals and success criteria for year one
3. Any red flags or concerns raised during negotiations
4. The technical setup requirements and who handles each piece
5. Key relationships — who advocated for us and who was skeptical

Because I have too many accounts to dig through scattered notes, create a single handoff record I can trust. For every missing piece, flag it as a data gap with the exact person or system I need to fill it, and do not make assumptions.

Create the initial account record in the CRM with:
- A verified CRM entry with all contract details
- A stakeholder map showing relationships and influence levels
- A handoff summary document for my records
- A list of data gaps that still need to be filled from sales

1.2 Run Kickoff and Build Success Plan

Prompt

Prepare a structured kickoff and 30-60-90 day success plan for [customer name].

Customer profile:
- Industry: [industry]
- Company size: [employees]
- Primary use case: [what they bought the product for]
- Decision criteria: [what they evaluated us against]
- Go-live date: [date]
- Integration requirements: [list any technical integrations needed]

The success plan must include:
- Week 1: Technical setup, user provisioning, admin training
- Days 8-30: Core use case enablement, first workflow live, first value milestone defined
- Days 31-60: Feature expansion, additional user onboarding, process integration
- Days 61-90: Full adoption, measurable outcome review, QBR scheduling

For each phase, specify:
- The concrete action the customer needs to take
- What successful completion looks like
- How we will measure it
- Who owns each action (us vs. customer)

Given my portfolio size, I cannot babysit every account. Build this plan so a customer can self-execute most steps with checkpoints, and I only intervene when a milestone is missed.

Return a calendar timeline with specific milestone dates and a shared tracking document.

INFO

Time-to-first-value is the single strongest predictor of retention. Customers who hit their first value milestone within 30 days retain at significantly higher rates. Structure every onboarding plan to compress this timeline.

Step 2 — Monitor Account Health

Build a system that continuously tracks account health and flags risks before they become churn. For lead qualification signals that feed into onboarding, see the AI SDR Workflow.

2.1 Set Up Health Scoring

Prompt

Build a health scoring model for my portfolio.

Available data sources:
- CRM: [HubSpot / Salesforce / other] — last activity date, deal history, support tickets
- Product usage: [source] — login frequency, feature adoption, session depth
- Support: [Zendesk / Intercom / other] — ticket volume, sentiment, response time
- Billing: [Stripe / Chargebee / other] — payment status, plan changes
- Survey: NPS / CSAT scores if available

Design a scoring model with:
1. Four health tiers: Green (on track), Yellow (attention needed), Orange (at risk), Red (critical)
2. Weighted signals — use 80% leading indicators (login frequency, feature breadth, stakeholder engagement) and 20% lagging indicators (NPS, CSAT)
3. Automated alerts when an account drops from Green to Yellow or below

For each tier, define:
- The specific signal thresholds that trigger that tier
- The recommended CSM action for accounts in that tier
- The escalation path if an account stays in Orange or Red for more than [X] days

I do not trust vague health scores. Calibrate every threshold to a behavior I can verify in the data, not a subjective score. Show me exactly how each account landed in its tier.

Apply the model to my current portfolio and return a ranked list from most to least at risk.

2.2 Run Weekly Health Scan

Prompt

Run my weekly portfolio health scan.

For each account, check:
1. Login frequency this week compared to baseline — flag any account below 70% of normal
2. Feature adoption — list features with declining usage across the portfolio
3. Open support tickets — flag accounts with 3+ open tickets or tickets older than 5 days
4. Stakeholder changes — any departures, new hires, or role changes at key accounts
5. Contract milestones — upcoming renewals, expirations, or price increases due

Return:
- Accounts that moved down a health tier since last week (with reason)
- Accounts that moved up a health tier (with reason)
- Accounts that need human attention this week (max 3 priority accounts)
- Any patterns across the portfolio I should know about

Do not give me a long list of every account. I have too many. Give me only the 3 I must act on this week, with the one specific action for each, plus the single portfolio pattern I should escalate internally.

Step 3 — Deliver Business Reviews

Connect product usage to measurable business outcomes and keep executive stakeholders engaged.

3.1 Prepare a Quarterly Business Review

Prompt

Prepare a Quarterly Business Review for [customer name].

Customer context:
- Account age: [months since go-live]
- Product: [product name and edition]
- Users: [licensed vs. active users]
- Annual contract value: [$ amount]
- Previous QBR outcomes: [notes from last review]

Data to pull:
1. Usage trends — login frequency, active users, feature adoption over the quarter
2. Support history — ticket volume, resolution time, common issues
3. Outcomes achieved — what they said they wanted vs. what they accomplished
4. Expansion signals — new use cases, new departments expressing interest, power user behavior
5. Risk signals — declining usage, stakeholder departures, unresolved escalations

Structure the QBR deck:
- Executive summary (one page): what happened, what it means, what we recommend
- Usage and adoption section with trend lines, not static numbers
- ROI section connecting usage data to business outcomes
- Joint success plan for next quarter with specific, measurable commitments from both sides
- Risk section if applicable — be direct about issues, don't bury them
- Stakeholder map update: identify the executive sponsor who controls the renewal and any new influencers or detractors

Return the full QBR script with slide-by-slide talking points.

WARNING

If you cannot document concrete ROI in a QBR, the renewal is at risk. Do not present feature adoption metrics as value — executives care about outcomes, not login counts. If the data shows the customer hasn't achieved measurable results, address it directly in the review rather than papering over it with activity metrics.

3.2 Document Account ROI

Prompt

Document the ROI achieved by [customer name] since onboarding.

Data to analyze:
- Time saved: compare pre-product manual process time vs. current automated time
- Cost reduction: any headcount reallocation, tool consolidation, or efficiency gains
- Revenue impact: any revenue generated through or because of the product
- Productivity lift: output per user before and after adoption
- Risk reduction: errors eliminated, compliance gaps closed, SLAs improved

For each category:
1. Pull the actual numbers from usage data and customer-provided metrics
2. Dollarize the impact where possible — time saved = hourly rate x hours
3. Use the customer's own stated goals from the kickoff as the benchmark
4. Flag any category where we don't have data — note what we need to track next quarter

Return a one-page ROI summary suitable for an executive audience. No jargon. Specific numbers. Clear before-and-after comparison.

Step 4 — Manage Renewals

Build a renewal pipeline that gives you 90 days of visibility and structured preparation.

4.1 Map the Renewal Pipeline

Prompt

Map my renewal pipeline for the next 90 days.

For each account renewing this quarter:
1. Contract details — current ARR, term length, start/end dates, auto-renewal terms
2. Health score trend — Green/Yellow/Orange/Red trajectory over the last 6 months
3. Champion status — is the original champion still employed and engaged?
4. Executive sponsor — who at the customer controls the renewal decision?
5. Usage trend — increasing, flat, or declining over the last 90 days
6. Open issues — unresolved product gaps, support escalations, pricing concerns
7. Competitive risk — any known evaluation activity or RFPs in flight

Return a ranked renewal pipeline sorted by likelihood to renew:
- Strong: Green health, active champion, documented value — no action needed beyond standard QBR
- Manage: Yellow health or champion changes — needs proactive executive engagement
- At Risk: Orange/Red health, declining usage, or known dissatisfaction — needs escalation now
- Unknown: Missing data on one or more critical signals — investigate this week

4.2 Prepare Renewal Package

Prompt

Prepare the renewal package for [customer name].

Account context:
- Current ARR: [$ amount]
- Current users: [count]
- Proposed renewal: [same / expansion / downgrade]
- Key wins this term: [list of outcomes achieved]
- Outstanding concerns: [any unresolved issues from the account]
- Decision maker: [name and title]
- Decision timeline: [date they need to sign by]

The renewal package must include:
1. A value summary — what they invested, what they got, dollarized where possible
2. What's changing in the new term — price, terms, features (if anything)
3. The proposed timeline for next term's initiatives
4. Pricing options — standard renewal and any expansion options

Negotiation preparation:
- Identify their likely objections based on health data and recent interactions
- Prepare counteroffers for each objection
- Define maximum discount authority and escalation path
- Because I am not a trained salesperson, give me the exact wording for the value conversation and when to bring in a deal desk or account executive

Return the full renewal package as a document ready to share, plus internal negotiation notes.

Step 5 — Drive Expansion Revenue

Identify accounts ready to grow and build the business case for expansion.

5.1 Identify Expansion Opportunities

Prompt

Scan my portfolio for expansion opportunities this quarter.

Signal types to detect:
1. Usage growth — accounts where active users or session frequency has grown 20%+ over last 3 months without a corresponding contract upgrade
2. Department spread — accounts where users span multiple departments but only one team is licensed
3. Feature ceiling — accounts that are heavy users of core features but haven't adopted premium modules
4. Positive NPS — promoters (score 9-10) who haven't been asked to expand
5. Organic mentions — accounts that have expressed interest in new use cases in support tickets or QBRs
6. Contract anniversary — accounts approaching renewal where expansion could be bundled

For each flagged account:
- The specific signal type and strength
- Recommended expansion action (upsell, cross-sell, seat expansion, multi-year)
- Suggested timing (now, next QBR, renewal)
- Revenue potential estimate
- The executive sponsor or budget owner to engage, not just the daily user

Do not flag accounts based on gut feel. Every opportunity must be tied to a verifiable usage, engagement, or contract signal.

Return a prioritized expansion pipeline with expected revenue and close timeline.

5.2 Build an Expansion Business Case

Prompt

Build an expansion business case for [customer name].

Expansion opportunity:
- Current product/plan: [current]
- Proposed expansion: [new product / additional seats / upgrade]
- Trigger signal: [what prompted this opportunity]
- Customer need: [what problem the expansion solves for them]

The business case needs:
1. The customer's current state — what they have, what they're missing, what the gap costs them
2. Quantified impact of the expansion — time saved, revenue gained, risk reduced
3. Expected ROI timeline — how long until the expansion pays for itself
4. Competitive context — are they evaluating alternatives?
5. Pricing recommendation — standalone vs. bundled with renewal
6. Internal notes — relationship health, key stakeholders, likely objections

Return the business case ready for internal review and customer presentation.

Step 6 — Intervene on At-Risk Accounts

Detect churn signals early and execute structured save plans. For retention email templates and follow-up automation, see the Email Outreach Workflow.

6.1 Run Churn Risk Assessment

Prompt

Run a churn risk assessment across my portfolio.

Risk signals to scan:
- Usage collapse — login frequency dropped more than 50% in the last 30 days
- Champion loss — known internal champion has left the company or changed roles
- Support escalation — 5+ tickets in 30 days or a critical escalation unresolved for 7+ days
- Negative survey — NPS score of 0-6 or CSAT below [threshold]
- Billing issues — failed payment or downgrade request
- Competitive activity — customer requested a security review, RFP, or referenced a competitor
- Stakeholder churn — multiple stakeholder departures at the customer in 90 days
- Silence — no login, no support tickets, no QBR attendance for 45+ days

For each flagged account, return:
- Risk score (high / medium / low)
- The specific signals that triggered the alert
- Recommended action within the next 48 hours
- Whether the situation can be handled by the CSM or needs executive escalation

If an account is silent (no logins, no support tickets, no QBR attendance) for 45+ days, treat it as high risk even if the survey score looks fine. Lagging indicators can lie; absence of leading behavior usually does not.

6.2 Create and Execute a Save Plan

Prompt

Create a structured save plan for [at-risk customer name].

Account situation:
- Risk signals: [list of specific signals and their severity]
- Root cause: [what went wrong — overpromised feature, poor support experience, pricing friction, competitor pressure, champion loss]
- Stakeholder status: [who is still engaged, who has disengaged, who controls the decision]
- Contract status: [months until renewal, auto-renewal terms]

The save plan must include:
1. Immediate action (next 48 hours) — who contacts whom, with what message
2. Short-term fixes (next 2 weeks) — product issues to resolve, features to deliver, support backlog to clear
3. Executive engagement — schedule a call with their executive sponsor and your manager or VP
4. Value recovery — revisit their original success criteria, document what was achieved, identify what was missed
5. Decision options — proposed resolution options from full remediation to contract adjustment
6. Drop-dead date — when to stop investing and let the account churn

Return the full save plan with owners and deadlines. Flag any resource or product commitments that need leadership approval.

Step 7 — Analyze Portfolio and Optimize Process

Review portfolio performance and refine your playbooks for the next cycle.

7.1 Run Portfolio Performance Analysis

Prompt

Run a portfolio performance analysis for this quarter.

Metrics to calculate:
- Gross Retention Rate — accounts that renewed vs. accounts up for renewal
- Net Revenue Retention — starting ARR vs. ending ARR including expansion and contraction
- Time-to-First-Value — average days from kickoff to first value milestone across all accounts onboarded this quarter
- Health score distribution — % of portfolio in each health tier this quarter vs. last quarter
- QBR completion rate — accounts that received a business review vs. accounts due for one
- Save plan effectiveness — accounts flagged as at risk vs. accounts that successfully saved
- Expansion conversion — identified expansion opportunities vs. closed expansion revenue

For each metric:
- Compare against last quarter
- Flag anything that moved more than 10% in either direction
- Identify the accounts driving the change (good and bad)

Return a one-page portfolio summary with the 3 biggest improvement opportunities for next quarter.

7.2 Refine Playbooks and Process

Prompt

Review my CS playbooks and recommend improvements based on this quarter's data.

Areas to analyze:
1. Onboarding playbook — are customers hitting first value faster now than last quarter? Which onboarding stages cause the most delays?
2. Health score model — did the current model correctly flag accounts that churned or contracted? Were there false positives that wasted time?
3. QBR template — which sections of the QBR drive the strongest renewal outcomes? Are we spending time on slides that don't matter?
4. Renewal process — what's the average time from first renewal conversation to signed deal? Where does the process stall?
5. Save playbook — which intervention types (executive call, product remediation, pricing adjustment) have the highest save rate?

For each playbook:
- What worked this quarter (keep)
- What didn't work (change)
- What we tried that failed fast (drop)
- What we haven't tried but should (test next quarter)

Return an updated playbook with specific changes, not general principles.

Step 7 Output

Data-driven process improvements flowing back into every stage of the customer success cycle.

Final Closed-Loop Customer Success Workflow

Account Signed → Handoff Executed → Onboarding Complete → Health Scoring Active →
Usage & Adoption Monitored → Business Reviews Delivered → Renewal Secured →
Expansion Identified → At-Risk Accounts Intervened → Portfolio Analyzed → Process Refined → Next Account

Practical Usage Tips

1. Track time-to-first-value for every new account and flag any onboarding that passes day 30 without a documented first value milestone — this single metric predicts more about retention than any health score
2. Health scores should use 80% leading indicators (login frequency, feature breadth, stakeholder engagement) and 20% lagging indicators (NPS, CSAT) — most CS teams get this backwards and react to churn after the customer has already disengaged
3. Always map the executive sponsor who controls the renewal decision, not just the daily user who likes your product — relationship theater with the wrong stakeholders is the most common blind spot in CS
4. Bundle expansion conversations with renewals rather than pitching them separately — a combined negotiation gives you more leverage and the customer a clearer total value picture
5. Send a health score summary to each customer before their QBR so there are no surprises in the meeting — the QBR should validate what they already know, not drop bad news
6. Set a save plan drop-dead date and stick to it — investing resources in an account that won't recover takes time away from accounts that will
7. For escalating complex issues to a dedicated support team, see Customer Support Automation
8. For tracking renewal dates and contract details through a structured pipeline, see CRM Sales Workflow