Garrett Wolfe on why cookie-cutter GTM is dead

Garrett Wolfe's thesis is blunt enough to sound like a slogan:

"Cookie cutter go-to-market no longer works."

The more interesting line comes right before it:

"Growth has become this painful cycle of like discovering go-to-market alpha and then everyone else copying it and it's like no longer worthwhile."

That is the actual argument.

The problem is not just that everyone has access to the same tools. The problem is that the tactic itself decays the moment it becomes visible enough to be copied.

Garrett is not selling custom software in the abstract

This is where the talk gets better than the usual bespoke-software pitch.

Garrett is not saying custom is good because it feels premium. He is saying generic systems cannot encode the weirdness of a real sales workflow.

He grounds that point in operator pain:

• only 45% of companies even know what GTM engineers do
• GTM engineers inherit poorly integrated systems
• they report to everyone
• the bottlenecks are always bandwidth and capacity

That is why the talk starts with frustration, not with a product category.

The point is not "buy less SaaS." The point is "stop forcing frontline teams through software that assumes the workflow is already solved."

The best part of the talk is the ugly app

Garrett says it himself:

"This is like a web app that I built. It's like obviously ugly."

Good.

That is exactly why the demo lands.

Instead of selling a polished abstraction, he shows a working internal product layered on top of Attio and Supabase. The app pulls CRM records and intent signals into one place, lets reps filter and prioritize, then lets them do the next thing immediately:

• find the right person
• enrich the phone number
• push the record back into the CRM
• move it straight to the dialer

That is the real product insight in the whole talk:

"I should be able to have my list of intent signals for each company and then immediately prospect."

Once you hear it, it sounds obvious. Which is exactly why it is such a good insight.

Signals and actions should not live in different worlds.

This is really a talk about closing the loop

Most teams do not have a signal problem. They have a handoff problem.

Someone notices a trigger. Then the rep jumps tools, rebuilds context, re-finds the company, looks for people, enriches the contacts, and only then does the actual selling motion begin.

That dead space between signal and action is where a lot of GTM energy goes to die.

Garrett's point is that bespoke tooling becomes valuable when it collapses that dead space. Not because it is custom. Because it is closer to the actual work.

That is also why his talk fits the broader Deepline thesis so well. Agent-native GTM should reduce the number of translation steps between "something changed" and "here is the next action."

The more durable lesson is about experimentation culture

One of Garrett's better lines is not about tooling at all:

"You need to focus a lot on experimentation culture and what it takes to get really good at figuring out what you should spend your time on and what that will yield."

That is the difference between a bespoke tool and a bespoke motion.

The tool matters because it lets the team test faster:

• can we act on this signal now
• does this prioritization actually improve output
• which workflows reps adopt without being pushed

That is what makes the "days to 20-30 minutes" line important. The value is not speed by itself. The value is shortening the loop enough that teams will actually run the experiment.

The takeaway

Garrett's talk is not "custom software good, SaaS bad."

It is that GTM advantage decays faster now, and generic workflows tend to decay first because everybody inherits the same assumptions.

So the work shifts:

• less time inheriting default workflow logic
• more time building around the exact motion the team wants to run
• more direct connection between signal, prioritization, and action

That ugly app is the best part of the talk because it makes the shift tangible. It is not precious. It is just closer to what the team actually needs.

If you want to go deeper

For the full event context, start with the April Tools Day recap.

If you want to build signal-to-action workflows without hopping across five tools, start with Deepline.

More talk breakdowns from the same event:

• Ben Holley on outbound from the terminal
• YG Hong on shipping lead scoring without knowing ML
• Jai Toor on outcome-first GTM systems
• Shashank Khanna on revenue as a state machine

$ curl -s "https://code.deepline.com/api/v2/cli/install" | bash