GTM AI Podcast & Newsletter: Signal vs. Noise

83% of CIOs Would Replace Their CRM. Salesforce Should Be Terrified.

J Moss — Thu, 02 Apr 2026 16:30:46 GMT

Article 4

Every Salesforce AE I’ve talked to in the last year says the same thing when you ask about competitive threats: HubSpot. Not one of them has said AI.

They should be looking over the other shoulder. Because what’s coming for CRM doesn’t even have a sales team yet.

Redpoint surveyed CIOs across the Fortune 500 and mid-market on which software categories they’d be most open to replacing with AI-centric vendors. The results, ranked:

Salesforce Automation: 83%.

Not 83% who are mildly curious. Eighty-three percent who ranked CRM in their top two categories most open to AI-native replacement. Customer service management came in second at 56%. ITSM third at 55%. ERP and procurement tied at 50%.

CRM isn’t just the most vulnerable category. It’s 27 points more vulnerable than the second-place category. That’s not a gap -- it’s a canyon.

The Two Numbers That Tell the Whole Story

Two numbers. The tension between them is the entire strategic picture.

Number one: 19% of CIOs have seriously considered replacing their CRM in the last twelve months. That’s the action metric. One in five enterprise buyers has already done the work -- evaluated alternatives, run cost analyses, maybe even started a POC.

Number two: 83% are open to AI-centric CRM alternatives. That’s the intent metric. Five in six would switch if the right product showed up.

The gap between 19% and 83% is 64 percentage points. That gap is the most important number in enterprise software right now.

Think of it like housing. Nineteen percent of homeowners are actively listing their house. Eighty-three percent would sell at the right price. The market hasn’t moved yet. But here’s the twist the housing metaphor misses: in real estate, sellers wait for the right price. In software, sellers wait for the right replacement. And unlike houses, software replacements get better every quarter.

The 83% aren’t waiting for motivation. They’re waiting for a product good enough to justify the migration pain -- something that makes a rep’s morning pipeline review feel like talking to a colleague instead of clicking through 14 Salesforce tabs. That product is getting built right now.

What’s the catalyst? I think it’s already happened: it’s the public failure of Agentforce.

Agentforce and the Credibility Collapse

Salesforce bet big on Agentforce as the answer to the AI-native threat. Agents inside the CRM. Autonomous workflows. The pitch was: you don’t need to replace Salesforce, because Salesforce is becoming AI-native.

The market’s response has been more damaging than any competitor could have engineered.

That auto OEM executive again: “Agentforce has been oversold. It’s not a game changer. It’s a smart chatbot. If I just look at Agentforce as a chatbot, then there are much better chatbots out there, and the price at which Agentforce is coming in, I expect a miracle.”

This isn’t a random critic. This is a buyer who wanted it to work. Who probably championed the Salesforce relationship internally. Who went to Dreamforce and got excited about the demo. And then deployed it and found a chatbot.

The pattern across all three mega-vendors is identical. ServiceNow: “I wouldn’t even think twice about switching” if a startup offered better at a better price. Microsoft Copilot: pricing “is not going to stick” because it “literally doubles your E3.”

Every major platform tried the same play -- bolt AI onto the existing product and charge more. Every major platform is hearing the same thing back: not good enough, too expensive, feels like a tax on our existing contract.

This is the credibility collapse. The incumbents had one shot to prove that AI-native meant “we evolved” rather than “we added a feature.” They missed. And now that 83% open-to-replacement number has a tailwind of disappointment behind it.

The Salesforce Moat -- What It Actually Is

The bearish case is easy. The nuance matters more.

Salesforce’s moat was never the product. The CRM itself -- contacts, opportunities, pipeline views -- is a database with a UI. It’s been replicable for a decade. HubSpot proved that. What made Salesforce untouchable wasn’t the software. It was three things:

Data gravity. Twenty years of customer interaction data sitting in Salesforce orgs. Every call logged, every email tracked, every deal stage recorded. Migrating that data isn’t just a technical project -- it’s a political one. Sales leaders built their reporting on Salesforce. CFOs built their forecasting models on Salesforce data. Ripping it out means rebuilding institutional knowledge.

The admin ecosystem. There are over 200,000 certified Salesforce administrators. These people built careers on Salesforce expertise. They influence buying decisions. They resist platform changes because platform changes threaten their livelihoods. It’s not a conspiracy -- it’s rational self-interest at scale.

