Harry Stebbings posted three quotes this week from a CEO he interviewed on 20VC. The thread is here. The line that changes the conversation is the one in the middle.

“We replaced our $600K Salesforce contract with a vibe-coded CRM, built within 3 weeks.”

“We will get rid of 80% of the SaaS we use internally.”

“If Anthropic doubled pricing, we would not change usage in any way.”

The easy reading is “SaaS is dying and AI is killing it.” That stays on the surface. The line that matters is the third. It is the customer admitting on camera that the moat moved. It is not in Salesforce anymore. It is not in Anthropic either. It is in the workflow this company built on top.

That is the thesis. The IQ Source piece for companies living through this shift without the in-house capacity to absorb it is Technology Partner. The rest of the post explains why the third line matters more than the first two, and what the CEO is missing for the shift to actually stick.

The three quotes, line by line

I’ll break them down because each one measures something different.

Six hundred thousand replaced in three weeks. The number is precise. The interesting question isn’t whether the new CRM is as capable as Salesforce (it isn’t, and it doesn’t matter). The question is how fast the cost of replicating the functions this team actually used collapsed. Three weeks ago that was an eighteen-month implementation plus another half year of migration. Today it is three weeks. That is an order-of-magnitude change, not an incremental one.

The middle quote is the natural consequence. If the first line is true, the second is predictable. A mid-market B2B company’s stack runs to dozens of SaaS tools, most of them bought to cover a specific process for a specific team. If replacing Salesforce takes three weeks, replacing Greenhouse or Calendly or an entire Notion module is days of work. The “one tool per process” economics stop closing the moment a replacement is buildable in a single sitting.

The third line is the one almost nobody processed correctly. It isn’t Anthropic fan-enthusiasm. It is a business owner saying, on the record, that he is no longer price-elastic to the model provider. The reason is structural. If the company’s workflow lives inside Claude Code, inside a vibe-coded CRM that calls Sonnet 4.5 dozens of times a day, inside five internal agents that each own a slice of the process, then the model cost is a margin input, not a continuity input. Doubling compute pricing hurts the P&L. It does not threaten the ability to operate.

What that third line proves

The Salesforce moat was never the CRM code. It was three things that took years to accumulate: customer data, integrations across the rest of the stack, and team knowledge about where every field lived. That combination is exactly why custom CRMs in the 2000s lost to Salesforce. It wasn’t price. It was the cost of keeping twenty integrations alive.

AI made all three cheap. Data migrates with scripts generated in an afternoon. Integrations rebuild with MCPs and SDKs in a matter of days. Team knowledge transcribes into a two-hundred-line CLAUDE.md file any model reads at the start of every session. Salesforce’s triple moat stopped costing years.

That’s what changed. And that’s why the CEO Stebbings interviewed answered the way he did. The language model vendor doesn’t own his workflow. He does. Anthropic can double the price and he keeps operating. What he can’t do overnight is swap the model itself, because his flow is written assuming Claude’s specific behavior. But paying more for the same compute is a finance problem, not an operations problem.

This is the lock-in inversion. For twenty years, the lock-in belonged to SaaS, and CEOs accepted it because building alternatives was expensive. Now the lock-in belongs to the flow the company built itself, and building the flow got cheap. It is the first time in recent memory that the customer comes out of the trade with more structural capacity than the vendor. We covered the same inversion from a different angle in the runtime-commodity, workflow-moat post.

In the 2000s I watched the reverse pattern. Large companies turned off CRMs they had built in C++ or PHP and migrated everything to Salesforce. The reason was always the same: the cost of maintaining integrations against the rest of the stack outweighed the savings of owning the code. That equation just flipped. Integrations are now the cheap side. Expensive is not owning your flow.

The moat isn’t free

There’s a catch most CEOs aren’t pricing in yet, and the proof is in the cost-side numbers Mark Ajzenstadt, founder of Limestone, posted on X this week. Limestone runs production AI projects at two hundred dollars per developer per month. Uber engineers, per The Information, were burning between five hundred and two thousand per person per month before the budget collapse. Ten times the spend.

The difference isn’t the tool. Both teams use Claude Code. The difference is the layer Ajzenstadt names directly: cost and quota controls, model routing, caching strategy, margin analysis at ten times current volume before the first agent ships. Translated: somebody designed the workflow with margin discipline from day one. At Uber, nobody did. We covered Uber’s case in the AI-addiction-architecture post.

That layer is the hidden problem underneath the moat the Stebbings CEO named. Replacing Salesforce in three weeks with a vibe-coded CRM is doable. Keeping that CRM alive, optimizing its token consumption, controlling which agents anyone can trigger, patching behavior when Anthropic ships a new model version, onboarding new engineers into the workflow design — all of that is the work SaaS used to do for you. It doesn’t anymore.

The moat moved. So did the maintenance of the moat. And maintenance is where most mid-market B2B companies, especially in LatAm, lack capacity. They have engineers who can vibe-code the first prototype. They don’t have the role that sits on top of the flow once it’s in production and the CFO starts asking about the invoice.

What IQ Source does about this

Technology Partner exists precisely to fill that role. The client company doesn’t subcontract the implementation to us; implementation is becoming accessible. They subcontract the owner of the flow: the team that designs cost controls, maintains margin, absorbs model upgrades, and keeps workflow knowledge inside a trained group rather than a single engineer. It’s the role a Chief Technology Officer would fill if a mid-market B2B company could afford a good one. Most can’t, and that’s why they end up with a junior engineer who ships something and two months later nobody knows how to maintain it.

The prior discovery work is AI Maestro, two months of consultancy producing the Process Reality Map, the AI Opportunity Score, and the Go/No-Go gate. It decides which flows are worth building before you build them and which to walk away from. But continuous execution — the role the Stebbings CEO is going to need the first quarter after Salesforce goes dark, when somebody has to decide whether the vibe-coded CRM scales next year — that’s Technology Partner.

The cross-calculation matters more than it looks. The two options a CEO has now are hiring an in-house team capable of maintaining critical AI flows (a tech lead and three decent engineers in LatAm sit comfortably above half a million a year once benefits and turnover are factored), or subcontracting a partner who absorbs that role with an already-formed team. The question is not whether you can avoid the spend. The question is whether the role exists somewhere in your organization. If it doesn’t, the moat that replaced Salesforce evaporates the day the engineer who built it quits.

Before the week ends, ask your team a concrete question. If the person who knows your most critical AI flow best resigned today, how many months would it take to rebuild that knowledge? If the answer is more than one, you don’t have a moat. You have a personal asset with exit risk. That is the problem Technology Partner solves before it surfaces.

Subcontract the role that keeps your moat alive