Is the Claude Hype Real? We Asked 200 GTM Operators.
New data from the 2026 Claude for GTM Pulse Report
This newsletter is kindly supported by Attio - the AI-native CRM built for modern GTM teams. If you’ve ever battled a rigid legacy CRM, Attio fixes that with clean data, real-time visibility, and workflows that actually speed you up.
Today, 5,000+ fast-moving companies rely on Attio’s flexible data model, modern design, and builder-friendly setup to shape their CRM around how they work - not the other way around. It’s built for founders, revenue ops, and GTM teams who need a system that adapts as fast as we do.
So if 2026 is the year you finally break up with your legacy CRM or start fresh on a new project, this is the perfect moment to take Attio for a spin.
Dear GTM Strategist,
Claude mania has taken the GTM AI space by storm in Q1 2026. People who have never written a line of code are now spending their nights and weekends staring at a console, shipping GTM systems that used to require a full engineering sprint.
And Anthropic, the company behind Claude, just crossed $30B in ARR - in record time:
But is the hype real? Are GTM operators actually getting value from all their cool builds, or are we entering another “crypto” era - lots of talk, energy, questionable ROI?
Time to find out.
Kyle Poyar (Growth Unhinged) and I surveyed 200 GTM AI operators and curated their best insights into the 2026 Claude for GTM Pulse Report, focusing on how they use Claude Cowork and Code, the value teams get from these tools, and their limitations.
In this article, I am presenting my 5 key takeaways from a 37-Page report:
Claude Cowork is not (just) Claude Code for Dummies. Claude Code and Cowork split GTM operators almost 50/50, but they are not complete substitutes.
80% use Claude for productivity. Content creation (29%) and GTM engines (23%) deliver the most impact at the moment, but it feels like we are just scratching the surface of what is possible.
GTM engineers are wiring Claude Code into stacks and systems, not using it solo but in combination with other tools. Most common use cases so far: 79% are building SDR research tools and 71% adapting messaging dynamically by segment.
92% reported that Claude Code and Cowork help them “save time”, but more interestingly, 67% have reported building workflows that were previously impossible. But just 27% have replaced a GTM tool so far - the SaaS apocalypse crowd might be getting ahead of the data.
But nothing is perfect - even Claudes. Anthropic is a pretty savvy monetizer - even Max plan ($100-$200/month) users hit credit walls 2-3x a day. Memory loss, integration gaps, and a lack of team skill-sharing round out the list of frustrations. We’ve also gathered some intel on how best-in-class users bypass these limitations.
A massive thank you to every community member who participated in the survey 🙏 - this article would not have been possible without you. You are the best!
Want more insights?
Here you go.
Insight 1: Is Cowork Just Claude Code for Dummies?
When Anthropic introduced Cowork in January 2026, my first reaction was: “OK, this is Claude Code for people who don’t want to open the terminal.” I was somehow wrong. We went ahead and bypassed Cowork to go all in on Claude Code, but after talking to colleagues who built legitimate, serious use cases in Cowork, I revised my opinion.
For example, one of the well-known Substackers in my circles let go of three VAs because Cowork could just absorb their workload for content research and repurposing.
Cowork is not just a lite version of Claude Code - it is a different tool optimized for a different kind of work, and it feels like they are just getting started, so we should not dismiss them as some “inferior version” of Code.
Our data backs this up: just three months after launch, Cowork (32%) has already surpassed Claude Code (31%) as the primary Claude product among GTM operators we surveyed.
Claude Chat sits at 30%, and many of us use all tools at the same time, which tells you something important: there is no “one to rule them all” - they do different things in different time and cost differently - here is a quick breakdown on when to use each.
A reality check: this survey sample skews toward advanced users, so the share of Claude Chat users in the broader population is much higher. Don’t let the numbers intimidate you - use them as inspiration instead.
The core insight from the data: 93% of Claude Code users rely on detailed company context1 as a core foundation, vs. 72% of Cowork users. That gap tells you who is building a compounding system and who is running sophisticated tasks.
For advanced users: The other thing where Claude Code outshines its siblings is interconnectivity with other tools for complex use cases and GTM systems. If we are somehow limited with native apps and MCPs within chat and Cowork, CLIs and API integrations fuel powerful, customizable Claude Code builds at optimized costs. Bring agents into the mix and you can unlock the kind of agentic AI systems Canva, Descript, and Linear have built2.
Insight 2: Most Teams Are Still in Productivity Mode - but #1 Use Case is Content
The most widely adopted use case is productivity at 80% - analyzing data, preparing for meetings, and creating documents. Content creation comes in second at 69%, followed by product marketing at 64%.
That is the adoption story. But here is the more interesting cut: which use case do people say has the biggest impact?
Content creation jumps to #1 impact at 29%, while productivity drops to 15% despite leading on adoption. GTM engines punch way above their adoption weight, cited as the #1 impact use case by 23% of respondents despite only 54% adoption.
Long story short: people use Claude most for productivity, but they get the most value from content and GTM engines. Specifically, Claude Cowork shines for content creation, while for Claude Code users, GTM engines are the primary use case.
Within content, the top workflows are:
Creating social media posts (72% of content users)
Building websites, landing pages, and micro-sites (66%)
Creating structured content pipelines (52%)
Auditing SEO performance (38%)
Analyzing traffic and content performance (34%)
The thing that separates content in Claude Code/Cowork from content in Claude Chat is context engineering. With Code or Cowork, you can encode your brand voice, your ICP, your top-performing posts, your sponsor briefs - and Claude pulls exactly what is relevant for the task at hand. The more you feed the system, the better the output gets.
But remember - with AI content creation, it is often “garbage in, garbage exponentially out”. Strategic narratives and unique points of view are more important than ever:
Without something original to say, the best architecture in the world just produces polished noise. The system amplifies your point of view. It does not create one for you. - Amos Bar-Joseph, CEO at Swan AI
To help make LinkedIn a better place for the intelligent carbon life still being there, I am sharing a core idea of how we structured the content system in our Claude Code. It is already producing amazing LinkedIn pieces (still human edited!) - design briefs are OK but need final touch and AEO/SEO. Well, we still have room for improvement there - so if you have some advanced builds, send them my way, and I’ll consider sharing them in our future content.
Now back to survey results:
Insight 3: GTM Engine Builders Are Playing a Completely Different Game
The 54% of operators using Claude for GTM engines are not just doing things faster. They are building workflows that did not exist before. Here is what the top GTM engine use cases look like:
What makes this category different is the combination of tools. GTM engine builders are not using Claude in isolation. They are wiring it into a stack. The tools that Code and Cowork users love the most are ChatGPT (#1, mentioned by 26% of respondents), Clay (#2 at 21%), HubSpot (#3 at 19%), LinkedIn (#4), and Apollo (#5).
The top GTM AI tool stack in 2026 is Claude + CRM + orchestration. These tools are not competing. They are combining.
Claude handles the intelligence layer. Clay handles data enrichment and workflow automation. It connects the CRM layer. LinkedIn and Apollo feed the signals. The builders who get this are not asking “which AI tool should I use?” They are asking “how do I architect a system where Claude sits at the center, reads my context, connects to my stack, and runs while I sleep?”
Insight 4: Show me the money - what value are users getting from Claude
Every reasonable human being at this point feels like - OK, sounds like an interesting opportunity, but it does take a lot of work and changes. Is it worth the trouble or are GTM nerds just raving to each other to have something new to say? In other words - is the hype real?
Respondents are practically unanimous (92%) that Claude Code and Cowork have saved them time. But what really sparked my attention is that 67% said that it enabled them to do something previously impossible. Enabling previously impossible workflows is a different category of value - that is where compounding GTM intelligence lives.
What’s really interesting is whether Claude replaces existing tools. 55% of respondents said yes, but the breakdown was more intriguing.
Lower qualified work and non-core contractors have taken the larger hit so far 😢 - remember the Substack guy who could fire 3 VAs (yeah, that is the spiel ATM)? While having a good content person is invaluable, it is mission-critical to learn AI for the lower-qualified tasks. I’ve been saying that to every young person out there: if you cannot compete on quality yet, compete on speed and productivity - make AI your bestie.
On the tool replacement side, only 27% have replaced an existing GTM tool so far, 30% say they will soon, and 43% say no. Most at risk are contractors, SEO agencies, ad agencies, spreadsheets, manual outbound work, ChatGPT, Perplexity, analytics providers, and third-party automation tools.
Some are loudly predicting a SaaS apocalypse driven by vibe coding. Considering previous findings, this is not exactly true. I personally believe in combining the tools with strong ecosystems into new stacks that empower GTM systems.
Insight 5: The Frustrations Are Real, Documented, and Partially Fixable
This section exists because Emily Kramer (MKT1 Newsletter) suggested we ask about frustrations when she reviewed our survey. Best suggestion we got. The responses were juicy.
The reported limitations of Claude, ranked by number of mentions:
Credits, cost, and usage limits - running out of credits, throttling, usage limits even on the Max plan, unpredictable usage on small tasks.
Memory limitations - losing context between sessions, no persistent long-term memory, manual workarounds required.
Context window and token limits - running out mid-task, large operations failing, duplication across sessions.
Integration and data gaps - weak Google and Salesforce integrations, limited connectors, restricted access to company data sources.
Reliability and consistency - hallucinations, shallow outputs, inconsistent results across sessions.
Team collaboration - skills are not easily shareable, updating a skill does not cascade to teammates, poor team workflow support.
“I’m on a Max plan and I still run into model usage restrictions 2-3x per day.”
“If a coworker comes up with a skill that’s useful, we’ll have to build the skills separately rather than sharing.”
Some practical “hacks” that help:
Open new chats regularly instead of continuing long threads - reduces context bloat
Ask Claude to plan before executing - use plan mode before burning tokens
Move from MCP to CLI or direct API calls for reliability - ScaleKit benchmark data shows CLI hits 100% reliability vs around 72% for MCP, at a fraction of the token cost
Mix Sonnet model into your workflows instead of Opus for simpler tasks - it is about 20% of the Opus cost
Build an external memory system - a CLAUDE.md or history.md file Claude updates proactively
Test on a small sample before running full campaigns - do not burn credits on untested logic
To improve output quality, ask Claude to critique itself before you accept the output
“The biggest trap with Claude (or any LLM) is that it’s a yes-man by default. You bring it a plan and it’ll tell you it’s brilliant, maybe suggest a few tweaks around the edges. That’s not useful. I started building a habit: create the plan in Claude, then explicitly ask it to red team the thing.” - Andy Nester, CMO at PERSUIT
In the Future, Everybody Will Be an Engineer
In 1968, Andy Warhol famously said, “In the future, everyone will be world-famous for 15 minutes.”
In GTM AI in 2026, the equivalent might be: in Q4 2025, everybody became a ______ engineer (place your buzzword of choice to fill in the blank).
The trend started with the GTM engineer role, then the term content engineering started trending; oh, and have you ever heard of vibe coding? And just last week I heard about a marketing engineer for the very first time. It’s getting really hard to catch up with all the new engineers - it used to be easy (front-end/back-end). 🙈
It’s an incredibly exciting time to be building in this space and if these strategic narratives usually get great buzz on social media - so by all means, do it - but is all these engineering making non-technical people anxious, excluding women (lower representation in the engineering skill pool) and turning off competent operators who actually know their s*** and favoring tool jockeys instead?
Maybe …
But there are a lot of great things going on in the space, too. There are great companies, teams, solo contributors and content creators pushing the space forward. And sometimes that means having a critically acclaimed discussion or open-sourcing something outside the comfort zone.
I feel we are just getting started here and that Claude’s domination will continue throughout 2026. 🤞 So please keep track of what is new in the space and share your best practices.
The gap between AI power users and those who use GPT chat to prompt outbound emails and blog posts is getting wider and wider, and while you are still early in the space, the AI-powered teams are a force to be reckoned with, not something to smirk at.
Kyle and I hope this report is a high-quality contribution to what is actually happening with Claude in GTM - not just another hype piece. If it was useful, hit that heart on Substack - it helps me convince Kyle to do more of these collaborations 😉.
The full 37-page “Claude for GTM Pulse Report” is available to premium subscribers of Kyle Poyar’s newsletter. It includes more survey data and insights on Claude Code and Cowork adoption, how top GTM teams use Claude, limitations to be aware of, and advice to get the most out of Claude.
And if you like what I do and want to support my free content stream, you can do that by buying my digital solutions 👇
✅ Need ready-to-use GTM assets and AI prompts? Get the 100-Step GTM Checklist with proven website templates, sales decks, landing pages, outbound sequences, LinkedIn post frameworks, email sequences, and 20+ workshops you can immediately run with your team.
📘 New to GTM? Learn fundamentals. Get my best-selling GTM Strategist book that helped 9,500+ companies to go to market with confidence - frameworks and online course included.
📈 My latest course: AI-Powered LinkedIn Growth System teaches the exact system I use to generate 7M+ impressions a year and 70% of my B2B pipeline.
🏅 Are you in charge of GTM and responsible for leading others? Grab the GTM Masterclass (6 hours of training, end-to-end GTM explained on examples, guided workshops) to get your team up and running in no time.
🤝 Want to work together? ⏩ Check out the options and let me know how we can join forces.
Learn more about context engineering here - arguably one of the most important GTM AI concepts in 2026.
Get the full guide here.
Claude's take on Claude:
"A few things in that table land cleanly, and a few are off in ways worth flagging.
**What's right**
The basic axis — Chat for thinking/writing, Cowork for operational execution, Code for building systems — is a fair mental model. "Setup needed" scaling from none → low → medium-high is accurate. "Team sharing" differences are directionally right, especially Code's GitHub-native workflow. And "best starting point" is reasonable as a crude funnel.
**What's wrong or misleading**
*Tool connections.* "MCP + built-in tools" for Chat vs "MCP (some limits)" for Cowork undersells Cowork and oversells Chat. The more important distinction — which you've already hit in practice — is **read vs write**. Chat's Gmail connector is read-only; Cowork is where write actions actually happen. That's the material difference for anyone choosing between them, and the table buries it.
*Context engineering.* Calling Chat "Limited" is odd given Projects, custom instructions, memory, and skills all live there. Chat's context engineering is actually quite rich — it's the *execution surface* that's limited, not the context layer. Cowork being "Good" and Code being "Full power" on this axis conflates two separate things: how much context you can give the model, vs how much agentic loop you control. CLAUDE.md at global and project scope is a Code-specific thing, sure, but that's agent configuration, not context engineering in the prompt-engineering sense.
*"Builds GTM brain."* This is the marketing-overreach line. It's Voje's framing, which makes sense given her brand, but as a capability claim it's vacuous — a "GTM brain" isn't a product feature, it's a thing you build *using* the tools. Any of the three can contribute depending on what you're doing. Partially/No/Yes here is more about which surface Voje personally uses to build systems than anything intrinsic.
*Best for.* "Building GTM infrastructure, pipelines, agents" for Code is narrow. Code is a general-purpose agentic coding tool; GTM is one application domain among many. Fine for her audience, misleading as a general description.
**What's missing**
No row for the actual thing that matters most in choosing between Chat and Cowork day-to-day: whether the tool can take actions on your behalf vs just retrieve and reason. Also nothing on cost model, nothing on where your data lives, and nothing on the Projects/Skills layer that cuts across Chat and Cowork.
Net: useful as a first-pass orientation for someone who's never seen the three surfaces. Not something I'd hand to anyone already using them — the read/write distinction alone is more actionable than six of the eight rows here."