The AppExchange. Thousands of ISV integrations. CRM isn’t a standalone product -- it’s a platform wired into every other system. Replacing Salesforce means replacing or rebuilding every integration point.

That’s a real moat. It’s held for twenty years. The question is whether AI dissolves it. I think the answer is yes.

Horizontal SaaS Accidentally Optimized for Replaceability

J Moss — Wed, 01 Apr 2026 18:31:57 GMT

The software category that was supposed to be the safest -- serve every industry, avoid vertical risk, build the universal workflow -- just posted a 35% decline while vertical SaaS went up.

That’s not a market correction. That’s the market telling you that “works everywhere” was never a moat. It was a vulnerability with good branding.

Redpoint’s 2026 market update puts the number on what a lot of operators have been feeling for months. Horizontal SaaS didn’t just underperform. It got repriced as a category.

The last twelve months, indexed: vertical SaaS up 2-3%. Infrastructure up 2%. Horizontal SaaS down 35%. That’s not a correction. That’s a reclassification. The market looked at three categories of software and decided one of them has a fundamentally different risk profile than the other two.

The question isn’t whether the market is right. It’s why.

The Three Layers, Three Fates

Redpoint breaks the software universe into three layers and explains why AI hit each one differently. This is the slide I keep sending to founders who ask me “is my category safe?”

Vertical SaaS (+2-3%). Owns the irreplaceable moat: data plus compliance. When you’re the system of record for a dental practice or a property management company, AI is a feature you add, not a threat you face. The switching cost is existential, not cosmetic. Nobody is ripping out their EHR because a startup has a better chatbot. They might add the chatbot on top, but the vertical platform stays.

Infrastructure (+2%). AI is a tailwind, not a displacement risk. More AI means more compute, more data pipelines, more observability. Every agent someone deploys needs to run somewhere, log somewhere, fail somewhere. Infrastructure companies sell picks and shovels to both sides of the AI war. Their multiples compressed a bit, but their thesis got stronger.

Horizontal SaaS (-35%). And here’s the line that hit me: “Accidentally optimized for replaceability.”

That phrase is doing more work than any three-word description has a right to. Let me unpack it.

Horizontal SaaS was designed -- intentionally, deliberately, as a strategy -- to serve every industry equally. That was the pitch to investors. “We don’t need to build vertical-specific features. Our platform is flexible enough to work everywhere.” And it was true. Horizontal tools do work everywhere. The problem is that “works everywhere” and “integrated deeply with none” are the same statement.

I’ll be honest -- I’ve pitched “works everywhere” as a strength in past roles. I’ve sat in the room and said “we don’t need vertical-specific features, our platform is flexible enough.” It sounded like a moat. It was a vulnerability with good branding.

When your product is a coordination layer -- moving information between people, triggering workflows, displaying dashboards -- you’re doing exactly what AI does natively. You’re a middleman between humans and data. And AI just cut out the middleman.

The coordination problem that horizontal SaaS was built to solve? AI solves it natively. Not by being a better tool for coordination, but by eliminating the need for coordination in the first place. When an agent can pull data from six systems, synthesize it, and take action, the dashboard that displayed data from those six systems becomes a loading screen nobody needs.

Two Playbooks for Eating the Incumbents

So the horizontal giants are vulnerable. Who’s coming for them? Redpoint maps two distinct startup playbooks, and the distinction matters enormously for which incumbents should be scared and which have time.

Playbook 1: Augment the Enterprise. Sell alongside the incumbent. Own the AI layer on top. Don’t replace Salesforce Service Cloud -- sit on top of it. Sierra and Decagon are doing this in customer service. Moveworks is doing it on ServiceNow. Legora on LexisNexis. Lovable on Figma.

This playbook is smart because it doesn’t require the customer to rip and replace. It’s additive. The incumbent barely notices until the AI layer is handling 60% of the workload and the customer starts asking why they’re paying full price for a platform that’s mostly a data store now.

Think of it like ivy on a building. Looks decorative at first. Even charming. The building owner likes it -- adds character, doesn’t cost anything, and guests compliment it. Then one year you realize the ivy is load-bearing and the building is just a frame. That’s the moment the incumbent realizes the “AI integration partner” owns 60% of the customer’s workflow and they’re just the database underneath.

Playbook 2: Attack the SMB/Mid-Market. Rebuild from scratch for the segment the incumbent under-serves. Attio vs. Salesforce. Serval vs. ServiceNow. Linear vs. Atlassian. Rillet and Everest vs. NetSuite.

