Claude Code publishes 4-step GTM playbook

Kirke Männik’s May 22 post on X offered a concise operating recipe for using Anthropic’s Claude Code in GTM and RevOps work. The framework was organized into four steps — Explore, Plan, Code and Commit — and was aimed at people building enrichment pipelines, CRM integrations, reporting tools and automation workflows. Männik said the method was designed for “GTM, B2B, and RevOps builds,” according to the post cited in the source brief. Anthropic describes Claude Code as an agentic coding system that can read a codebase, make changes across files, run tests and deliver committed code. ### What exactly did Männik publish? Kirke Männik’s post described a four-part workflow rather than a product launch. The sequence began with Explore, then moved through Plan, Code and Commit, according to the social briefing built from the X post. The social briefing said Explore included sub-agent mapping and a dependency scan. The Plan step was described as a no-code planning pass with acceptance criteria and “ultrathink,” while Code focused on step-by-step implementation with test verification. (anthropic.com) Commit was described as a review stage using sub-agents and style-matched commit messages, according to the same briefing. ### How much of that lines up with Claude Code itself? Anthropic’s documentation says Claude Code supports specialized subagents for task-specific workflows and context management. (anthropic.com) The company’s product page also says Claude Code can read codebases, make changes across files, run tests and deliver committed code. Anthropic said in an October 2025 product update that it had added SDK support for subagents and hooks for teams building custom workflows. That makes Männik’s references to sub-agent mapping and staged execution consistent with documented Claude Code capabilities, even though the four-step GTM playbook itself appears to be Männik’s own operating method rather than an Anthropic-published framework. (code.claude.com) ### Why is this showing up in GTM and RevOps circles? The social briefing tied the playbook to practical GTM tasks: enrichment pipelines, CRM integrations, client reporting tools and automation workflows. Those are the kinds of multi-step jobs that often span Salesforce, HubSpot, spreadsheets, APIs and internal scripts rather than a single application. Anthropic’s own positioning for Claude Code helps explain that fit. The company says the tool is an entry point to software development for builders without an engineering background, and says it can handle build, test, iterate and ship tasks from natural-language instructions. (anthropic.com) ### What is distinctive about the four steps? The most distinctive part of Männik’s outline was not the labels themselves but the controls inside them. The source briefing said Explore starts with mapping sub-agents and scanning dependencies before any build begins. Plan was described as a no-code stage with acceptance criteria, which pushes specification ahead of implementation. The Code and Commit steps added two more controls. The social briefing said Code relies on stepwise implementation with test verification, and Commit uses sub-agent review plus message formatting that matches an existing style. (anthropic.com) Those details place the workflow closer to software delivery discipline than to prompt-based experimentation. ### Is this an official Anthropic playbook? Anthropic has published documentation for Claude Code features such as subagents, autonomy controls and committed-code workflows, but the four-step GTM sequence in this story was attributed to Kirke Männik’s X post, not to Anthropic. Männik’s post, as summarized in the source briefing, also included audience-specific modules for GTM outbound systems, RevOps pipeline and reporting work, and B2B client integrations. The post told readers to comment “WORKFLOW” to get the full playbook, according to the briefing. May 22 is the date attached to the source briefing’s social item, and Anthropic’s current Claude Code documentation remains the main public reference point for the underlying product features. (code.claude.com) Readers looking for the original framework would need the X post from Kirke Männik and any follow-up material he distributes through that thread.