A stalled-deal skill
The RevOps lead finds why one-contact deals stall at proposal and turns the answer into a skill AEs run.
How we work · What we build · Step 03
Your team opens AI that already knows the accounts
We set up Claude or ChatGPT, a Slack queue and coding agents for each role, connected to your data and loaded with the skills your first play needs.
Book a call30 min · no prep needed
What you're after
01
Good AI habits, shared
One setup per team, so nobody re-explains your product in their own chat window.
02
Answers from your data
AI that knows your accounts, your pipeline and your positioning before anyone pastes them in.
03
People who use it
Training on their own accounts and their own work, so the habit sticks.
One team's workspace, as we'd set it up
Illustrative. Companies, people and numbers are fictional.
Northwind's 20-person revenue team is starting one play: reach new VPs of Operations about peak-season readiness. We'd build on the CRM, sequencer and call recorder they have, for sales development and sales first.
Who gets what
| Role | Opens | Uses it for |
|---|---|---|
| 6 SDRs | Claude, Slack queue | Account research. First touches, each one approved by the rep. |
| SDR manager | Claude, Slack queue | Approves the peak-season argument. Reads the Friday play read. |
| 6 AEs | Claude, Slack queue | Pre-call planning and follow-up drafts |
| 3 CSMs | Claude | Renewal prep before peak season |
| Marketing lead | Claude | Page and email copy from the approved argument |
| RevOps lead and enablement lead | Claude Code and Claude | The power users. They change skills, query the warehouse and build workflows. |
| VP Sales | Slack | One weekly post: what the play moved, against comparison accounts |
What's connected, and how
Read-only to start. Write access is added one workflow at a time, when the play needs it.
| Source | Access |
|---|---|
| Warehouse | Read, through one connector every person and agent uses |
| CRM | Read. Writes only the follow-up tasks the play creates. |
| Sequencer | Read. Enrolls a contact only after the rep approves the first touch. |
| Call recorder | Read, raw transcripts |
| Website and product usage | Read, through the warehouse |
| Not connected | Billing, HR and support tickets. The play doesn't need them. |
Skills installed on day one
Five skills, all for the first play. Nothing generic.
| Skill | Who runs it | What it reads |
|---|---|---|
| account-research v1 | SDRs and the morning agent | The account timeline, the new-hire signal, past touches |
| first-touch-draft v1 | SDRs and the morning agent | The approved argument and the VP Operations persona file |
| pre-call-planning v1 | AEs | Past calls, the persona file, the open deal |
| call-follow-up v1 | AEs | The transcript and the next step agreed on the call |
| ask-the-data v1 | Everyone | The warehouse, for questions like “which accounts went quiet after a demo?” |
What's in the Slack queue at 7:30
An always-on agent runs before the team starts. One morning, for one SDR and one AE:
| Item | For | What they do |
|---|---|---|
| 3 new VPs of Operations at target accounts, each with a brief and a draft first touch | The owning SDR | Edit, approve or hold each one |
| 2 accounts with 2+ pricing-page visits this week | The owning SDR | Decide whether to call today |
| A one-page brief for each of today's 4 meetings | The AE | Read before the call |
| 2 follow-up drafts from yesterday's calls | The AE | Approve or edit |
| Fridays: touches, replies and meetings, against comparison accounts | SDR manager, VP Sales | Keep, change or retire the play |
Why AI seats haven't changed how people work
Every rep should be a manager. No first draft should start from a blank chat window.
Seats bought and handed out
- Left to each person to figure out
- Everyone writes their own prompts
- No connection to your data
A workspace set up with you
- Set up per role, with your data and strategy
- Shared skills everyone runs the same way
- Training until the habit sticks
What the power users build by month two
Better examples
Enablement reads the week's approval edits and rewrites the examples in first-touch-draft, now on v4.
Where to start
GTM AI Bootcamp
Every bootcamp sets up the workspace for the team running the first play and trains them on it. See our process.
Before you book
We already pay for Claude or ChatGPT. Do we need a new tool?
Usually not. We set up what you have: paid commercial tiers with no-training terms, or your own enterprise AI accounts.
Why not use the AI inside our CRM?
AI inside each GTM tool sees only that tool's data, so reps copy and paste anyway. The CRM stays your record, and the workspace reads it.
Who keeps it running after you leave?
Your RevOps and enablement leads, trained on it while we build.
Where's your line stuck?
Plan your team's AI workspace
30 minutes. Tell us who's on your team and what they use. We'll sketch the first workspace.
Book a call