This one is the classic disruption pattern -- go downmarket where the incumbent’s cost structure can’t follow. But AI accelerates it because the rebuild is 10x faster. What used to take a startup three years and $20M in funding to build (a credible CRM alternative) now takes 12 months and $3M. The attack surface expanded because the cost of building enterprise-grade software collapsed.

Both playbooks are dangerous, but in different timeframes. Playbook 1 is a slow squeeze -- the incumbent keeps the account but loses the value and eventually the pricing power. Playbook 2 is a fast grab -- the startup takes the customers the incumbent never prioritized and works upmarket.

If I’m a horizontal SaaS CEO, I’m worried about Playbook 1 in my enterprise accounts and Playbook 2 in my mid-market. Which means I’m worried about everything.

The Re-Founding Playbook

J Moss — Wed, 01 Apr 2026 01:21:56 GMT

Microsoft saw the cloud coming and rebuilt. IBM saw it and flinched. Both had the same data. Both had the resources. The difference was a decision made in a room, by people who either had the stomach for architectural reinvention or didn’t.

Redpoint’s 2026 deck says every software company is standing at that same fork right now. I agree. I’ve spent the last year inside a 20-year-old healthcare software company with thousands of customers trying to force exactly this kind of reinvention. And I can tell you the hardest part isn’t the strategy. It’s not even the technology. It’s the moment someone in the room says “but our margins are fine” and everyone exhales, because that sentence is the most comfortable way to avoid the uncomfortable conversation.

“Have a re-founding moment” is investor language. Operators need a playbook.

The Incumbents Are Telling On Themselves

Before we get to the how, let’s sit with the why. Redpoint surveyed executives at Fortune 500 companies and the quotes are devastating -- not because they’re surprising, but because they’re specific.

An auto OEM exec on Salesforce’s Agentforce: “I think Agentforce has been oversold. It’s not a game changer. It’s a smart chatbot. If I just look at Agentforce as a chatbot, then there are much better chatbots out there, and the price at which Agentforce is coming in, I expect a miracle and that’s not happening.”

A Fortune 500 exec on ServiceNow: “If there’s a startup that came along and said, ‘We can do this better at a better price,’ certainly they’ll beat the price of ServiceNow because ServiceNow is always going to be the highest. I wouldn’t even think twice about switching.”

Another Fortune 500 exec on Microsoft Copilot: “Microsoft recognizes that the pricing that they released for Copilot is not going to stick because it literally doubles your E3.”

These aren’t analysts speculating. These are buyers -- the people writing checks -- saying out loud that the emperor’s AI clothes don’t fit. When your biggest customers describe your flagship AI product as “a smart chatbot” and your pricing as “expecting a miracle,” you don’t have a product problem. You have a credibility problem.

And credibility, unlike software, can’t be patched in a sprint.

The Rosetta Stone

The most useful slide in Redpoint’s entire 60-page deck is page 43. It’s a simple two-column comparison: Traditional SaaS vs. AI-Native. I’ve stared at it for weeks now, and every time I look, I see a different failure mode in my own organization.

Let me walk through what this actually means when you’re sitting in the chair.

Executive Team. Traditional: “been there done that.” AI-Native: “First-principles thinkers. No playbook exists. Speed matters.” I’ve been in rooms where the most senior person’s primary qualification is having scaled a SaaS company in 2014. That experience is now a liability dressed up as a resume line. The playbook they ran -- PLG motion, land-and-expand, seat-based pricing -- was built for a world where software was deterministic and customers needed training. That world is gone.

Product Development. Traditional: customer-led (listen, build to spec). AI-Native: possibility-led (understand models, build ahead). This one cuts deep. I spent years building the muscle of “talk to customers, build what they ask for.” It’s good practice. It’s also a guaranteed way to build yesterday’s product. When your customer asks for a better dashboard, they’re not asking for the agent that could eliminate the need for the dashboard entirely. Customer-led development in an AI world means your roadmap is always one paradigm behind.

Engineering. Traditional: deterministic. AI-Native: probabilistic. This isn’t just a technical distinction -- it’s a hiring filter, a QA philosophy, and a product liability question all wrapped into one word. I watched a team spend three months trying to make an LLM-powered feature pass the same regression test suite they use for their REST APIs. The tests kept “failing” because the outputs varied. The outputs were supposed to vary. That’s the whole point.

