Your GTM stack was built to win customers. Not to keep them.

The first article in this series introduced State and Signal in the 4S Framework. This one focuses on Scale and System.

James Clear wrote in Atomic Habits: “You do not rise to the level of your goals. You fall to the level of your systems.”

That applies to modern GTM more than most companies realize.

For 15 years, companies built GTM systems to acquire customers; pipeline, new logos, and funnel velocity. Every tool in the stack was purchased to accelerate growth.

Almost none were designed to make it hard for customers to leave. They measured what they could see: closed revenue, pipeline, and new logos. They optimized for what they measured. Most GTM teams never intended to underinvest in retention. The systems trained them to prioritize acquisition. Sales compensation rewarded new accounts. Marketing dashboards prioritized attribution and pipeline creation. Product teams measured activation, adoption, and feature usage. Every function optimized locally around visible growth metrics while customer dependency remained invisible.

Over time, companies became highly efficient at acquiring customers without becoming structurally important to them.

Retention wasn’t counted, so nobody built for it. And when we can't measure it, we can't defend the budget for it.

That worked when Scale was the moat.

Today, AI makes many of those advantages temporary. Workflows that once required expensive software can now be rebuilt internally with AI agents, automation, or lighter tools in days.

The stack is easier to replicate.

The question more leadership teams should ask:

What actually protects you when your customer can rebuild part of your stack themselves?

The answer is not more software. It is whether your product becomes part of how the customer operates. 

For years, Scale rewarded size. Bigger distribution, larger datasets, and broader ecosystems made companies harder to compete against.

Now many of those advantages erode faster.

AI-native companies are discovering this too. ChartMogul’s 2026 retention report showed AI-native companies with median NRR of 48%.[1] Faster product cycles do not automatically create deeper customer dependency.

Scale gets you into the account. System determines whether you stay there.

System exists when your product becomes part of how the customer operates, not just something they use.

That distinction matters more than most companies realize.

McKinsey found top-quartile NRR performers trade at 24x EV/Revenue. Bottom-quartile peers sit at 5x.[2]

The reason is operational.

At 97% NRR, companies repeatedly spend money replacing revenue they already acquired. At 120% NRR, the installed base grows. The same acquisition investment keeps producing expansion revenue over time.

That is not a campaign improvement. It is a different business model.

Companies above 120% NRR usually look different operationally. Product, customer success, sales, and marketing are connected around customer workflows rather than isolated funnel stages. Expansion comes from deeper operational adoption, not just upsell pressure. The product becomes harder to remove because teams reorganize how they work around it.

The companies outperforming on retention are not running better campaigns or using newer tooling. They built deeper operational dependency inside customer workflows.

Latané Conant, CMO at Parloa, asked a room of marketing leaders this month who actually owns customer experience end to end. “Everyone plays a part,” she said. “But no one truly owns it.”[3]

That's not a management problem. It's a design problem.

Ryan Hinkle at Insight Partners described the difference directly:

“The key question is: What is a system of record? If it’s just a filing cabinet, a digitized storage system, that’s a problem. If it’s a true system of action or work, where knowledge workers can’t do their jobs without it, that’s very different.”[4]

AI can replicate your stack. It cannot replicate your customer’s operating process.

That is the distinction the 4S Framework calls System.

Not switching costs. Operational embeddedness.

Veeva built it inside life sciences. Its software became embedded in regulatory and clinical workflows where replacement means retraining teams, rebuilding processes, and navigating recertification requirements.

Procore built it in construction. Contractors, subcontractors, and owners operate inside the same environment. Removal impacts the workflow of the entire project ecosystem.[5]

Rockwell Automation built it in manufacturing. PLC infrastructure became deeply integrated into production environments where replacement affects operations, training, compliance, and uptime simultaneously.

Scott Brinker’s 2026 State of Martech reported 176 content marketing vendors removed from the landscape in a single year.[6] Many products did not fail technically. Customers removed them because doing so did not materially change how work happened.

That's increasingly the test.

What would your customers lose if you disappeared tomorrow?

The system James Clear described is not a personal metaphor. It is a business architecture decision.

If your customer can leave without reorganizing how their team operates, your position is weaker than most dashboards suggest.

The companies building strong System usually do three things differently.

Marketing listens for operational language. Customers describing the product as “part of how we work” signals something very different than “a tool we use.”

Customer Success documents workflow dependency, not just account health. Which operational process breaks if the customer leaves? That answer is often a better retention indicator than NPS.

Product evaluates removal cost during roadmap planning. If customers could replace the product tomorrow without rebuilding workflows, retraining teams, or changing operating behavior, System is shallow.

The companies building defensible GTM advantage are no longer optimizing only for acquisition. They are building products and workflows customers reorganize around.

Because when tooling advantages become easier to replicate, operational dependency becomes harder to replace than software itself.

Footnotes

[1] ChartMogul. SaaS Retention Report: The AI Churn Wave. chartmogul.com. 2026.

[2] McKinsey. “The Net Revenue Retention Advantage: Driving Success in B2B Tech.” November 2025. mckinsey.com.

[3] Latané Conant. LinkedIn. April 24, 2026. Reuters CONNECT Customer Service and Experience West, San Diego.

[4] Ryan Hinkle, Managing Director, Insight Partners. “Five Major Trends Reshaping AI, Software, and Leadership: Our Investor Predictions for 2026.” December 2025. insightpartners.com.

[5] Procore Technologies. Q1 2026 Earnings Report (8-K). Filed May 2026. SEC EDGAR.

[6] Scott Brinker and Frans Riemersma. State of Martech 2026. chiefmartec.com. May 2026.