The people who win at that moment
We sit with the reps who handle your costliest decision best and write down what they do, including the steps they skip.
Repeatable AI procedures like “prep this call” or “draft this follow-up”, written from how your top performers work and loaded with your context.
The steps your top performer takes at your costliest buyer decision, run the same way by your newest hire.
Call prep and first drafts start from the argument that wins at that moment, whoever the buyer talks to.
One shared library in your repo. When we improve a skill, everyone gets the new version at once.
A skill is a short file your AI workspace loads when the job comes up. Illustrative: a pre-call planning skill. Companies, people and numbers are fictional.
| Part | What it holds | In Northwind's pre-call planning skill |
|---|---|---|
| Trigger | When the skill runs, in the words people use | “Prep my call with Hartwell Freight”, or a first meeting on tomorrow's calendar |
| Inputs | What it needs and where it gets it | The account and attendees, through one connector to your whole business |
| Context it reads | The files that make it yours | Northwind's ICP, the VP Operations persona file, past calls with this account |
| Playbook steps | Your best rep's approach, in order | List what changed since the last touch. Tie it to peak-season readiness: missed deliveries, overtime. Draft three questions and one proof point. |
| Examples | What good looks like, and what doesn't | Two briefs the top AE wrote, plus one weak brief that leads with route-optimization features, and why it's weak |
| Checks | What it confirms before handing anything back | Every claim cites a source. Names match the CRM. One page, no more. |
| Version and owner | Who changes it, and what changed | v7 in your repo, with a change log. Owner: enablement. |
We sit with the reps who handle your costliest decision best and write down what they do, including the steps they skip.
The arguments that moved buyers, pulled from the raw transcripts.
GTM strategyEach skill is written for the play we're shipping at that decision. We don't hand over a generic prompt library.
Skills read your warehouse and strategy files through one connector, so they start from what your best people know.
We write skills for the buyer decision that costs the most revenue, not the easiest demo.
Skills ship into your team's AI workspace with training on real accounts. Working versions in days.
When the read on a play changes, the owner edits the skill and the version number moves.
Enablement is plugin development now. Your enablement team owns the skill files and the examples of good, and we train them to change both.
Call prep, follow-ups and executive briefs.
Read moreFirst touches and account research.
Read moreAlways-on agents run the same skills, so people and agents follow one playbook.
The bootcamp ships the first skills for the play we build with your users. More come through Implementation or the AI operating partnership.
They can. A skill is a prompt made reliable: tied to your context, checked against real examples, and shared so everyone gets the improvement.
Choosing which job gets a skill. We find the buyer decision where you lose the most before anyone writes one. What we add for builders.
At most teams' volume, no. Each skill gets a written definition of good and a few real examples to check against. Heavier testing comes when volume justifies it.
A skill does one job when a person asks. An agent starts on its own, runs skills, and waits for a named person to approve. Most teams need skills first.
30 minutes. Tell us the buyer decision your team handles worst. We'll say which skills come first.
Book a call