Gtm Enterprise Onboarding

A structured playbook for getting enterprise customers from signed contract to actual adoption without the typical Week 4 ghosting or Week 12 usage cliff. The framework walks through pre-kickoff validation (identifying internal project owners before you waste time), four implementation phases, and post-go-live retention tactics that most teams completely miss. The most useful part is probably the pre-onboarding checklist that forces you to confirm someone actually owns this project on the customer side before scheduling anything. Written by someone who has clearly watched too many enterprise deals die in the implementation phase because sales handed off a contract with no internal champion.

skills.sh installs: 1.6K
GitHub stars: 41K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add github/awesome-copilot --skill gtm-enterprise-onboarding --agent claude-code

Installs into .claude/skills of the current project.

Files

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.

SKILL.md on GitHub