What is a system of action in GTM?
A system of action is a GTM process whose routine steps run without a person. It reads from shared context someone keeps current, and one named person answers for whatever reaches a customer.
Where did the hours go?
In a 2026 Gartner survey, 210 sales leaders said AI saves each seller 4.8 hours a week, and 72% said their organization doesn’t reinvest the time. The survey doesn’t say where the hours went. Your own process can.
Each desk on your team got an AI tool, and the process is often the one the team ran before AI: someone researches the account, someone scores it, someone drafts, someone approves, someone sends. Follow one item through it and count the days it waits between people.
Source: Gartner, 2026 Sales Productivity in the AI-Enabled Era Survey (n=210 CSOs and senior sales leaders), as presented in the keynote “Reimagining Sales Productivity in the Age of AI,” May 2026.
A system of action changes the process, not the desk.
Every step needs a person’s yes or an owner with a check
Some steps need a person’s yes: a message written for one buyer, and anything that changes what a seller owns, such as a territory or a quota. The system drafts. A named person decides, message by message.
A message you send to many people works differently. A webinar confirmation or an approved nurture email is a template, and a named owner approves it once and answers for every send. Write down which of your messages are which.
Every other step needs an owner and a check. The check catches what looks wrong; the owner reads what it catches and fixes the cause. A check only works if someone wrote down what wrong looks like. With no check, the owner hears about it from a customer.
Mix them up and you get a bot speaking for the company, or a person approving every account score.


One of ours, from a job post to a sent email
As of · running since September 30, 2026
Ours starts when a company posts a seat for AI transformation in marketing or GTM, and ends when the first email to someone there goes out. Sam owns it from start to end.
| Step | What happens | The check or the person |
|---|---|---|
| Find the post | A scan reads the job boards of our top 100 accounts by fit and keeps titles that pair AI or agents with marketing, GTM or revenue. | A board that won’t load is recorded as failed, never as zero openings. |
| Read it | The posting’s body is scored against what we sell. The read is saved: what the seat owns, the phrases it uses, who it reports to. | Runs on its own. |
| Open the prospect | A read above the bar opens a prospect record and starts research and a draft deal room. | The room goes to the buyer only after Sam’s passes. |
| Find ways in | The system lists every way in it can find, each with its evidence: a connection, a teammate, a partner, the hiring manager. | It never ranks them. Sam picks, because he knows the history. |
| Draft | One email draft per person, using only what the system knows. Someone who has left the company gets a note asking for an alum’s view, not a pitch. | Each person’s current role is checked before the draft. |
| Send | The draft waits in Gmail. | Sam reads every word, edits and sends. Nothing sends on its own. |
It’s built to move two numbers: days from the post to the first email, and posts nobody acted on within seven days. Today Sam starts the scan by hand; the aim is a daily run. Our alerts, such as a Slack message when a buyer opens a sales room, are parts of systems like this one, not systems of their own.
We haven’t built onboarding, adoption, retention or expansion. Three of us run Fresh Context, and at our volume those processes don’t wait yet.
Why this column holds these three
On the AI x GTM map, systems of action are the right-hand side: builders read where the revenue plan is at risk and change the processes leaders own. GTM product thinking calls that build right.
This column covers three processes:
- Insights & Targeting: who to go after.
- Sales Acceleration: how sellers win the deals they’re in.
- Campaign Factory: how a piece gets from brief to live.
We picked these first because each runs weekly, crosses a team line where work waits, and reads straight from shared context, so we expect a stale fact to surface in days. That’s our reasoning, not a measured result. The map holds more: customer journey design, the engagement model, onboarding and adoption, retention and expansion.
Work toward a map where every process has an owner and a check, and every one reads the same shared context.
What leaders ask before they build one
- Isn’t a system of action just automation?
- It’s automation held to more: it covers a whole process rather than one step, a check catches what looks wrong, one named person owns it, and it reads from shared context someone keeps current. Without the owner and the check, it runs until it’s wrong.
- Can you buy a system of action?
- You can buy the parts: the models, the tools, the connectors. The process, the owner, the check and the context stay yours. A vendor can maintain them; your team still answers for what they produce.
- What happens when the owner leaves or changes jobs?
- The process loses its owner, and that’s a break, not a gap. Name the next owner before the handover and pass on the written description of what wrong output looks like. Until someone holds it, hold the steps that reach customers.
A system of action breaks in three places you can check
Stale context. The system reads context nobody keeps current and ships confident wrong work, faster. That’s context debt. Pick one fact your system quotes. Ask who last checked it against its source, and when.
No owner. Ask who owns the process from start to finish, then who owns each step that runs on its own. “The team” or silence is the break.
One desk made faster. Time one item across the handoffs, not at the desks. If the waits didn’t shrink, the process didn’t change.
A system nobody owns runs until it’s wrong, and nobody notices.
Your first one is already waiting
- Pick the process that feeds the number you care most about, and give it a start and an end: a new target account to a first meeting, say, or an approved brief to a live campaign.
- Follow five recent items through it. For each, write down every step where it waited, how many days, why, and where you found the evidence (the CRM’s timestamps, a ticket, someone’s memory).
- Write down today’s baseline: items a month, days from start to end, hours of people’s time, and how often the work gets redone.
- Run each wait through the stop conditions:
If this is true Then It sends a message written for one buyer, or changes what a seller owns, and no one is named to say yes Name that person first. Your team doesn’t own the process It waits. Settle who owns it first. The context it reads has no owner Give the context an owner first. Nobody can say what a wrong output looks like Write that down first. Without it there’s no check. You have no baseline Write down today’s numbers first. - Score each wait that passes from 1 to 3 on how often it happens, how many of its days are avoidable, and how directly it reaches the number. Agree what each score means before you start. Multiply. A wait with no evidence stays unscored until you find some; it never counts as low. Ties go to the wait nearer the number.
The wait at the top of that list is your first candidate. Before anyone builds, write down who owns the process from start to finish, what the check looks for, and which number should move.
