Run the GTM loop on one workflow
Episode 1, made runnable. Do not automate the org chart. Run the loop on the workflow that costs you the most.
Run the GTM loop on one workflow
Episode 1, made runnable.
Do not automate the org chart. Run the loop on the workflow that costs you the most.
Details
Details
Details
Details
Final stage 25%+ faster
One workflow, named and rebuilt with an owner, not a new headcount line.
The real problem named at its crux
The right tech
Signals stacked to run it
The reps free to sell with the human kept in the loop
Your instinct is to fix GTM by adding a person. But the workflow that is bleeding you does not need another owner. It needs to be taken apart.
The workflow that solves it, one step at a time.
Each step is the plain question you are already asking. The skills answer them in order, one handing its receipt to the next.
Cuts past the symptom to the real workflow that is costing you, whether that is lead scoring, enrichment, or reps buried in prep, and names the real problem.
Picks the tools that move the data and the signals that tell the workflow who and what matters, so it runs on the right inputs. Not a buy-everything shopping trip.
Pulls the non-selling drag, scoring, enrichment, history, first-draft prep, off the rep plate so their time goes to actual selling. Not automation for its own sake.
Marks the points where a rep owns the judgment, who to pursue, the relationship, the message, and gives the workflow an owner and a weekly check so it lasts.
The real problem named at its crux, the right tech and signals stacked to run it, and the reps free to sell with the human kept in the loop.
- All 4 chained skills resolve to real, scored skills.
- Has a problem, an outcome, 2+ steps, and proof from a real build.
- Ships an example chat showing the play run in Claude.
- Reads in plain operator voice, grounded in a real build.
We did not just check the structure. A judge read this play against the full text of every skill it chains (composition), then ran it on a real scenario end to end (simulated). It passed both. Test scenario: RevOps lead at a 40-person startup where reps spend ~9 hrs/week hand-prepping accounts, and leadership is about to post a research-analyst req to fix it.
This play runs across the org, not inside sales.
Every function below owns a piece of the play. Skip one and it stalls where most GTM plays stall: in the handoff.
Without it: The loop runs on exports and dies in a month.
Without it: The drag comes back under a different name.
Without it: The build stalls at the first procurement question.
Watch the skills answer in order.
Describe your situation in plain language. The right skill fires on its own and hands its receipt to the next.
Before you run it, I ran it for real.
This workflow is genericized from a real build. Here is the number it moved, and what I actually did.
WHAT I DID ›
Speed in a deal is not pressure. It is removing the places a deal goes to wait. Find where your deals stall, then remove the wait, not the patience.
Dig into the full build →The loop is only as good as its named owner
The four skills hand the team one workflow named at its crux, staffed with tech, and stripped of drag; the payoff comes when a rep spends the recovered hours actually selling. Here is how a GTM leader runs the first loop so it earns the right to a second.
Pick a single workflow, name its owner, and review it weekly against three questions: is the crux still the crux, where did the human override the system, and what drag came back. Nothing else joins the loop until this one holds.
- 01Teach the crux read
Train the team to separate the symptom from the workflow problem underneath, the exact move solve-the-problem makes. A loop built on a symptom automates the wrong thing faster.
- 02Hold a weekly loop review
Fifteen minutes, same day each week: what the workflow produced, where it broke, what the owner changes next. The loop compounds on cadence, not on launch.
- 03Staff the judgment points
Keep-the-judgment marks where a human stays in; make sure each of those points has a name, not a team. An unowned judgment point is a silent failure waiting.
- 04Inspect the recovered time
Cut-the-drag frees hours; check where they actually went. If the reclaimed time is not showing up in selling activity, the loop is leaking somewhere else.
One plugin. 4 skills, bundled.
The whole playbook installs as a single plugin in Claude Code, no copy-pasting 4 times. Or grab any single step above. It runs on what you paste; connect your stack to go live.