The Only AI Input Your Will Ever Need to Make Your GTM go from WTF to OMG
Pain Segment was never the deepest move. This is.
The Asymmetry Engine
A founder showed me his dashboard.
He runs an AI tool that watches alcohol ads for large consumer brands. White Claw. Aperol. Suntory. The thing scans a video, flags music it can't license, flags any frame that implies the drink is solving someone's anxiety, flags whatever six dozen things a Czech regulator can sue you for. He'd just gotten his first wave of customers and was setting up cold email for the first time. He led every email with a screenshot of his dashboard.
I told him to scrap the screenshot.
Same week, a guy on the call before him runs go-to-market for a lending infrastructure startup. Eighteen customers. Six-figure ACVs. Each customer launches a few products a year — credit cards, buy-now-pay-later, personal loans. He's tried everything. PQS-style outbound. Signal scraping. Predictleads jobs. He can find the companies that announced new lending products. He just can't get a reply.
Both of them are stuck. Both of them are working hard. Both of them are about to learn the same thing, which is that pain segment isn't the deepest move I teach.
It's an application of the deepest move I teach.
The deepest move is information asymmetry. Manufacture more information about the buyer's situation than the buyer has. Then deliver the insight as a complete gift the buyer can use without ever replying to you. Pre-AI, only the top 1% of reps could do this — the ones who'd lived inside one customer for so long they basically became them. Post-AI, anyone with eighteen customer transcripts and Claude Code can do it across an entire customer corpus in a long afternoon.
I'm calling the system that produces it the asymmetry engine.
Pain Segment, PVP, PQS, Working Backwards, Old World vs. Jordan's World — the whole framework lattice you've been reading from me for the last year — they're all applications of this single underlying move. I want to lay it out end-to-end. The law that runs underneath. The four moves that flip the game. The mining loop you can run on your customer base this week. And the way the existing frameworks slot in once the master frame is clear.
This one's long. Pour another coffee.
The Asymmetry Law
Sales is a power game. Power flows from information asymmetry. Whoever knows more about the buyer's actual situation has the upper hand. That's the whole thing.
Most reps lose this game on day one. They walk in with a deck. The buyer walks in with their actual job, their actual quarterly number, their actual fired-CFO ghost, their actual lawsuit they almost lost in Q2, and the ten Slack threads about whether the thing the rep sells will save them or get them fired. The buyer has more information than the rep. The asymmetry runs the wrong way. The pitch fails. The rep blames the copy.
Top-1% reps have always inverted this. They've sold to enough people in the same role to know, before the buyer opens their mouth, what the buyer is going to say next. They know the lawsuit. They know the number. They know the ghost. When the buyer talks, they're not gathering — they're confirming. That's why those reps close.
The catch was always that you had to spend years being them to know them. The German entrepreneur I always think about wanted to start a dental billing company. So he found a dentist in San Francisco and worked for free for six months filing bills. He learned that molar replacements are the most common thing a dentist invoices. He learned every step of the process from the inside. Then he built software that replaced his job. His first customer was the dentist he'd been working for. Every other customer felt like he was reading their mind, because effectively he was.
That used to be the whole skill. Live inside one customer until your guesses about every other customer were ground truth.
It isn't anymore. The asymmetry engine is what replaces it.
The god-customer question
The new question — the one nobody could ask before language models — is this. If your buyer were a god, with infinite reach, and they had access to everything you know about every customer who came before them, what would they ask?
Not what's their pain. Not what's their persona. Not how do I personalize the second line of the email.
What would a god-buyer want to know?
I asked the lending-infrastructure guy this on the call. He had eighteen customers. They'd launched somewhere between two and four products each. That's roughly seventy product launches across his platform — credit cards, buy-now-pay-later, personal loans, refi products. Every single one had transaction data sitting in his database. Every single one had a story. Some of them died at six months. Some of them tripled the customer's portfolio. He'd never asked, across the seventy of them, what the launch-day signal was that separated the dead from the tripled.
A god-buyer would. A god-buyer doesn't care about his dashboard. A god-buyer wants to know: if I launch a credit card next quarter at 7% APR, what's my pickup curve going to look like, based on every other 7% credit card that launched on this platform?
That question wasn't askable in 2023. The data was sitting in a Postgres table. The customer was sitting in their office worrying about it. Nobody could connect the two without a six-month consulting engagement and a SQL analyst. Now you can connect them with a Claude Code session and a sample of the schema.
This is the move. Stop selling product. Start asking the god-buyer question.
Why AI made this not just possible but necessary
A buddy of mine is an AE at a payroll-and-benefits company. Top quartile of his team. He told me last week that the SDRs at his company aren't sourcing him pipeline anymore. They got replaced. Not by him. By Claude. The average AE got replaced too — the one who sends I saw you raised money, can I have some. The one who sends I noticed you're hiring a benefits administrator, our payroll product is the best solution. That whole tier is gone. AI does it now. Probably better. Definitely cheaper.
So the floor moved up. The bar to get a meeting got higher. If your message reads like the average AE wrote it, your message is competing with a robot army doing the same thing for free.
The only thing that beats the robot army is data the robot army doesn't have.
That's your customer interviews. That's your transaction histories. That's your support transcripts. That's the seventy product launches sitting in your back-end. None of it's on the public web. None of it's in the LLM's training set. None of it can be replicated by the recruiter sending the "I saw you're hiring, we have cheap labor in the Philippines" email — and let me tell you, the volume of recruiters sending that exact email is greater than atoms in the universe by maybe one rounding error. They are competing in the saturation zone. You don't have to.
Your customer corpus is the moat. It's the only moat that works in 2026. The asymmetry engine is the machine that turns the corpus into messages that can't be replicated.
That's the law. Now the moves.
The Inversion
The lending-infrastructure guy on the call asked me a fair question. How do you actually do this? Like, what's the practice?
The practice is four moves. Three of them are about how you think before you ever open a Claude Code window. The fourth one is the running. Today's article is about the thinking move-set, then the running. Let's start with the thinking.
The kidnap-engineer test
Imagine your customer broke into your office, kidnapped your engineering team, and got root access to your data. They can only do three things before the cops arrive. What are they?
Sounds insane. It works. The reason it works is that it forces you off your product and onto their actions. An engineer with access to your seventy product launches isn't going to look at your dashboard. They're going to write three SQL queries that answer what they personally need to ship next month and have nothing else.
For the lending guy, those three queries probably look like give me the pickup curve for every credit card we launched at 6.8% to 7.2% APR, normalized for issuer size. And give me the sign-up bonus value where pickup peaks and starts to flatten. And give me the personal-loan products that died inside six months and what they had in common.
Three queries. Three answers. Three messages he can ship to seventy companies that he knows are thinking about lending products this year.
That's the kidnap-engineer test. It's the inversion of the GTM question. You don't ask what would my buyer be persuaded by? You ask what would my buyer's most resourceful colleague steal if they could? Then you ship them what they would have stolen, without the kidnapping.
Inhabit the customer's mind
The quality of every piece of GTM work you do is set by how much of the buyer's mind you can inhabit.
I mean this almost literally. The German dental guy who worked at the dentist for six months — that's the gold standard. He went and lived inside the buyer until he stopped guessing. The reason he was the gold standard is that nobody else was willing to do it. Working at a dental office for six months for free is unpleasant. So almost no one did it. So the few who did had a permanent edge.
The asymmetry engine isn't a substitute for inhabiting the customer's mind. It's the only known way to inhabit a hundred customers' minds at once instead of one. You take every transcript a customer has ever recorded, every email a customer has ever sent you, every transaction in your back-end, and you ask Claude to act as this person at this company launching this kind of product. What questions would you ask of this data?
Then you read the answers. Then you push back. Then you ask three more times until the answers stop sounding like a robot puked them up. Then you go to a real customer — even just one — and ask, would you respond to this? And you listen to the no.
That's the inhabit step. The model is your speed. The customer is your ground truth. You need both.
The differentiation trap
The reason this matters more than ever is that everyone else is sending the same message.
A guy on the call last week wanted to sell a recruiting service. Cheap labor from the Philippines, 30-40% discount on hires. He asked me what he should write in the cold email. I told him not to send it. Every recruiting agency on Earth is sending the exact same email. I saw you're hiring a senior engineer. We can save you 40%. It's not that the offer is bad. The offer might be great. The problem is that the buyer has heard the same sentence eight hundred times this quarter. The message has zero differentiation. The buyer has no reason to read past the subject line.
The asymmetry engine breaks the trap by giving you something nobody else can say. Not because you're a better writer. Because you have data they don't have, and a question they couldn't ask, and an answer they didn't get last week from any of the eight hundred clones.
When you have that, the message practically writes itself. When you don't, no amount of merge-tag wizardry saves you.
That's the inversion. Now the engine itself.
Who Gets This
You've got the doctrine. Below the line is the build.
Free: what you just read — the law, the inversion, why it matters now.
$50/mo (most readers start here): the mining loop — the actual Claude Code prompt, the four data layers, the worked example for the lending case, the permissionless-gift template, and the way every existing framework I teach slots into this master frame.
$2,499/yr: Every tool I ship. Edge Copilot is how you talk to all of it through Claude Code. Current tools: Edge Copilot, AutoClaygent, Agent 7, Who to Target and What to Say, Blueprint Cloud, Technology Finder, Video List Extractor, Competitor Monitor, LinkedIn Engagement, Domain & LinkedIn Finder, Dossier Builder, PDF Contact Finder. Whatever ships next is included. Plus all 3 courses and weekly office hours.