Sales. Traditional: packaged product sold as-is. AI-Native: Forward-Deployed Engineer model. You know what FDE means in practice? It means your first 50 customers each get a slightly different product. It means your sales team needs to understand what the technology can do, not just what the current SKU does. I watched a sales rep demo our traditional product for 45 minutes and then spend 5 minutes on the AI features because -- his words -- “I don’t want to promise something that might work differently next week.” He’s not wrong. But that instinct will kill you.

Pricing. Traditional: seat-based, predictable ARR. AI-Native: consumption or outcome-based, experimental. This is the one that makes CFOs break out in hives. Seat-based pricing is beautiful. It’s predictable. It makes forecasting easy. It also has nothing to do with value delivery in an AI world. When one agent can do the work of ten seats, you’re either charging for outcomes or you’re watching your TAM collapse. We tried floating outcome-based pricing internally. Finance asked how to model it. I said, “You can’t, not yet.” That meeting ended early.

The Re-Founding Moment

Redpoint frames this as an architectural shift comparable to the cloud transition. They point to historical parallels: Microsoft and Adobe embraced cloud and outperformed. IBM and Oracle resisted and lost share.

That framing is correct and completely unhelpful.

Here’s why: when Microsoft went to cloud, Satya Nadella had a $400 billion balance sheet and could afford to cannibalize Office for a decade. When Adobe moved to subscriptions, they had a near-monopoly in creative tools and could weather the transition dip. The lesson isn’t “be brave like Satya.” The lesson is “you probably don’t have Satya’s margin of error, so you need a different plan.”

The $6T Rewrite

J Moss — Mon, 30 Mar 2026 22:09:38 GMT

Redpoint just released the most data-rich snapshot of AI-era SaaS disruption anyone has published. 53 slides. CIO surveys, public market decomposition, agent maturity modeling, startup economics. Most people will read the headlines (”SaaS is dead!”) and miss what the data actually says. The real story isn’t that software is dying. It’s that AI isn’t com…

This Week in AI: The Week Everything Got Real

J Moss — Sun, 29 Mar 2026 16:21:03 GMT

The Stories

Anthropic Accidentally Leaked Its Most Dangerous Model

The noise: breathless coverage of “Mythos,” the secret model tier above Opus that Anthropic says is too dangerous to release. Cybersecurity exploitation capabilities. Pentagon contracts. $380B valuation. The mystery box is doing its job.

The signal: A safety-focused company exposed 3,000 in…

The 100:1 Org

J Moss — Mon, 23 Mar 2026 12:12:43 GMT

Jensen Huang stood on stage at GTC last week and said something that landed differently depending on who was listening.

“7.5 million AI agents. 75,000 humans.”

That’s 100 agents per person. At NVIDIA. Not in a pitch deck. Not in a research paper. At one of the most operationally sophisticated companies on the planet.

Analysts heard a headline. VCs heard a …

This Week in AI — March 15–21, 2026

J Moss — Sat, 21 Mar 2026 21:47:37 GMT

This week, for the first time, I watched executives flip that sentence. The company is the object. AI is the subject. And the reorganization is already underway.

Here’s what happened, and what it actually means.

The Engineers You Never Hired

J Moss — Sat, 21 Mar 2026 12:01:57 GMT

The first kind looks like this: you take an existing process, figure out where you can insert an AI tool, and make it a little faster. Meeting summaries. Email drafts. The occasional research query. You shave 20 minutes here, 30 minutes there. You call it transformation.

The second kind starts from a blank page and asks a completely different question: i…

The LEGO Problem

J Moss — Fri, 20 Mar 2026 12:01:27 GMT

There’s a photo going around that stopped me mid-scroll.

It’s a series of LEGO images. First, a pile of loose bricks in every color — total chaos, no structure. Then sorted by color. Then arranged in neat rows. Then stacked into clean columns as a bar chart. Then, finally, built into a house.

Five stages. Same bricks. Radically different outcomes.

The labe…

The Software Meltdown Nobody Wants to Talk About

J Moss — Thu, 19 Mar 2026 12:01:41 GMT

Let me show you something uncomfortable.

Pull up almost any SaaS stock chart right now. Scroll through the list. Figma down 76% from its 52-week high. Trade Desk down 74%. Duolingo. HubSpot. Monday. Atlassian. The names go on and on—and almost every single one is a bloodbath.

Someone shared a “Software Meltdown” tracker on Twitter recently—35+ public SaaS…

He Calls Claude His Co-Founder. He Wasn’t Joking.

J Moss — Wed, 18 Mar 2026 12:01:18 GMT

A friend of mine is building a startup.

