Gtm Ai Adoption Rollout

---
name: gtm-ai-adoption-rollout
version: 1.0.0
description: |
  AUTO-TRIGGER: Apply this skill when the user is planning, executing, or
  troubleshooting an AI tool rollout for a sales or marketing team. Trigger
  phrases include: "rolling out AI to our team," "getting our reps to use,"
  "nobody is using the tool," "AI adoption is low," "how do I get buy-in,"
  "rolling out HubSpot," "Salesloft rollout," "ZoomInfo training," "tool
  adoption," "change management," or any request about getting a GTM team
  to actually use a new tool or workflow.

  Also trigger when the user is evaluating which AI tools to roll out, or
  when they have been given responsibility for a company-wide AI initiative
  without a clear implementation plan.

  Do NOT trigger for general AI tool comparisons, software procurement
  questions, or requests to learn how a specific tool works. This skill
  is about the organizational adoption problem, not the tool itself.
allowed-tools:
  - Read
  - Write
  - Edit
---

# GTM AI Adoption Rollout: Getting Sales and Marketing Teams to Actually Use New Tools

This skill addresses the gap between buying a tool and the team actually
using it. Most rollouts fail not because the tool is wrong but because
the adoption plan treats it as a training problem rather than a behavior
change problem. These are different problems with different solutions.

---

## HOW TO SET UP THIS SKILL

This skill works out of the box. For more specific output, provide:

- The tool or tools being rolled out
- The team size and composition (reps, SDRs, marketers, managers)
- Whether this is leadership-mandated or a bottoms-up initiative
- What the team is currently using and being asked to change from
- What has already been tried and failed
- Your timeline and any hard deadlines

---

## Why GTM Tool Rollouts Fail

Before building a rollout plan, diagnose which failure mode applies.
Most failed rollouts trace to one of five root causes.

---

### Failure mode 1: The tool solves a problem leadership has, not one the team has

Leadership buys a tool to get pipeline visibility or forecast accuracy.
The rep sees it as more data entry with no personal benefit. Adoption
fails because the incentive structure is inverted. The tool asks reps
to give something (their time, their process) in exchange for something
they do not personally receive (a dashboard the VP uses).

Fix: Identify one thing the tool does that makes the rep's job easier,
not just the manager's job more visible. Lead the rollout with that use
case. If no such use case exists, the tool has an adoption problem that
no training program will solve.

---

### Failure mode 2: Training was a one-time event, not a reinforcement system

The team attended a two-hour kickoff session, got a login, and was left
to figure it out. Within two weeks, 80% reverted to the old workflow.

Fix: Adoption is not a training event. It is a 90-day behavior change
program. The kickoff session gets people started. The first 30 days
builds the habit. Days 31-60 reinforces it under real conditions. Days
61-90 standardizes it and removes the workarounds. Each phase requires
different interventions.

---

### Failure mode 3: The rollout tried to change everything at once

The team was asked to learn a new CRM, a new sequencing tool, and a new
intent data platform in the same quarter. Cognitive overload produced
surface compliance, which looked like adoption in the first week and
collapsed by week four.

Fix: Sequence the rollout. One tool, one workflow, one team segment at
a time. Get the first group to true adoption before expanding. Their
success story is the most effective onboarding asset for the next group.

---

### Failure mode 4: The resisters were not identified early

Every team has three adoption profiles. Early adopters will use anything
new and evangelize it without prompting. The majority will adopt when
they see it working for someone they respect. Resisters will find reasons
the tool does not work for their specific situation and will actively or
passively undermine adoption.

Identifying resisters after the rollout fails is too late. They need to
be identified before launch and either converted or managed differently.

Fix: Run a pre-rollout audit. Ask the team directly: "On a scale of 1-5,
how useful do you think this tool will be for your day-to-day work?"
Anyone who scores 1 or 2 is a likely resister. Bring them in early. Give
them a voice in the implementation. Convert them into co-owners where
possible. Do not ignore them and hope training fixes it.

---

### Failure mode 5: No one owned adoption as a metric

The tool was purchased, the vendor ran a kickoff session, and then
ownership diffused. Marketing thought sales was managing it. Sales thought
IT was managing it. Nobody tracked usage data or intervened when numbers
dropped.

Fix: Name a single adoption owner with a defined metric and a 90-day
mandate. That metric is not "logins" or "licenses activated." It is a
behavioral metric: sequences sent per rep per week, contacts enriched per
week, deals updated per rep per week. Something that indicates the tool
is embedded in the workflow, not just installed on the laptop.

---

## The 90-Day GTM AI Adoption Framework

### Pre-launch (Weeks 1-2)

**Vendor dependency audit**
Clarify what the vendor will and will not do after the kickoff session.
Most vendors run a launch session and then hand off to a CSM who responds
to tickets. That is not an adoption plan. Document specifically what
internal ownership covers after the vendor's involvement ends.

**Tool configuration audit**
Before training anyone, confirm the tool is set up correctly for how
the team actually works. A sequencing tool with generic templates the
team did not write will not get used. A CRM with fields that do not
match the sales motion will be worked around. Fix the configuration
before training on it.

**Adoption profile mapping**
Identify early adopters, the majority, and resisters on the team.
Recruit two or three early adopters as internal champions before launch.
Brief resisters separately and give them a specific role in the rollout
(testing, feedback, edge case identification) that makes them feel
ownership rather than compliance.

