gtm-enterprise-onboarding

Implements a four-phase framework for onboarding enterprise customers from contract to sustained adoption.

38.5k|4.9k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill gtm-enterprise-onboarding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gtm-enterprise-onboarding
Source: https://github.com/github/awesome-copilot/tree/main/skills/gtm-enterprise-onboarding
Command: npx skills add https://github.com/github/awesome-copilot --skill gtm-enterprise-onboarding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enterprise customers frequently stall or churn after signing: Week 4 ghosting happens when no internal project owner exists, and the Week 12 adoption cliff kills deals when teams treat go-live as the finish line. This Skill provides a structured framework to prevent both failure patterns.

Core Features & Use Cases

  • Pre-Kickoff Validation: Checklists for sales-to-CS handoff, project owner identification, timeline realism, and internal readiness before the first customer call.
  • Four-Phase Onboarding Flow: Kickoff, Discovery & Planning, Implementation, and Go-Live & Sustained Adoption with agendas, deliverables, and parallel workstream guidance.
  • Adoption Cliff Prevention: Week-by-week value demonstration plan (value reports, user success stories, use case expansion) plus decision trees for diagnosing at-risk onboardings.
  • Use Case: A customer success manager notices a new enterprise account stopped responding in Week 4. Use this Skill to diagnose the missing project owner, escalate to the executive sponsor, and restart onboarding with a validated internal champion.

Quick Start

Use the gtm-enterprise-onboarding skill to build an onboarding plan for a new enterprise customer with a 60-day implementation timeline.

Frequently Asked Questions about gtm-enterprise-onboarding

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent enterprise customers from ghosting during onboarding?

Week 4 ghosting happens when no internal project owner exists on the customer side. Before kickoff, require sales to identify a named owner with capacity, authority to unblock issues, and motivation to drive the project weekly.

How do I prevent churn after enterprise go-live?

Treat go-live as the starting line, not the finish. Run a Week 7 value report, Week 9 user success story, and Week 11 use case expansion conversation, then track active users through Week 26 to catch the adoption cliff early.

What are the phases of an enterprise customer onboarding framework?

The four phases are Kickoff (Week 1, align on success metrics), Discovery & Planning (Weeks 2-3, technical and success planning), Implementation (Weeks 4-6, pilot deployment), and Go-Live & Sustained Adoption (Week 6+, rollout and value demonstration).

Should onboarding workstreams run sequentially or in parallel?

Run technical setup, training, and pilot tracks in parallel with separate owners and weekly syncs. Parallel execution cuts a typical six-week sequential timeline to three weeks and surfaces blockers before broad rollout.

When should I delay an enterprise onboarding kickoff?

Delay kickoff when no named project owner exists on the customer side, the requested timeline is unrealistic given technical requirements, or internal capacity is unavailable. Surface gaps to sales or the executive sponsor first.