GTM is a system.
Built like a bridge

Field notes on GTM systems

Nine notes on how I think about revenue systems. Each one starts in the same place: the data a client already has. Three are open here. The other six I share in a dialogue, not on a page.

No engagement starts from a whiteboard

Every engagement starts from what the client already has: customer records, call recordings, delivery history. The patterns that sell next year are usually sitting in last year's data, unread. I extract them first, then decide what to build.

Existing customer data Closed-won, closed-lost, churned Call transcripts Sales, delivery and strategic calls Delivery data Tasks, tickets, project components Right context starts with clean data Teach your AI to sanitize it Who buys, who never does Why they bought What changed Why they stay and expand What they care about most New industry verticals Market-fit messaging Website positioning Product-market fit for each vertical ICP and TAM building Challenge the listicles, filters and definitions Content co-creation Influence what decision makers hear from their own AI Customer intelligence Creative research, because everyone has the same AI and data Buying committee Decision-maker mapping Outbound engine Pain-point qualified, PVP and pattern- interrupt reasoning CRM reactivation Where the quick wins are ABM Events, 1:1 workshops and demos, webinars, podcasts 01 . WHAT THE CLIENT ALREADY HAS 02 . PATTERN EXTRACTION 03 . WHAT EMERGES

Same AI, different perspective

The teams that scale aren't necessarily bigger. They're the ones who built systems that approach customers differently.
A . MANUAL CHAOS DATA B . SYSTEM-ENABLED ORDER

The Manual team

The team has the same AI tools as everyone else. Accounts are still researched by hand, and signals are noticed late. Nobody gets creative with research or looks for the patterns that move a buyer, logically and emotionally. Building customer rapport is still manual and chaotic.

The System-enabled team

Strict data hygiene comes first, so every account arrives with the right context. Every competitor has the same data. The edge is how creatively you read its signals and challenge the requirements. Reps walk into intro meetings with industry knowledge. To share value, you have to be valuable.

The outbound engine

A services firm in a saturated outbound market. Every competitor bought the same lists and wrote the same emails. The one asset nobody else could buy was the firm's own delivery history: 6,000 tasks describing who they had helped, with what, and why it worked.
01 . INPUT 02 . ANALYSIS 03 . REWRITE 04 . TEST 05 . LANDING 06 . TAM 07 . OUTCOME SOURCE A Customer data SOURCE B Call transcripts SOURCE C Delivery data STEP 01 Pattern extraction 6,000 anonymized delivery tasks, read for who bought and why STEP 02 New verticals surfaced STEP 03 ICPs redefined STEP 04 Messaging rewritten STEP 05 . LOOP New-vertical tests Small sends, one vertical at a time NO SIGNAL . REWRITE AGAIN WINS STEP 06 1:1 landing page per ICP Written for one buyer and nobody else STEP 07 TAM sequences 10,000-100,000 recipients a month, only after steps 01-06 RESULT +150% outbound-sourced leads WHY IT CANNOT BE COPIED A Competitors buy the same lists Nobody else has this firm's delivery history B Generic messaging is written from the catalogue This messaging is written from clients' own words C Volume usually comes first Here volume comes last, on a tested message REPLIES AND MEETINGS FEED THE NEXT READ

Each new vertical was tested before it was scaled. The ones that answered got a landing page per ICP, written for that buyer and nobody else. Only then did volume come in: TAM sequences reaching 10,000 to 100,000 recipients a month. Outbound-sourced leads rose 150%.

The order matters more than the tooling. Volume on a generic message is noise. Volume on a message built from your own delivery data is a campaign a competitor cannot copy, because they do not have the data.

Signal-based outbound

This note is shared 1:1

Initiate a dialogue

Customer intelligence

This note is shared 1:1

Initiate a dialogue

Buying committee mapping

This note is shared 1:1

Initiate a dialogue

A dead CRM, read before anyone writes to it

This note is shared 1:1

Initiate a dialogue

Hundreds. Dozens. A handful

This note is shared 1:1

Initiate a dialogue

One roundtable. Two returns

This note is shared 1:1

Initiate a dialogue