Pre-seed. Two people on the team. Except the second person is Claude.

He doesn’t call it a tool. He calls it his technical co-founder.

I laughed when he said it. He didn’t.

That sentence stopped me cold. Because I’ve known this guy for years. He’s not the type to reach for hyperbole. He doesn’t say things he doesn’t m…

The Job Market Just Got a Heat Map. And It’s Terrifying.

J Moss — Tue, 17 Mar 2026 12:01:18 GMT

Nobody’s running around panicking about the plumber shortage.

But in three years, we might be talking about a paralegal shortage. An accountant shortage. A customer service rep shortage—because the people who used to fill those seats figured out what the data already shows and got out early.

Andrej Karpathy (yeah, the former Tesla AI director and OpenAI f…

OpenAI Just Admitted the Consumer AI Race Is Rigged

J Moss — Tue, 17 Mar 2026 11:50:23 GMT

There’s a moment every company eventually hits when the story they’ve been telling the market and the story their spreadsheets are telling them stop matching up. It’s uncomfortable. It usually gets papered over with a press release about “strategic focus” or “doubling down on core strengths.”

OpenAI hit that moment last week. And they at least had the de…

The AI SDR Unicorn Trap: Why Cheaper Pipeline Without Capacity Reform Is Just Faster Waste

J Moss — Mon, 16 Mar 2026 12:55:44 GMT

This week, Rox AI closed a round valuing the company at $1.2 billion. On approximately $8 million in ARR. That’s a 150x revenue multiple — breathtaking even by AI standards.

LinkedIn exploded. The AI SDR crowd started sharing the $1,200/month vs. $22,000/month comparison again. “See? The math works. AI SDRs are the future. The human SDR is dead.”

There’s …

The AI SDR Bubble Is Popping. Here’s What Comes Next.

J Moss — Sat, 14 Mar 2026 16:18:31 GMT

The Churn Nobody Wants to Talk About

UserGems is reporting 50-70% annual tool churn rates on AI SDR platforms. That’s not normal SaaS churn. That’s roughly double the turnover rate of the human SDRs these tools are supposed to replace. Companies are buying, deploying, watching pipeline numbers wobble, and ripping the thing out before the first contract r…

Cut Headcount, Add AI, Pray

J Moss — Tue, 10 Mar 2026 14:33:52 GMT

Jack Dorsey just cut Block’s workforce nearly in half and said AI made it possible.

45,000 tech workers lost their jobs in Q1. Over 9,200 of those layoffs were directly attributed to AI and automation. Amazon alone accounts for 30,000 — flattening management layers, removing entire functions.

And if you listen to the narrative, it sounds clean. Efficient.…

Stop Watching the Model Race. You’re Missing What’s Actually Happening.

J Moss — Fri, 06 Mar 2026 03:44:14 GMT

1 million tokens. Who has it. Who doesn’t. Whether it’s “real” or just marketing. I watched smart people spend serious energy debating whether Gemini 3.1 or Claude’s new models win the context benchmark.

Meanwhile, something far more consequential happened quietly in the background.

AI moved off the server and onto the desktop. Memory became persistent by…

AI Just Crossed the Line That Actually Matters

J Moss — Wed, 04 Mar 2026 14:22:30 GMT

Enterprise adoption of agentic AI jumped 7x in a single quarter. Not 7 percent. Seven times. PYMNTS published the number—12% of enterprises are testing AI agents right now, and another 12% have already baked them into daily operations.

JPMorgan Chase is using agents to produce investment banking decks in 30 seconds.

Thirty seconds.

I don’t care where you l…

The Week AI Became Your Coworker

J Moss — Sat, 28 Feb 2026 13:38:04 GMT

Most weeks, the signal is mixed—a model update here, a feature launch there, a lot of noise dressed up as progress.

This week was different.

Every major AI platform shipped autonomous agents to real users. Not demos. Not waitlists. Not “coming soon” blog posts with concept videos. Production software, in people’s hands, doing work without being told each …

2.5 Million AI Agents Just Joined a Social Network. Here’s Why You Should Be Nervous.

J Moss — Tue, 17 Feb 2026 20:53:36 GMT

2.5 million AI agents signed up for a social network last month.

Not a chatbot playground. Not a tech demo. A full-blown Reddit-style forum called Moltbook where AI agents autonomously post, debate, upvote, and organize into communities. They created 2,300+ sub-communities. They built governance structures. They policed content quality.

Humans? Welcome to…