Gtm Enterprise Onboarding
Run a four-phase enterprise onboarding playbook from contract kickoff through value realization so adoption does not cliff after go-live.
Overview
GTM Enterprise Onboarding is an agent skill most often used in Grow (also Ship launch prep, Operate support) that guides four-phase enterprise customer onboarding from contract to sustained adoption, including the Week 4
Install
npx skills add https://github.com/github/awesome-copilot --skill gtm-enterprise-onboardingWhat is this skill?
- Four-phase framework from contract to value realization with Week 4 ghosting prevention
- Week 1–4 adoption cliff pattern and stakeholder engagement tactics
- POC-to-production transition guidance for 30–90 day implementations
- Multi-stakeholder enterprise and mid-market onboarding triggers
- Churn-risk framing for weak adoption three months after go-live
- Four-phase onboarding framework
- Week 4 ghosting pattern
- 30–90 day implementation timelines
Adoption & trust: 1.3k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You closed the enterprise deal and went live, but stakeholders go quiet by week four and adoption collapses before renewals.
Who is it for?
Solo founders or tiny CS/sales teams onboarding complex B2B accounts with 30–90 day implementations and multiple stakeholders.
Skip if: Pure pre-sales discovery with no signed contract, or B2C self-serve onboarding with no human implementation track.
When should I use this skill?
Implementing new enterprise customers, preventing churn during onboarding, solving the adoption cliff post-go-live, or POC-to-production transitions.
What do I get? / Deliverables
You get a phased onboarding plan with anti-ghosting checkpoints so customers reach value realization instead of churning three months after launch.
- Phased onboarding plan
- Anti-ghosting cadence and checkpoints
- POC-to-production transition outline
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Grow/lifecycle because the framework starts after the deal closes and focuses on sustained customer adoption, not pre-sale validation. Lifecycle is where onboarding, handoffs, and post-go-live success live in the solo-builder journey once product is shipped.
Where it fits
Define what CS must deliver in the first 30 days before marking an enterprise tenant production-ready.
Run the four-phase framework after contract sign to keep champions engaged past week 4.
Scope implementation timelines and stakeholder maps before committing to a 90-day enterprise rollout.
How it compares
Use for post-sale enterprise motion and adoption cliffs—not for writing landing pages or technical API integration skills.
Common Questions / FAQ
Who is gtm-enterprise-onboarding for?
Indie SaaS founders, technical founders wearing customer success, and small teams implementing enterprise or mid-market customers after contract sign.
When should I use gtm-enterprise-onboarding?
Use when kicking off a new enterprise customer, fixing weak adoption after go-live, planning POC-to-production, or when deals die around week 4 silence; also when shaping Ship launch handoffs into Grow lifecycle playbooks.
Is gtm-enterprise-onboarding safe to install?
It is procedural GTM guidance with no shell or API requirements; review the Security Audits panel on this page before installing from the marketplace.
SKILL.md
READMESKILL.md - Gtm Enterprise Onboarding
# 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. Have sales introduce you to economic buyer: "Before we kick off implementation, we want to make sure we have the right project owner on your side. In our experience, implementations succeed when someone owns driving this forward week-to-week. Who on your team should we partner with?" **Common Mistake:** Assuming someone will own it. Ask explicitly. If they can't name someone, the deal is at risk. --- ### 2. The Adoption Cliff (Week 12 Problem) **The Pattern:** Go-live happens Week 6. Usage spikes. You celebrate. Week 8: Usage plateaus. Week 10: Usage declining. Week 12: Usage down 50% from peak. **Why This Happens:** You treated go-live as the finish line. **Go-live is the starting line.** **What Drives Sustained Adoption:** **Not:** Feature completeness, technical integration, training sessions **Yes:** Ongoing value demonstration, user success stories, expanding use cases **Framework: Adoption Stages Beyond Go-Live** **Week 1-6 (Implementation):** Get it working - Measure: % of technical setup complete - Owner: Technical lead **Week 6-12 (Initial Adoption):** Get people using it - Measure: # active users, frequency of use - Owner: Enablement / DevRel **Week 12-26 (Sustained Adoption):** Prove ongoing value - Measure: Use case expansion, team spread - Owner: Customer success **Week 26+ (Expansion):** Grow within account - Measure: New teams, new use cases, upgrade triggers - Owner: Accoun