How I use Claude Code in client GTM work
Beyond the outbound agent stack: how Claude Code runs content operations, CRM hygiene, and research inside real client engagements: what the delivery model looks like from the outside.
GTM Architect & Growth Operator · Now · 25 May 2026
TL;DR · Key insights
- Claude Code runs three jobs in every engagement: outbound intelligence, content operations, and CRM data hygiene.
- The compounding effect is real: the fifth run on a client engagement is measurably better than the first.
- Clients see faster delivery and better drafts. They don't see the agent stack. That's the point.
Most people who’ve heard of Claude Code think of it as a coding assistant. That’s the smallest part of what it does in my client engagements.
I’ve embedded it into three parts of every GTM engagement I run: outbound intelligence, content operations, and CRM data. The result is a delivery model that didn’t exist two years ago, and one I can’t imagine going back from.
This isn’t about replacing the thinking. It’s about eliminating the overhead between thinking and shipping.
The three jobs it does
50-account list: cold CSV to scored accounts with drafted sequences in under an hour. CLAUDE.md context compounds across runs.
Audit phase reveals gaps. Draft phase is research-grounded, not template-based. Iteration loop is hours instead of weeks.
Consistent ICP classification at scale, flagged duplicates and missing data, reviewable reasoning before any CRM touch.
I use Claude Code for three distinct workloads, each with its own setup and logic.
Job 1: Research and outbound intelligence
I’ve documented the GTM agent stack in detail. Short version: Claude Code, four MCP tools, a CLAUDE.md operator brief, and five named skills handle the enrichment-to-draft pipeline. A 50-account list goes from cold CSV to scored accounts with drafted sequences in under an hour.
The piece I didn’t cover there: the compounding effect.
After three months on an engagement, the CLAUDE.md is dense with client-specific ICP signals, objection patterns, and sequence learnings. The fifth run is measurably better than the first. That doesn’t happen in Clay or Apollo. Those systems process rows. They don’t accumulate operator context.
Job 2: Content operations
Every GTM engagement touches content: the website, case studies, LinkedIn positioning, email nurture tracks. The gap between “we need to update the homepage” and “homepage is updated” is usually weeks of stakeholder cycles and writing back-and-forth.
With Claude Code, the workflow collapses:
- Audit phase:
/auditreads the current site, the competitor set, and the ICP brief. Returns a structured gap analysis with specific recommendations per section. - Draft phase:
/draft [section]: not from a template, from the audit findings. Each draft is grounded in what the audit surfaced, not what the writer assumed. - Iteration: I edit the draft. It observes what I changed and why. The next draft starts closer to the right answer.
The output isn’t perfect out of the gate. The baseline is research-grounded, and the iteration cycle is hours instead of weeks.
Job 3: CRM data operations
This is the most underrated use case.
Most B2B CRMs I walk into have the same problems: duplicate companies, contacts without companies, deals stuck at the wrong stage, custom fields nobody filled in. Cleaning this manually takes a researcher weeks and still comes out inconsistent, because humans apply the same rules differently on row 12 and row 412.
Claude Code with the HubSpot MCP does it differently:
Batch read + classify
Duplicate + gap detection
Human-reviewed updates
It’s not one-click. You still review and approve. But the classification logic is consistent and auditable.
The engagement model this enables
Traditional GTM engagement
6 weeks minimum
With agent stack
Faster delivery
Before: A GTM engagement meant scoping deliverables, assigning research tasks, writing briefs for writers, reviewing drafts, building sequences, managing CRM cleanup in parallel. Six weeks minimum, with constant orchestration.
Now: I scope around operator outputs: the enriched account list, the sequenced outreach, the positioned website copy, and the clean CRM. I deliver them faster with fewer dependencies on external resources.
This doesn’t mean I work alone. Clients are still in the loop on ICP definition, sequence tone, content approval. The judgment is mine and theirs. What’s gone is the research overhead and the writing latency.
What clients see and don’t
Clients see faster delivery and higher-quality first drafts. Sequences that reference actual account-specific signals rather than generic personalization. A CRM that reflects the ICP rather than historical chaos.
They don’t see the agent stack. That’s intentional.
The output speaks for itself. The tool is an implementation detail. A client doesn't need to understand MCP servers. They need sequences that book calls. That's the contract.
What separates a good run from a great one
Three things drive the difference between average output and output that actually ships.
- Context depth: a detailed CLAUDE.md with ICP signals, objection patterns, and account notes compounds across runs. Sparse brief = sparse output.
- Task density: richer source material yields sharper output. The agent amplifies quality; it doesn't manufacture it.
- Operator judgment at the centre: scoring logic, sequence strategy, and positioning decisions come from the operator. The agent executes faster and more consistently.
If you’re running GTM engagements and the bottleneck is research, writing, or CRM hygiene rather than strategy, reach out and I’ll walk through how it maps to your stack.
