“Paragraph two is your product. Cut it, and find the thing she thinks is fine.”
Keenan · Gap Prospecting · every draft
Judged on the eight elements before it leaves.Find the crack. Every cold touch, judged before it leaves.
Gap Prospecting is Keenan’s outbound discipline: find the thing the buyer believes is fine, open a loop they cannot close, prove it with three findings, then redefine the problem and ask for almost nothing. Replicate Labs installs the architecture once. Keenan then reads every draft against it, cuts what fails, and says what the next version should say.
The crack under the message. The loop on top of it.
Every cold touch makes two sales, in order. Sale one is intrigue: the subject line opens a loop the brain cannot leave unresolved. Sale two is interest: the proof and the redefine answer the buyer’s three questions. Could I have this problem, is it big enough, can this person help. Under all of it sits the crack, silent in the message and the spine of it.
Gaps your SIEM isn’t catching
You’ve tuned the SIEM twice this year and the alert volume finally looks right. Most teams stop there.
- 3 of 11 log sources at one 400-seat fintech never reached the SIEM
- 41% of its alerts traced back to two rules
- The incident that mattered came in through source four
This is not an alerting problem. It is a coverage blind spot.
The SOC lead you posted for last week inherits it on day one.
Want the three findings? Yes or no is fine. No meeting.
A subject line is a loop, or it is deleted.
One to four words. If the line can be finished with a full stop and sounds complete, it is a label and the buyer files it. If it makes the reader ask “which ones?”, it is a loop.
Finished. The reader is done.
Which gaps? The Zeigarnik effect does the opening for you.
Intrigue first: make them stop. Interest second: make them act. If sale one fails, nothing else in the email matters, however good the offer is.
Outbound starts with a Problem Identification Chart: the fixed reference of buyer problems, impacts and root causes. Without it, reps invent problems on the fly and the message reads like a guess.
Binary yes or no. Sharing notes, never selling time. Never a meeting in first touch. Earn the reply; the meeting comes later.
The email, judged before it sends.
Paste the draft, or ask Keenan to write it from your Problem Identification Chart. Either way it is scored on the eight elements the method demands before it leaves: problem first, the crack and the redefine, forensic proof, the loop, future connection, the ask, relevance, voice. A product mention or a meeting ask caps the CTA score at 20, however good the rest is.
- Cold email, call opener, LinkedIn DM, voicemail, cadence. Each element audited against the architecture.
- Scored on eight dimensions. A composite, the biggest gap, and the line to cut.
Then talk it through. The rewrite is a call with Keenan; typing is the fallback.
Gaps your SIEM isn’t catching
You’ve tuned the SIEM twice this year and the alert volume finally looks right. Most teams stop there.
Our platform gives you full coverage across every log source with AI-driven detection, and I’d love to show you a quick demo this week.
It isn’t an alerting problem. It’s a coverage blind spot the tuning can’t see.
Want the three findings? Yes or no is fine.
Gap Prospecting, in short.
The architecture, element by element, in Keenan’s terms.
What is Gap Prospecting?
The outbound discipline built on Gap Selling. Same diagnostic foundation (current state, future state, the gap, root cause), applied to cold email, cold call, LinkedIn DM, voicemail and cadence. Built on a Problem Identification Chart, governed by the two sales (intrigue then interest), and constructed element by element: the crack, the subject line, the opening, the proof, the redefine, the future connection and the CTA. It is an architecture for outbound, and each element has to be built for the buyer.
What is “the crack”?
The thing the buyer believes is fine that is actually the root cause. It is the gap between the buyer’s current theory about why things are not working and the real explanation. The crack is silent in the message but it is the spine of the message. Find the crack and the email writes itself. Miss it, and you are restating the buyer’s own theory back to them.
Why does the subject line have to “open a loop”?
The Zeigarnik effect: the brain cannot leave an open loop unfinished. “Gaps your SIEM isn’t catching” works because the reader cannot stop wondering which gaps. “The demo trap” does not work; it is a finished label. One to four words. No questions. No buzzwords. If the subject line can be completed with a full stop and sounds done, it is a label. If it demands a question mark in the reader’s head, it is a loop.
What counts as forensic proof?
At least three distinct, numbered findings from a real engagement, each a different dimension of the problem. Not one pattern restated three ways. Numbers, not adjectives. Three specific findings the buyer recognises, because a round stat convinces nobody.
Why never ask for a meeting in first touch?
The buyer has zero confidence in you at first touch. A meeting ask is expensive. A binary yes-or-no on a single sharp question costs nothing. The CTA must match the buyer’s confidence level. Offer minus Ask equals Value: the offer should promise insight (notes, findings, prompts) and the ask should cost the buyer almost nothing. A calendar link in touch one is a banned pattern.
How is this different from Gap Selling?
Gap Selling is for live deals: discovery, demo, close. Gap Prospecting is for the conversations that have not started yet. Same foundation, different surface area. Gap Prospecting earns the meeting. Gap Selling earns the decision.
Is this for SDRs only?
No. AEs use it for re-engagement emails, prospecting into new buying committees and pre-call outreach. Same discipline, different volume.
Bring the sequence you were about to send. Keenan will take it apart in front of you.
Your last five cold emails, your Problem Identification Chart, one working session. Watch each element get judged, cut and rewritten, then decide whether every send your team makes should go through it.