When Execution Is Cheap, Judgment Becomes Scarce

When Stripe was still small, the Collison brothers decided to focus on a handful of their Startup cohort at Y Combinator. They had interest from hundreds of potential customers but chose depth over breadth.

A little-known practice at Stripe. Engineers were asked to sit in on failed sales calls and watch screen recordings of developers abandoning integrations. Docs were rewritten based on drop-off moments, not feature completeness. This is why Stripe’s docs read like a tutorial written by someone watching over your shoulder.

The brothers spent time understanding how those specific companies built products, what their developers cared about, and whether Stripe’s approach to payments would actually matter to them. Judgment first. Systems later.

The Execution Surplus

We’re living through an odd moment. The tools to execute have become remarkably accessible. Research that took days now takes minutes. Decks generate themselves. Forecasts, content briefs, and competitive analyses flow faster than we can use them.

The bottleneck has moved.

A decade ago, a decent GTM operator won by outworking competitors. More calls, more content, more meetings. Effort was the limiting factor. Today, every team has access to the same execution leverage. AI writes the emails, automation books the meetings, and analytics surfaces the signals.

The hard work now lies in deciding which emails matter, which meetings to take, and which signals to ignore.

Judgment Scales Differently

Execution scales with tools. Judgment scales with context, experience, and accountability.

A junior rep can send personalised outreach to 900 accounts in an afternoon. The tooling exists. Knowing which 42 accounts are actually reachable, which 13 have budget timing that aligns, and which 7 deserve the founder’s time. That knowledge comes from closing deals, losing deals, and learning which patterns repeat.

In enterprise GTM, this gap widens daily. Execution becomes abundant. Judgment becomes scarce.

What Judgment Actually Looks Like

When Salesforce was expanding beyond its initial SMB success into enterprise accounts, Marc Benioff started flying to meet with individual CIOs at large enterprises, spending days on single accounts that hadn’t committed to anything. The execution machine was working. Benioff read something different.

Salesforce’s flagship conference, Dreamforce, is often framed as a celebration of customer love. Internally, Dreamforce was optimised first for partner dominance.

Enterprise required a different motion entirely. He studied political landscapes, understood procurement cycles, and built relationships that would take years to convert. Recognising when the playbook needs to change, even while the current one works, is what separated Salesforce from competitors who kept applying an SMB playbook at larger companies.

You see the same thing in smaller decisions. A VP of Sales kills pursuit of a logo everyone wants because the buying committee lacks real authority. A founder delays a launch because the market narrative isn’t ready, even though the feature works. A marketing leader kills a campaign with strong engagement because the personas don’t match who actually buys. These decisions create discomfort because they involve saying no to things that look productive. They require believing that constraint creates more value than volume, and that activity and progress are not the same thing.

The Questions That Matter

When execution becomes cheap, the valuable questions change. It stops being “Can we do this?” and starts being “Should we do this now?” The question isn’t how to reach more accounts but which accounts are worth the friction. Data stops being the answer and starts being one input among several, because the harder question is what the data doesn’t say.

These questions require someone to own the outcome, to have skin in the game, to accept that choosing one path means closing others. You can’t automate that.

Where Judgment Fails

Two failure modes come up repeatedly.

Analysis paralysis. Teams that treat every decision like it needs a framework, a model, a consensus process. They value judgment but make the act of judging so heavy that nothing moves. Good judgment means making calls with incomplete information and adjusting as you learn.

Abdication. Teams that delegate judgment to systems. “The model says we should focus here.” “The playbook says we do this next.” Models and playbooks are tools for execution. They don’t substitute for thinking.

Figma’s enterprise expansion shows this. They had data showing demand across dozens of verticals. Dylan Field and the team focused on design and product teams first, saying no to marketing teams, engineering teams, and other buyers who wanted in. The data would have supported broader execution. The judgment was to stay narrow until they truly understood one motion.

Building Judgment Capacity

You can’t scale judgment the way you scale execution, but you can build it.

Atlassian built their enterprise GTM motion by letting individual contributors and small teams buy and deploy their tools without sales involvement. Every other enterprise SaaS company was building outbound teams and going top-down.

Atlassian’s “No Sales Team” story is famous. What’s less known is how close it came to breaking. In early enterprise pilots, Atlassian noticed deals stalling not because buyers disliked the product, but because procurement departments didn’t trust a company that wouldn’t negotiate.

The Atlassian founders believed that watching thousands of organic buying decisions would build better judgment than optimising a traditional sales playbook. They were right. By the time they built an enterprise sales team, they had years of pattern recognition about how software spread inside companies.

The best GTM leaders I know create space for their teams to make real decisions rather than just follow processes, because a rep who has only ever run a script will never develop the judgment to know when to break it. They reward good calls alongside good outcomes, since the right decision still loses sometimes. They make their own thinking visible after a tough call, explaining how they weighed the options. None of this is fast. But it compounds in ways that deploying a new tool never does.

The Advantage

Snowflake’s early GTM shows what this looks like in practice. They entered a market with entrenched players: Oracle, AWS, traditional data warehouses. Every competitor had more resources, more salespeople, more marketing budget. Snowflake couldn’t outspend them on execution.

Snowflake rejected standard ICP thinking. Instead of “data leaders” or “CIOs,” they built an internal persona called “The Skeptic.”

Frank Slootman and the team made precise judgments about where to compete. They focused on data teams at cloud-native companies who were frustrated with existing solutions. That precision meant teams stopped chasing every opportunity and moved faster on the ones that mattered. Competitors could copy Snowflake’s architecture. They couldn’t copy hundreds of well-made decisions about which customers to serve and how.

What This Means for Enterprise GTM

Enterprise buyers are drowning in outreach. Everyone has the tools to reach them, the data to personalise, and the automation to follow up.

They respond to precision. Knowing what they actually need. Showing up at the right time with the right message for the right stakeholder. Because someone made a call.

As execution continues to get cheaper, judgment will continue to get more expensive. The gap between teams that understand this and teams still optimising for output will widen.

The question is whether you can decide what’s worth executing in the first place. That’s where the work is now.