Agent skill · marketing growth · github
gtm-enterprise-onboarding
Four-phase framework for onboarding enterprise customers from contract to value realization. Use when implementing new enterprise customers, preventing churn during onboarding, or solving the adoption cliff that kills deals post-go-live. Includes the Week 4 ghosting pattern.
Why this skill is useful
Provides a structured framework for enterprise onboarding that includes specific strategies to prevent customer churn and improve adoption, which the AI wouldn't reliably generate on its own.
What it needs
About 8k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Enterprise Onboarding Four-phase framework for onboarding enterprise customers from contract to value realization. The goal isn't just go-live — it's sustained adoption that doesn't cliff at Week 12. When to Use Triggers: "How do we onboard this enterprise customer?" "Customer went live but adoption is weak" "We keep losing customers 3 months after go-live" "POC to production transition" "How do I prevent Week 4 ghosting?" "Customer success onboarding framework" Context: Enterprise or mid-market deals Complex technical requirements Multiple stakeholders involved 30-90 day implementation timelines Risk of churn during first year --- Core Frameworks 1. The Week 4 Ghosting Problem (And How to Prevent It) The Pattern: Week 1: Kickoff call goes great. Everyone's excited. Week 2-3: Technical discovery, requirements gathering. Still good. Week 4: Customer stops responding. Meetings get cancelled. "Too busy." What Happened? You started customer onboarding before internal alignment on their side. Who Owns This Project Internally? Sales rep? (Already moved to next deal) Technical champion? (Day job took over) Executive sponsor? (Delegates, doesn't drive) Nobody? (This is why they're ghosting) The Framework: Internal Owner Validation Before kickoff call, answer: Who on customer side will: Attend weekly project meetings? (Not "invited" — will actually show up) Unblock issues with procurement/legal/security? (Has authority) Drive adoption with end users? (Has influence) Escalate when things stall? (Has executive access) If you can't name a specific person for each, you don't have a project owner. You have a signed contract with nobody driving it. How to Fix It: During sales → CS handoff (before customer kickoff): Sales rep must identify: Primary project owner (name, not role) Their capacity (dedicated or side project?) Their authority (can they unblock?) Their motivation (what's in it for them?) If there's no clear owner: Don't start onboarding yet. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/gtm-enterprise-onboarding