startup-customer-success

Startup Customer Success

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "startup-customer-success" with this command: npx skills add vasilyu1983/ai-agents-public/vasilyu1983-ai-agents-public-startup-customer-success

Startup Customer Success

Retention and expansion systems for early-stage B2B products: turn “closed won” into realized value, keep customers, and expand based on outcomes.

When to Use

  • Designing onboarding and activation flows (time-to-value)

  • Building a support triage and escalation system

  • Creating customer health scoring and churn prevention playbooks

  • Renewals and expansion motions (with clear triggers and value proof)

  • Creating a Voice of Customer loop that feeds product and GTM

When NOT to Use

  • Help center information architecture and documentation taxonomy -> help-center-design

  • Closing and negotiation -> startup-sales-execution

Quick Start (Inputs)

  • Customer type: self-serve vs high-touch; contract size band

  • "First value" moment: what success looks like in 7/30/90 days

  • Product dependencies: integrations, data onboarding, admin setup

  • Current issues: churn reasons, support volume, activation drop-offs

Benchmarks (B2B SaaS 2025)

Metric Average Top Quartile

Annual retention rate 74% 90%+

Net Revenue Retention 100-105% 120%+

Onboarding dropout (week 1) 30-50% <20%

Time-to-value (median) 14-30 days <7 days

Expansion revenue share 20-30% 50%+ of new ARR

Workflow

  • Define success outcomes and time-to-value

  • For each ICP, define: success metric, activation events, and typical blockers.

  • Build onboarding in two layers

  • Self-serve: checklists, in-product guidance, fast support.

  • Assisted: kickoff call, MAP, implementation plan.

  • Install support triage and escalation

  • Severity levels, response targets, and ownership.

  • Prevent “support as chaos” by tagging and routing.

  • Create a customer health score (simple first)

  • Use assets/customer-health-score.md .

  • Combine: product usage, outcomes, support signals, and stakeholder engagement.

  • Run churn prevention and renewal playbooks

  • Use assets/churn-postmortem.md for every churned customer.

  • Start renewal conversations early for larger contracts.

  • Expand based on outcomes and triggers

  • Expansion triggers: additional team adoption, usage growth, new compliance needs.

  • Expansion proof: outcomes achieved and next outcomes enabled.

  • Close the loop to product and GTM

  • Monthly: top 5 customer problems, top 5 objections, and “what we should build/say.”

Metrics (Minimum Viable CS Analytics)

  • Time-to-value (median and p90)

  • Activation rate (by segment)

  • Support volume and time-to-first-response

  • Logo churn and revenue churn (if applicable)

  • Renewal rate (contracted customers)

  • Expansion rate (seat/usage/team growth)

AI and Automation in CS

  • Automated health score updates from product usage data

  • Triggered outreach: low usage, support escalation, renewal approaching

  • AI-assisted support triage (sentiment, urgency classification)

  • Predictive churn models using engagement signals

Anti-Patterns (Avoid)

  • Reactive-only CS: Waiting for customers to complain instead of proactive health monitoring

  • Manual health scoring: Quarterly spreadsheet updates instead of real-time signals

  • One-size-fits-all onboarding: Same flow for $500/mo and $50,000/mo customers

  • Individual-only activation: Tracking user activation without account-level view

  • Renewal surprise: First renewal conversation 30 days before expiration

Resources

Resource Purpose

onboarding-design.md Onboarding patterns and time-to-value design

support-triage.md Support workflow and escalation

cs-metrics.md CS metrics definitions and early benchmarks

health-scoring-guide.md Health score design, signals, models, and calibration

churn-prevention-playbook.md Proactive churn prevention and save offer frameworks

expansion-playbook.md Expansion triggers, motions, and pipeline management

renewal-management.md Renewal process, pricing strategy, and negotiation

voice-of-customer-program.md VoC program design, feedback collection, synthesis, and product loop

customer-segmentation-tiering.md CS touch model segmentation, tier design, and resource allocation

Templates

Template Purpose

onboarding-checklist.md Self-serve onboarding checklist

customer-health-score.md Health scoring starter

churn-postmortem.md Churn analysis template

qbr-outline.md QBR outline (for higher-touch accounts)

Data

File Purpose

sources.json Customer success references

Related Skills

Skill Use For

startup-growth-playbooks Retention-driven growth evidence and case studies

What Good Looks Like

  • You can state the “first value” moment and measure time-to-value for new customers.

  • Support issues feed product decisions through a visible loop (tags -> priorities).

  • Renewal risk is visible early through health signals, not discovered at cancellation.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Automation

product-management

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

marketing-visual-design

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

startup-idea-validation

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

software-architecture-design

No summary provided by upstream source.

Repository SourceNeeds Review