GTM is a system.
Built like a bridge
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.
Same AI, different perspective
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
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 dialogueI start from first principles. What problem do you solve? What data points connect to that problem? Then monitor everything: intent data (website visits, LinkedIn engagement, open-source activity), signal data (supply-chain changes, market volatility, operational shifts that indicate the problem exists or is getting worse), and trigger data (job changes, funding, expansion that creates buying windows).
Targets appear when the problem exists or changes, when they're showing awareness, or when a window opens. Not from static demographic lists.
Customer intelligence
This note is shared 1:1
Initiate a dialogueMimics how humans learn. Every customer interaction generates hypotheses. Every new data point validates or rejects them. After each call, an agent classifies the conversation, reads existing hypotheses, generates new ones, updates the database. All reps' learnings compound into one continuously validated knowledge base.
Critical for finding product-market fit faster. Every other system queries this for "what's true about this company or persona?" - your GTM runs on validated intelligence, not static assumptions.
Buying committee mapping
This note is shared 1:1
Initiate a dialoguePull all contacts broadly - cast wide net - store in database. An agent then selects the actual buying committee using customer intelligence plus real-time LinkedIn data.
Enterprise titles don't map to roles consistently. "VP Platform" at one company is "Head of Engineering" at another. 2 to 3 hours of research per account, automated, catches personas you'd miss manually. Particularly useful in Enterprise motions.
The agent understands context, not just keywords. This is where Customer Intelligence pays back: every prior conversation informs which title, at which company, in which market, is actually on the committee.
A dead CRM, read before anyone writes to it
This note is shared 1:1
Initiate a dialogueA client had 20,000 contacts sitting dormant in a B2C CRM. The usual move is a blast, then a support queue. I built an agent that read each record first: what the contact had done, when, and what state they were left in. The record decided the message, not the campaign calendar.
Every reply writes back to the record, so the next pass starts from a newer state than the last one. 20k contacts reached on WhatsApp. No spike in customer support.
Hundreds. Dozens. A handful
This note is shared 1:1
Initiate a dialogueAccount-based work fails when every account gets the same attention. I split every target list into three stages and let evidence, not the calendar, move an account between them. Enterprise deals here can take twelve months or more, so the system is built to stay visible for a year, not to close in a week.
One rule does most of the work: an account enters Active Focus only once a challenge is known. If the prospect goes quiet, the deal is removed and the account goes back a stage. It keeps the pipeline honest, and it keeps the hours on the accounts that have earned them.
Tier decides depth. A Tier 1 account may get a dinner or a page of its own. A Tier 3 account gets light, automated touches. Same system, different spend.
One roundtable. Two returns
This note is shared 1:1
Initiate a dialogueA roundtable over a Michelin-star dinner costs €1,500 to €4,500 to run. Nine attendees. The evening is the smallest part of the work: challenges collected in advance, a research profile on every guest, seats planned around shared problems.
The first return came at two months: one attendee signed a €50k proposal. The second came at eight months: a €500M account that never came to the dinner signed a €150k deal. They had been invited, declined, and stayed in every follow-up since.
The dinner was the reason to write. The follow-ups were the reason they remembered.