gtm-enterprise-onboarding

This skill provides a four-phase framework for onboarding enterprise customers, focusing on preventing common pitfalls like Week 4 ghosting and the Week 12 adoption cliff. It includes checklists for pre-kickoff validation, meeting agendas, and strategies for parallel implementation tracks.

1.4K
Installs
5
Use cases
5/10
Quality

Is gtm-enterprise-onboarding safe to install?

Safe to install

Safe to install: our audit of gtm-enterprise-onboarding's source files found 0 shell commands, 0 external URLs, no file writes (none risk). Every command and URL listed appears verbatim in the skill's source. The skill provides a text-based framework and checklists. It does not execute code, access the internet, or modify local files.

How we audit skills: our security review methodology.

Who is this skill for?

Customer Success Managers, Implementation Specialists, and Account Executives managing enterprise or mid-market customer onboarding.

What can you do with it?

  • Implementing new enterprise customers
  • Preventing churn during the onboarding process
  • Solving the adoption cliff post-go-live
  • Managing POC to production transitions
  • Identifying and resolving Week 4 ghosting patterns

How good is this skill?

Quality score: 5/10. The skill is well-structured, provides actionable frameworks, and clearly defines triggers and common mistakes. It is highly specific to the enterprise onboarding domain.

What does the skill file contain?

SKILL.md
# 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 invol...

Frequently asked questions

How does this framework prevent Week 4 ghosting?

It mandates the identification of a specific project owner on the customer side before the kickoff call, ensuring someone has the authority and motivation to drive the project forward.

What is the recommended approach to shorten implementation time?

The skill suggests running technical setup, training, and pilot tracks in parallel rather than sequentially to shorten time-to-value and maintain customer engagement.

What should be done if a customer has no clear project owner?

The framework advises against starting onboarding. Instead, it suggests having sales introduce the team to an economic buyer to identify a project owner who can unblock issues and drive adoption.

How does the framework address the Week 12 adoption cliff?

It shifts the focus from go-live as a finish line to a starting line, emphasizing ongoing value demonstration through value reports, user success stories, and use case expansion conversations between weeks 6 and 26.

Data sourced from github/awesome-copilot on GitHub. Install counts from skills.sh. The summary and security audit are derived from the skill's source files: every command and URL listed appears verbatim in the source.

Related skills