customer-success-getting-started

$npx mdskill add Significant-Gravitas/skills-catalog/customer-success-getting-started

Use this before scoring accounts or drafting outreach.

SKILL.md

.github/skills/customer-success-getting-startedView on GitHub ↗
---
name: "customer-success-getting-started"
description: "Set up customer success work from agreed outcomes, account evidence, owners, dates, and clear approval rules."
triggers: ["customer success setup", "start customer success", "account management", "retention process", "customer portfolio"]
version: "1"
---

# Customer success getting started

Use this before scoring accounts or drafting outreach.

## Define success

Ask for the customer segments, stated outcomes, onboarding stages, product
signals, support records, relationship owners, renewal dates, notice periods,
and approved communication rules. Record the system, field, date range, and
last refresh for each source.

## Set the working rules

Agree which measures describe adoption, outcomes, support, relationship, and
commercial readiness. Define missing-data handling and who may approve an
external message, offer, term, or product commitment.

## Return the setup brief

Give the user:

1. Accounts and period in scope.
2. Source map and stale or missing fields.
3. Agreed success and risk signals.
4. Renewal and onboarding deadlines.
5. The first three account reviews, with reasons.

Never fill a data gap with a guess. Do not send outreach, edit customer
records, promise an outcome, or treat silence as proof of health.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.