A Note Before We Begin: I’m writing this because I genuinely admire what Clay is building. I’ve been watching Kareem, Varun, and the team for a while now. The content they put out. The way they think about GTM. The courage it takes to burn the boats on a horizontal product and go narrow. The discipline to build GTM Engineers into your own go-to-market motion instead of just hiring traditional sales teams. That’s real commitment.

This isn’t a hit piece. It’s not criticism disguised as analysis. It’s an attempt to do something I find endlessly fascinating: look deeper into what makes a business connect with identity, both the founder’s and the customer’s.

I’ve tried my best to get the facts right. I’ve read interviews, tried and tested the product, watched demos, studied customer language, and analyzed your decisions. But I’m looking from the outside. If I’ve misrepresented anything (numbers, timelines, intentions), it’s not deliberate. I’m genuinely trying to understand the patterns.

Here’s the thing about positioning work: you can’t read your own label from inside the jar. You’re living it. You’re making a thousand decisions a day that prove what you are. You experience your success from the inside, which makes it nearly impossible to see the patterns that explain it.

That’s where an outside perspective can help. Not because I know your business better than you do. You absolutely have data, evidence, and lived experience that I don’t have access to. But sometimes the person outside the jar can read the label more clearly than the person inside.

This entire piece exists to answer one question: What business are you actually in?

Not what you sell. Not what your product does. But what do you mean — what concept you’re building toward owning in customer minds, whether you’re claiming it explicitly or proving it implicitly through every costly decision you make.

You might read this and think “he doesn’t understand what we’re doing.” That’s fair. You have information I don’t. You’ve made strategic choices for reasons I can’t fully see.

But you might also read this and think, “Huh, I never saw it that way.”

If it’s the former, ignore it entirely. You’re the one building. You’re the one with the data. If it’s the latter (if even one insight shifts how you think about what you’re building), then this was worth writing.

Either way, I’m rooting for you. What you’re attempting is hard. Category creation is hard. Building something that doesn’t fit existing frameworks is hard. Having the courage to let early customers churn because they don’t fit your vision is hard.

I respect the work. This is just me trying to read the label.

Let’s begin.

PS: Monopoly uncovered all the insights you’ll read in this perspective.

Part 1: The Story They Tell

Kareem Amin has a sophisticated narrative about Clay’s rocket ship to $3.1 billion. The company created a new professional category called “GTM Engineering” and built the “GTM Development Environment” that powers it. They’re the Figma for go-to-market teams. The IDE where technical operators build custom workflows generating “GTM Alpha,” a competitive advantage through unique data combinations no database alone can provide.

The story is consistent and intellectually compelling. Clay isn’t competing in sales intelligence or data enrichment. They’re creating an entirely new category where technical GTM operators use 150+ data provider integrations plus AI research agents to build programmable workflows in a spreadsheet interface.

Varun Anand articulates the thesis: standard data leads to standard results. GTM teams need unique data to achieve outsized returns. Clay aggregates providers, adds Claygent for AI research, wraps it in spreadsheet familiarity, and enables what they call “programmable GTM.”

Their claimed success drivers reveal an explicit positioning strategy:

Category creation. Over 400 GTM Engineer job postings emerged in 4.5 months. They’ve published the “Three Laws of GTM” manifesto. Built Clay University with free certifications. Created 20,000+ member Slack community. They’re manufacturing a profession into existence.

Product-led growth combined with education. Generous free tier. “Reverse demos” where customers bring real problems and Clay solves them live. Community as acquisition engine. Templates and workflow sharing.

Structural commitment. They operate with GTM Engineers as their own go-to-market team, no traditional AEs or SDRs. These engineers report directly to co-founder Varun. They’re living what they’re selling.

Technical differentiation. 150+ integrations versus competitors’ 5-20. Waterfall enrichment logic. Claygent as research agent. Spreadsheet UI with “serverless” backend power.

Listen to how they describe themselves:

“Development Environment”
“IDE for GTM”
“GTM Engineer” (the role)
“GTM Engineering” (the discipline)
“System of Action, not System of Record”
“Creative tools for growth”
“Programmable GTM”

These aren’t casual word choices. They’re deliberate framing attempts, explicit positioning claims meant to establish mental territory.

But here’s the revealing tell: Amin admits the positioning discovery wasn’t strategic analysis. It was a psychological revelation. “There was something in my psychology that made me feel like, ‘Oh, we could do anything.’ That was the lure of the horizontal product.”

The founder’s psychology became the positioning discovery engine. This matters enormously because it reveals Clay is doing something right that they don’t fully understand they’re doing.

Part 2: The Hidden Position – The “Remove All Words” Test

Remove Clay’s name. Delete every tagline. Strip away all marketing copy, “GTM Development Environment,” “IDE for GTM,” “creative tools,” all of it. Take away the words. What pattern of decisions remains?

The Pattern That Emerges:

2017-2021: Refused to commit to a single ICP despite revenue stagnation. Supported wildly different use cases. Built a spreadsheet interface connecting APIs. The horizontal temptation.

2021: Narrowed to outbound sales. Cut features irrelevant to salespeople. Nearly all original customers churned.

2022-2023: Transitioned from sales-led ($200/month requiring seven demos) to completely self-serve. Built 8 “reverse demos” daily, where customers brought real problems. Launched Clay University with free cohort-based training. Nicolae Rusan, one of Clay’s co-founders, left the company to pursue other interests.

2024-2025: Acquired Avenue for intent signals. Launched six major features. Grew from approx 20 to 500-1000 employees. Raised $204M, reaching $3.1B valuation.

The Constant Thread:

• 150+ data provider integrations (not proprietary data ownership)
• Free education at a massive scale (not monetized training)
• Usage-based credit system (not predictable seat pricing)
• Self-serve motion for $720/month product (not sales-led)
• Unlimited users on all plans (not seat-based revenue)
• Category creation investment (not positioning in an established category)
• Music tool UI aesthetics (not enterprise software design)
• Reverse demos as standard motion (not scripted presentations)
• GTM Engineers instead of the sales team (not traditional roles)

What does this pattern prove without stating it?

Experimentation infrastructure. Every major decision points to enabling creative experimentation over operational efficiency. The spreadsheet interface provides infinite configurability. The 150+ integrations maximize data source optionality. AI agents enable custom research at scale. The credit system encourages exploration. Free education lowers barriers to sophistication.

But here’s the critical insight: They don’t own this concept yet. They’re building toward it.

Clay is making costly commitments that implicitly prove the value of experimentation infrastructure, while simultaneously making explicit claims about being an “IDE” and “Development Environment.” The costly signals are authentic. The explicit language is aspirational.

The concept Clay proves through decisions: “We are the infrastructure for creative experimentation in GTM operations.”

The concept Clay claims through language: “We are the GTM Development Environment that created GTM Engineering.”

These are not the same. And the gap explains everything about their current trajectory.

The Noun-Verb Architecture:

Claimed noun: “GTM Engineering” (a professional discipline)
Proven noun: “Creativity” (enabling novel approaches)
Supporting verbs: Build workflows, enrich data, orchestrate systems, automate research, ship experiments

The architecture reveals confusion. They’re claiming a noun (GTM Engineering) that describes a role, while proving a noun (Creativity) that describes a capability. One is about who uses the tool. The other is about what the tool enables.