Christian posts a prompt for one GTM file every AI tool reads
A nine part prompt meant to stop you re-explaining your ICP to every agent you open.
Christian published a prompt that builds one GTM source-of-truth document you hand to every AI tool before it touches your outbound. His argument is that Clay has Sculptor, HubSpot has Breeze, Apollo has its AI assistant and Prospeo has a chat box built in, and every one of them starts from zero on who you sell to.
The prompt asks for nine sections in order. What you sell, who buys it and average deal size. Your TAM split into segments with rough company counts in each. The ICP for your top three segments, covering titles, headcount, tech stack and the signals that mean they are ready to buy. The pains and KPIs each persona owns, written the way they would say it. Your proof, meaning every case study with the real number attached. Your offers ranked from easiest yes to hardest. Search keywords for building lists in Apollo, Clay or Prospeo. A never-say list of claims you cannot back up and words that trip spam filters. And disqualifiers, the accounts you never email.
It also tells the model where to start. If you paste closed-won deals or sales call transcripts, it builds the ICP from those first rather than from whatever it already knows about the company. Output is plain text with headers so it pastes into any tool.
The two sections most context docs skip
The never-say list and the disqualifiers are the parts that do not show up in a normal positioning doc, and they are the two that matter most once an agent is writing copy unsupervised. Without them an agent will reach for a proof point you cannot defend, or mail an account you already agreed to leave alone.
Christian also builds in a guard against the usual failure mode of these prompts, which is a model filling gaps with confident invention.
For people sending, this is a prompt Christian posted, not a tested result. There is no reply rate or campaign attached to it. What it is worth is the structure, a single file that every tool in your stack reads from, so your ICP definition does not drift three different ways across three different assistants.
If something's missing, list it as a question at the end instead of guessing.
Know what is landing before you burn another domain
One email a day. Under three minutes. What the operators found out yesterday.