**Success metric definition**
Define what 100% adoption looks like in behavioral terms. Not "everyone
has logged in." Specifically: what will reps be doing differently in 90
days, at what frequency, and how will you measure it.

**Workflow mapping**
Map the existing workflow step by step. Identify exactly where the new
tool fits. Define the new workflow with the same specificity. The gap
between old and new workflow is where resistance lives. Address it
explicitly before training.

---

### Launch phase (Weeks 3-4)

**The kickoff session structure**
Lead with the team's problem, not the tool's features. The first ten
minutes should be about the pain the tool addresses from the rep's
perspective, not from leadership's perspective. Show the tool solving
that specific pain. Walk through the first workflow in live demo format
with a real account, a real sequence, or a real deal.

Do not cover everything the tool can do. Cover the one workflow they
will use in their first week. Everything else comes later.

**Same-day activation**
Every rep should complete their first meaningful action in the tool
during or immediately after the kickoff session. Not just logging in.
Enrolling a real contact, updating a real deal, pulling a real record.
Same-day activation dramatically increases 30-day retention.

**Office hours, not help tickets**
Schedule two 30-minute optional office hours sessions in the first two
weeks. Drop-in format. No agenda. Reps bring their real questions from
real workflows. This surfaces the friction points faster than any
feedback survey.

---

### Reinforcement phase (Days 31-60)

**Usage data review**
Pull usage data by rep at the end of week four. Identify who is using
the tool as intended, who has started and stalled, and who has not
engaged. Do not wait for the quarterly business review to find out.

**Individual outreach for stalled users**
Reach out to stalled users individually, not with a group training
reminder. Ask what is getting in the way. Most stalls have a specific
cause: a workflow that does not apply to their accounts, a technical
issue they did not report, or a manager who is not reinforcing the
behavior. Each cause has a different fix.

**Manager enablement**
If managers are not reinforcing the tool in their one-on-ones and
pipeline reviews, adoption will stall regardless of the individual
training quality. Train managers on what to look for in usage data and
how to coach to the tool specifically. Not "are you using it?" but
"show me the sequence you sent to [specific account] this week."

**Public wins**
Identify one or two early adopter success stories by week six. A rep
who booked a meeting because of an intent signal, a deal that moved
because of a timely follow-up sequence. Share these in the team channel
with specifics. Generic praise does not drive adoption. Specific outcomes
from specific reps using specific workflows do.

---

### Standardization phase (Days 61-90)

**Workflow lock-in**
By day 60, the new workflow should be standard operating procedure, not
optional. This means building it into the onboarding checklist for new
hires, into the manager inspection criteria for pipeline reviews, and
into the team's definition of a complete record or a worked account.

**Workaround elimination**
Every team has people who found a way to do the old thing inside the
new system. They export data to a spreadsheet. They skip the enrichment
step and enter data manually. They mark deals complete without completing
the actual workflow. Identify the workarounds and address them directly.
Usually they indicate a configuration gap, not a training gap.

**Adoption review and next cycle planning**
At day 90, review adoption metrics against the success criteria defined
in pre-launch. Document what worked, what stalled, and what you would do
differently. If adoption is at 80% or above, the next tool or workflow
can be introduced. If it is below 80%, diagnose the remaining gap before
adding complexity.

---

## Deliver the Adoption Plan

Output in this format:

```
GTM AI ADOPTION PLAN
[Tool or tools being rolled out]
[Team size and composition]
Built: [today's date]

FAILURE MODE DIAGNOSIS
[Which of the five failure modes is most likely based on what the user
described. Be direct. If the rollout has already started and is failing,
name the failure mode that best explains what is happening.]

PRE-LAUNCH ACTIONS (complete before training anyone)
1. [Specific action with owner and deadline]
2. [Specific action with owner and deadline]
3. [Specific action with owner and deadline]

ADOPTION PROFILE MAP
Early adopters: [names or roles if known, otherwise criteria for identifying]
Likely resisters: [names or roles if known, otherwise criteria and approach]
Champion recruitment plan: [how to engage early adopters before launch]

SUCCESS METRIC
[The specific behavioral metric that defines 100% adoption at 90 days.
Not logins. A workflow action at a defined frequency.]

90-DAY ROLLOUT CALENDAR
Week 1-2 (Pre-launch): [specific actions]
Week 3-4 (Launch): [kickoff structure and same-day activation plan]
Week 5-8 (Reinforcement): [usage review cadence, manager enablement,
individual outreach triggers]
Week 9-12 (Standardization): [workflow lock-in, workaround elimination,
adoption review]

MANAGER COACHING GUIDE
[Three specific questions managers should ask in one-on-ones and pipeline
reviews to reinforce tool adoption. Not generic. Tied to this specific
tool and workflow.]

RISK FLAGS
[The two or three most likely reasons this rollout will underperform.
Based on what the user has described, not generic rollout risks.]
```

---

## Output Rules

- Base the plan on what the user has described. Do not invent details
  about their team structure, tool stack, or current process.
- If the rollout has already started and is failing, diagnose the failure
  mode before prescribing the fix. The diagnosis changes the solution.
- Be direct about whether the problem is the tool, the plan, or the team.
  Not every adoption problem is solvable with a better rollout plan.
- No em dashes. Use commas or periods.
- No generic change management language. Every recommendation should be
  specific to a GTM team adopting a sales or marketing technology tool.