[reply worthy | day 26] why your DM lead needs to see what you see
(before they’ll trust you to fix it)
Janelle had a white linen shirt she wore in college. Cost her $200 at a boutique in Charleston the summer after sophomore year. The fit was perfect.
She spilled red wine on it at a wedding rehearsal dinner. Tiny drop. Right at the collar.
She went home that night and tried to get it out. Cold water. Salt. The little stain stick from the back of the bathroom drawer. Nothing worked.
She tried bleach next. Diluted. Just on the stain. The wine came out. So did most of the color in the surrounding fabric. The shirt now had a Rorschach-shaped white blotch where the wine had been.
She tried to fix the blotch with a stronger bleach. Made it worse. Tried to “even out the color” with a fabric pen. Worse.
By the end of the weekend, the shirt was unwearable.
Her friend walked into her apartment Sunday afternoon. Saw the shirt on the floor. Picked it up. Looked at the tag.
“Why are you bleaching this? This is dry-clean only.
Janelle had not looked at the tag.
For 3 days she’d been trying to solve a problem with the wrong tool because she’d never bothered to read the instructions printed on the back of the shirt.
I see soooo many DM sequences send 7 messages that “confirm the problem” without ever showing the prospect the tag .
My friend Reid’s DM sequence... the one he paid an agency $2k for... had this exact problem.
The sequence was setup to nod along with everything the prospect said.
“Yeah, the AE pipeline is the bottleneck.” “Yeah, the booking rate is the issue.” “Yeah, we can help with that.”
Confirm. Confirm. Confirm. Pitch.
Sure, it’s comforting. But not very useful on the other end.
So the prospect filed Reid in the same folder as the other 11 people who’d said the same thing that week.
Today, I’m walking you through how to build message 5. The Insight Bridge. The message that makes the prospect think “I hadn’t considered that.” The message that turns you from “another person who confirmed my problem” into “the person who showed me the tag.”
→ Why “confirm the problem” sequences die at message 5 regardless of how good messages 1-4 were
→ The three insight angles you can use to create the “huh” moment
→ How to write a message that earns the call by reframing the problem, not restating it
Let’s start with Janelle’s $200 shirt...
💡 Build 4: The Insight Bridge
After you expand the impact, the prospect sees how big their problem is, but only through their eyes.
The Insight Bridge is the message that reframes the problem so the prospect sees it the way you see it. The “I hadn’t considered that” moment.
If the insight bridge simply confirms what they already knew, the conversation flatlines. You become forgettable.
But, if it reframes the problem, the prospect leans in, and you become the only person in their inbox who showed them the tag.
Three insight angles. Pick the one your offer is built to deliver.
1️⃣ ANGLE 1: The wrong-problem reframe.
“Most teams I see in your situation think the issue is [the surface problem they named]. The pattern I’ve watched is that [surface problem] usually isn’t the actual issue. It’s a symptom of [the upstream problem].”
You’re naming a different root than the one they’ve been working on.
2️⃣ ANGLE 2: The right-problem-wrong-order reframe. “What you’re describing is real, and you’re right about [the surface problem]. The thing that doesn’t usually get sequenced right is that [the order they’re solving it in] tends to make [the surface problem] worse before it gets better. Most teams I see who fix this start with [a different starting point] first.”
You’re naming a sequencing issue.
3️⃣ ANGLE 3: The hidden-variable reframe.
“On [the surface problem], one variable that almost never gets looked at is [the hidden variable]. Most teams either don’t measure it or measure it wrong, which is why [the surface problem] keeps not getting fixed even after they throw resources at it.”
You’re naming a missing input in their analysis.
Whichever angle you pick, the structure is the same. You acknowledge what they said. You name what they haven’t considered. And again… stop short of pitching the solution.
✅ The Insight Bridge ends with: “Curious if you’ve looked at it that way before.”
❌ Not “want to talk about it?” Not “should we get a call on the books?” Just curious.
The question lets the prospect close the loop themselves.
Reid’s agency never wrote an Insight Bridge.
Basically just confirmed the problem. Pitched the call. Got ghosted. Repeat.
Your team sends the discovery messages. The prospect explains their problem.
Your team nods and says “we can help with that.”
And the prospect files you in the same folder as the other 11 people who said the same thing.
🤖 I built a free DM Sequence Grader that scores your sequence (or existing conversations) across 7 dimensions in under 3 minutes.
→ Score your DM sequence or last DM conversation for free here
Before & After
Here’s how to fix it in your own DMs:
1️⃣ Pick your reframe angle based on the offer, not the prospect.
Wrong-problem, right-problem-wrong-order, or hidden-variable.
Your offer is built to deliver one of these reframes more naturally than the other two. Pick the one that matches your work. Build a library of insight starters for that angle.
Train your setter or VA to use them.
2️⃣ Run the Context Gap check on every Insight Bridge before send.
Strip every name, number, and specific detail from the message. Read what’s left.
If the message still works without you in it, the insight isn’t earned. It’s a generic observation.
Reid’s sequence never ran this check. Every “insight” writteen could have been pasted into 200 different threads.
3️⃣ End every Insight Bridge with “curious if,” not “want to talk.”
Your head of growth or VA should be trained to end the message with curiosity, not a call ask. The Insight Bridge earns the call. It doesn’t ask for it. The prospect will ask. Let them.
The fix isn’t smarter copy. It’s a reframe the prospect hadn’t considered before they read your message.
That’s it.
Here’s what you learned today:
→ The Insight Bridge is the message that reframes the prospect’s problem so they see what you see. The “I hadn’t considered that” moment.
→ Most sequences confirm the problem instead of reframing it. The prospect categorizes you with everyone else and forgets you exist.
→ The fix is picking one of three reframe angles (wrong-problem, right-problem-wrong-order, hidden-variable) and ending with curiosity instead of a call ask.
Start with just one:
Pull up your message 5 in your most-used sequence.
Read it. Ask yourself: “Does this confirm or reveal?”
If it confirms, rewrite it as an Insight Bridge with one of the three angles. Send it to the next prospect who reaches message 5.
Over 31 days, I’m walking you through:
→ How to write a Value Drop that earns the call without asking for it
→ How to write a close that works because 6 messages earned it
→ How to build a recovery system calibrated to WHERE in the sequence they went silent
→ The full sequence assembly, every piece, scored against every diagnostic from the series
→ The May Vault: every diagnostic, every builder, every assembly tool in one place
→ Built to Reply: the 30-day rebuild of every system that surrounds the sequence
→ The first 7 days of June: the prospect targeting system that determines who ever sees your sequence
Today is Day 26.
Today’s mega-prompt doesn’t just write you an Insight Bridge.
It takes your offer details and the prospect’s stated challenge, picks the right reframe angle, and generates the message with the curiosity-question close pre-built.
Paid members get:
✔ The Insight Message Builder
→ Paste your offer and the prospect’s challenge, get back the recommended reframe angle and a paste-ready Insight Bridge
→ Each output runs through the Context Gap check so the insight is provably earned
→ Pre-checked for confirmation language, generic observations, and premature pitching
✔ A reframe library: 10 insight starters for each of the three angles, customizable per ICP
✔ The Context Gap diagnostic for any message your team writes
