You (or your agent) spent 15 minutes researching your prospect.

You found out where they went to college. You read their last three LinkedIn posts. You noticed they ran a marathon last spring. You opened your email with “Hey Sarah, saw you’re a fellow Stanford alum and just crushed a half marathon — respect!”

You sent 200 of those.

You got two replies. Both said “unsubscribe.”

Here’s the uncomfortable truth: you weren’t doing hyper-personalization. You were doing hyper-stalking and we’re sooo over it.

In 2026, the game has changed in ways most founders haven’t caught up to. AI flooded inboxes with “personalized” emails that all start the same way — your name, your school, your recent post, your job title. Prospects got so numb to this pattern that their brains filter it out in under two seconds. Faster than you can say “I hope this finds you well.”

Which it doesn’t. Because that line is dead.

I’ve talked about this before — the shift isn’t from low-effort to high-effort. It’s from about you to about the problem.

The single insight that separates the 4% reply rates from the 0.4% ones: the prospect doesn’t care about you knowing some facts about them. They don’t care about your company, your funding, or your story. They care about one thing — is this person (you) aware of the exact problem I’m fighting right now?

That’s it. That’s the whole game.

Nobody needs more people “to know” them, but we all need someone to solve our immediate problems.

Old personalization: “I noticed you went to MIT.”

New personalization: “Most SaaS teams scaling past 50 people watch their onboarding completion rate fall off a cliff. Usually around the time they stop doing white-glove demos.”

The second message is personalized to their reality, not their résumé. I didn’t need to stalk their LinkedIn to write it. I needed to understand (or guess) their situation enough to name the pain they’re living.

This is the difference between mentioning someone’s marathon and knowing exactly what mile they hit the wall.

The prospect reads that second message and (hopefully) thinks: this person has been inside companies like mine. That thought — that split-second recognition — is worth more than a thousand correctly spelled names.

Short. Shorter than you think. Under 100 words is an ideal, not a limitation.

Here’s the anatomy:

You open with the problem. Not “I saw that you...” — the problem itself. State it like a doctor names a symptom. Precise. No warm-up.

Then you briefly make the cost of that problem visible. Not in an aggressive way — just enough to confirm you understand the stakes. One sentence. Maybe two.

Then you connect it to an outcome or a question. Not a 30-minute demo request. Something almost frictionless: “Worth a look?” or “Is this on your radar for Q2?”

This simple structure is enough. Problem → Stakes → Low-friction ask (PAS).

The PAS framework (it's official name) — Problem, Agitate, Solve — has been around for decades for a reason. It works because it mirrors how human decision-making actually functions.

We notice pain before we notice opportunity. We act to escape discomfort before we act toward reward. Any message that leads with your solution before establishing the problem is asking the prospect to care about an answer before they’ve felt the question.

There’s no single best framework. There’s the best framework for the specific situation. If you only master PAS I described above, you’ll be fine.

But let’s expand your horizons too;

Typically, PAS works when your prospect already knows they have a problem but hasn’t made fixing it a priority. You’re not educating them — you’re reactivating urgency. A team lead at a B2B SaaS company who’s watched their churn tick up every quarter knows something’s wrong. They just haven’t acted. PAS reminds them why acting now costs less than waiting six more months.

Here’s what that looks like in practice. Say you’re selling a team knowledge management tool — something like Fibery — targeting an engineering lead at a 40-person SaaS company. The wrong message looks like this:

“Hey Marcus, saw you’re leading engineering at Acme and just shipped your v2 — congrats! I’m reaching out because we help teams like yours stay aligned. Would love 15 minutes to show you what we’ve built.”

That’s about Marcus. Marcus does not care about Marcus in the context of his inbox. He’s drowning. The right message looks like this:

“Most eng teams past 30 people hit the same wall: decisions get made in Slack, rationale never gets written down, and six months later nobody knows why the architecture looks the way it does. The new hire onboarding cost alone is brutal. Fibery connects the decision trail from product spec to code. Worth a look?”

Same product. Same prospect. Completely different nerve. The second message works because Marcus reads it and thinks: someone has been inside teams like mine. That thought takes less than three seconds to form. That’s your entire window.

BAB — Before, After, Bridge — is the right tool when your solution creates a visual transformation.

Before: “Right now, your SDRs spend 40% of their time on manual data entry.” After: “In six weeks, that number is zero, and they’re back on the phone.” Bridge: “We built the connection layer that makes that switch.” BAB is a movie trailer for your product. Use it when the contrast between before and after is dramatic enough to make someone stop scrolling.

Josh Braun’s 4T framework is what you reach for when the deal is large and the prospect is sophisticated. You need a trigger — a real, observable signal that this is the right moment to reach out (a funding announcement, a new hire, a product launch).

Then a think — a question that reframes their current approach. Not “do you have this problem?” but “most teams that do X end up hitting Y — have you run into that?” Then a third-party credibility point: a company they’ve heard of that faced the same thing. Then a soft talk — are you the right person to decide on this? This framework takes work. You can’t fake the trigger. But for the deals worth fighting for, 4T gets meetings that PAS can’t.

For high-volume outreach — agents, sequences, automated DMs — NOR is your workhorse. Needle, Outcome, Request. What specific needle are you moving? What does moving it mean for their business? What’s your ask?

Forty words. Forty-five if you need a breath. NOR survives AI spam filters because it’s so specific and so brief that it reads like a human who respects the prospect’s time. Which, if you’re thinking about it correctly, is exactly what it is.

This is the part many founders also miss.

In 2026, cold outreach lives across every asynchronous channel where your prospect already spends their working day. LinkedIn DMs still get higher reply rates than cold email for B2B — but it’s changing quickly. Slack communities, Discord servers, and even WhatsApp broadcast lists have become legitimate outreach channels for the right verticals.

The rule doesn’t change. The medium and the channel does.

A cold LinkedIn DM that opens with “I loved your recent post on...” gets ignored. A cold LinkedIn DM that opens with “Most growth teams I talk to are seeing their LinkedIn CPL go up 30% this year while their email lists decay — is that pattern showing up for you?” much more likely gets a reply.

The channel is just the pipe. The problem-first message is the water.

What’s changed operationally: Your technical setup now matters as much as your copy. In email, if you’re sending from your primary domain (yourcompany.com), you’re already behind. Secondary domains (getcompany.com, trycompany.io) keep your sender reputation clean while you’re in the testing phase. Your SPF, DKIM, and DMARC records need to be configured correctly or you’re landing in Promotions before anyone reads a word. Gmail and Outlook have hardened their filters significantly. Infrastructure is table stakes.

AI sales agents can now research prospects, identify trigger events, write first drafts, and send messages across multiple channels simultaneously. That sounds like a distribution advantage. And it is — but only if the underlying message is right.

Here’s where many make the mistake: they automate the old playbook. They build agents that scrape LinkedIn for profile details and plug them into templated “personalized” intros. What they’ve built is a faster way to be ignored at scale.

The right way to think about agents in outreach: they should be doing the research legwork that surfaces real triggers — a company’s recent pricing change, a job posting that signals a strategic shift, a product launch that creates a new problem they’re now facing.

The agent’s job is to find the signal. Your job is to turn that signal into a problem statement the prospect recognizes as true.

A well-built agent running a 4T framework — with a real trigger, a real reframe, and a real soft ask — can outperform a human SDR on volume without sacrificing the quality of the signal. The output still sounds human because the underlying logic is human. The agent is doing the detective work. You’re providing the insight about what the clues mean. And agent can improve itself and even frameworks it’s using as it goes.

What I think is the winning motion in 2026:

• agents find the signal,

• humans (or possibly well-prompted AI) write the problem framing once per ICP segment,

• agents distribute it with the right trigger context stitched in.

You’re not automating personalization — you’re automating trigger identification so you can personalize around problems that are actually live.

And you should always, always, always review any message before it gets sent out en masse.

Before you send anything — email, DM, Slack message — read it out loud.

If you wouldn’t say it to a person standing next to you at a professional event, it’s not good enough. Delete it. Rewrite it. The words you use with a real human at a real event are the words that work now.

The English grammar and polite blabla they taught you at school is over.

“I hope this finds you well” — would you say that at a party? No. You’d say: “Hey, I keep seeing teams in your space struggle with X. Is that something you’re dealing with?”

See the difference? Feel the difference? That’s what you can send.

If you’re a founder doing your own outreach right now — or building an agent to do it — here’s your operating framework:

Pick one ICP segment. Understand their world deeply enough to name three specific problems they’re living with right now. Not hypothetically, but Right now, in Q2 of this year.

Write one problem-first message for each. Keep each under 80 words. Don’t mention your company name until the second message. Choose the channel where they actually have their attention — LinkedIn before email if you’re in B2B SaaS, Discord or Slack if you’re in developer tooling, email if you have a warm signal, etc.

Test your messages. When a message gets a reply, ask yourself: what did they recognize? That’s the nerve you found. Go back and make the next message hit that same nerve harder.

The founders who win outreach in 2026 aren’t the ones with the best product. They’re the ones who can make a stranger feel most understood in forty words.

That’s not a sales skill. That’s a writing skill. And it’s learnable.

Hope you'll go and use it now!
Till next time, let’s BUILD BETTER!

Cheers,

Pete (aka BFG)

All examples use Fibery as the product. ICP: B2B SaaS companies, 30–150 people. The pattern is the same across every framework: problem before product, always.

BAB — Head of Product, Series A company

Before:

“Hi Jana, loved your recent post on async-first culture. We’re building tools for teams like yours and I think there’s a strong fit here. Happy to jump on a call?”

After:

“Right now: your product context lives in six tools. Notion for specs, Linear for tasks, Confluence for docs, Slack threads for decisions — none of it connected. Six months from now: one place where the spec, the ticket, the decision, and the outcome are all linked. That’s what Fibery does. Is this the kind of mess you’re currently navigating?”

NOR — High-volume, agent-run sequence, targeting Ops/RevOps leads

Before:

“Hi Alex, I work with operations teams and wanted to reach out about our knowledge management platform. We’ve helped companies like yours improve team alignment. Are you free for a quick call this week?”

After:

“Reducing the time your team spends re-explaining context that should already be written down — that’s what we move. Teams using Fibery cut onboarding ramp by ~30%. Right person to look at this?”

4T — LinkedIn DM, VP Engineering at a company with 3 active senior engineer job postings

Before:

“Hey David, congrats on the growth — saw you’re scaling the team! We help engineering orgs stay aligned as they grow. Would love to connect.”

After:

“Saw you’re hiring three senior engineers right now. Most eng orgs that scale that fast tell me the same thing three months later: the new hires are productive on tasks but completely blind to why decisions were made. It’s an undocumented architecture problem, not a skills problem. Seen that pattern yet? [Similar Company] fixed it with Fibery before their Series B. Happy to share how.”

LinkedIn DM (channel shift, problem-first logic unchanged) — Head of Product

Before:

“Hi Sarah! I love what you’re building at [Company]. I work with product teams on knowledge management and thought there might be a fit. Open to connecting?”

After:

“Quick observation from talking to a lot of product teams: the bigger the roadmap, the more the ‘why’ behind decisions disappears into old Slack threads. By the time a feature ships, half the team has forgotten the original constraint. Is that a problem you’re actively solving for, or still on the backlog?”

Let's connect on Farcaster: https://farcaster.xyz/bfg 😉

You (or your agent) spent 15 minutes researching your prospect.

You found out where they went to college. You read their last three LinkedIn posts. You noticed they ran a marathon last spring. You opened your email with “Hey Sarah, saw you’re a fellow Stanford alum and just crushed a half marathon — respect!”

You sent 200 of those.

You got two replies. Both said “unsubscribe.”

Here’s the uncomfortable truth: you weren’t doing hyper-personalization. You were doing hyper-stalking and we’re sooo over it.

In 2026, the game has changed in ways most founders haven’t caught up to. AI flooded inboxes with “personalized” emails that all start the same way — your name, your school, your recent post, your job title. Prospects got so numb to this pattern that their brains filter it out in under two seconds. Faster than you can say “I hope this finds you well.”

Which it doesn’t. Because that line is dead.

I’ve talked about this before — the shift isn’t from low-effort to high-effort. It’s from about you to about the problem.

The single insight that separates the 4% reply rates from the 0.4% ones: the prospect doesn’t care about you knowing some facts about them. They don’t care about your company, your funding, or your story. They care about one thing — is this person (you) aware of the exact problem I’m fighting right now?

That’s it. That’s the whole game.

Nobody needs more people “to know” them, but we all need someone to solve our immediate problems.

Old personalization: “I noticed you went to MIT.”

New personalization: “Most SaaS teams scaling past 50 people watch their onboarding completion rate fall off a cliff. Usually around the time they stop doing white-glove demos.”

The second message is personalized to their reality, not their résumé. I didn’t need to stalk their LinkedIn to write it. I needed to understand (or guess) their situation enough to name the pain they’re living.

This is the difference between mentioning someone’s marathon and knowing exactly what mile they hit the wall.

The prospect reads that second message and (hopefully) thinks: this person has been inside companies like mine. That thought — that split-second recognition — is worth more than a thousand correctly spelled names.

Short. Shorter than you think. Under 100 words is an ideal, not a limitation.

Here’s the anatomy:

You open with the problem. Not “I saw that you...” — the problem itself. State it like a doctor names a symptom. Precise. No warm-up.

Then you briefly make the cost of that problem visible. Not in an aggressive way — just enough to confirm you understand the stakes. One sentence. Maybe two.

Then you connect it to an outcome or a question. Not a 30-minute demo request. Something almost frictionless: “Worth a look?” or “Is this on your radar for Q2?”

This simple structure is enough. Problem → Stakes → Low-friction ask (PAS).

The PAS framework (it's official name) — Problem, Agitate, Solve — has been around for decades for a reason. It works because it mirrors how human decision-making actually functions.

We notice pain before we notice opportunity. We act to escape discomfort before we act toward reward. Any message that leads with your solution before establishing the problem is asking the prospect to care about an answer before they’ve felt the question.

There’s no single best framework. There’s the best framework for the specific situation. If you only master PAS I described above, you’ll be fine.

But let’s expand your horizons too;

Typically, PAS works when your prospect already knows they have a problem but hasn’t made fixing it a priority. You’re not educating them — you’re reactivating urgency. A team lead at a B2B SaaS company who’s watched their churn tick up every quarter knows something’s wrong. They just haven’t acted. PAS reminds them why acting now costs less than waiting six more months.

Here’s what that looks like in practice. Say you’re selling a team knowledge management tool — something like Fibery — targeting an engineering lead at a 40-person SaaS company. The wrong message looks like this:

“Hey Marcus, saw you’re leading engineering at Acme and just shipped your v2 — congrats! I’m reaching out because we help teams like yours stay aligned. Would love 15 minutes to show you what we’ve built.”

That’s about Marcus. Marcus does not care about Marcus in the context of his inbox. He’s drowning. The right message looks like this:

“Most eng teams past 30 people hit the same wall: decisions get made in Slack, rationale never gets written down, and six months later nobody knows why the architecture looks the way it does. The new hire onboarding cost alone is brutal. Fibery connects the decision trail from product spec to code. Worth a look?”

Same product. Same prospect. Completely different nerve. The second message works because Marcus reads it and thinks: someone has been inside teams like mine. That thought takes less than three seconds to form. That’s your entire window.

BAB — Before, After, Bridge — is the right tool when your solution creates a visual transformation.

Before: “Right now, your SDRs spend 40% of their time on manual data entry.” After: “In six weeks, that number is zero, and they’re back on the phone.” Bridge: “We built the connection layer that makes that switch.” BAB is a movie trailer for your product. Use it when the contrast between before and after is dramatic enough to make someone stop scrolling.

Josh Braun’s 4T framework is what you reach for when the deal is large and the prospect is sophisticated. You need a trigger — a real, observable signal that this is the right moment to reach out (a funding announcement, a new hire, a product launch).

Then a think — a question that reframes their current approach. Not “do you have this problem?” but “most teams that do X end up hitting Y — have you run into that?” Then a third-party credibility point: a company they’ve heard of that faced the same thing. Then a soft talk — are you the right person to decide on this? This framework takes work. You can’t fake the trigger. But for the deals worth fighting for, 4T gets meetings that PAS can’t.

For high-volume outreach — agents, sequences, automated DMs — NOR is your workhorse. Needle, Outcome, Request. What specific needle are you moving? What does moving it mean for their business? What’s your ask?

Forty words. Forty-five if you need a breath. NOR survives AI spam filters because it’s so specific and so brief that it reads like a human who respects the prospect’s time. Which, if you’re thinking about it correctly, is exactly what it is.

This is the part many founders also miss.

In 2026, cold outreach lives across every asynchronous channel where your prospect already spends their working day. LinkedIn DMs still get higher reply rates than cold email for B2B — but it’s changing quickly. Slack communities, Discord servers, and even WhatsApp broadcast lists have become legitimate outreach channels for the right verticals.

The rule doesn’t change. The medium and the channel does.

A cold LinkedIn DM that opens with “I loved your recent post on...” gets ignored. A cold LinkedIn DM that opens with “Most growth teams I talk to are seeing their LinkedIn CPL go up 30% this year while their email lists decay — is that pattern showing up for you?” much more likely gets a reply.

The channel is just the pipe. The problem-first message is the water.

What’s changed operationally: Your technical setup now matters as much as your copy. In email, if you’re sending from your primary domain (yourcompany.com), you’re already behind. Secondary domains (getcompany.com, trycompany.io) keep your sender reputation clean while you’re in the testing phase. Your SPF, DKIM, and DMARC records need to be configured correctly or you’re landing in Promotions before anyone reads a word. Gmail and Outlook have hardened their filters significantly. Infrastructure is table stakes.

AI sales agents can now research prospects, identify trigger events, write first drafts, and send messages across multiple channels simultaneously. That sounds like a distribution advantage. And it is — but only if the underlying message is right.

Here’s where many make the mistake: they automate the old playbook. They build agents that scrape LinkedIn for profile details and plug them into templated “personalized” intros. What they’ve built is a faster way to be ignored at scale.

The right way to think about agents in outreach: they should be doing the research legwork that surfaces real triggers — a company’s recent pricing change, a job posting that signals a strategic shift, a product launch that creates a new problem they’re now facing.

The agent’s job is to find the signal. Your job is to turn that signal into a problem statement the prospect recognizes as true.

A well-built agent running a 4T framework — with a real trigger, a real reframe, and a real soft ask — can outperform a human SDR on volume without sacrificing the quality of the signal. The output still sounds human because the underlying logic is human. The agent is doing the detective work. You’re providing the insight about what the clues mean. And agent can improve itself and even frameworks it’s using as it goes.

What I think is the winning motion in 2026:

• agents find the signal,

• humans (or possibly well-prompted AI) write the problem framing once per ICP segment,

• agents distribute it with the right trigger context stitched in.

You’re not automating personalization — you’re automating trigger identification so you can personalize around problems that are actually live.

And you should always, always, always review any message before it gets sent out en masse.

Before you send anything — email, DM, Slack message — read it out loud.

If you wouldn’t say it to a person standing next to you at a professional event, it’s not good enough. Delete it. Rewrite it. The words you use with a real human at a real event are the words that work now.

The English grammar and polite blabla they taught you at school is over.

“I hope this finds you well” — would you say that at a party? No. You’d say: “Hey, I keep seeing teams in your space struggle with X. Is that something you’re dealing with?”

See the difference? Feel the difference? That’s what you can send.

If you’re a founder doing your own outreach right now — or building an agent to do it — here’s your operating framework:

Pick one ICP segment. Understand their world deeply enough to name three specific problems they’re living with right now. Not hypothetically, but Right now, in Q2 of this year.

Write one problem-first message for each. Keep each under 80 words. Don’t mention your company name until the second message. Choose the channel where they actually have their attention — LinkedIn before email if you’re in B2B SaaS, Discord or Slack if you’re in developer tooling, email if you have a warm signal, etc.

Test your messages. When a message gets a reply, ask yourself: what did they recognize? That’s the nerve you found. Go back and make the next message hit that same nerve harder.

The founders who win outreach in 2026 aren’t the ones with the best product. They’re the ones who can make a stranger feel most understood in forty words.

That’s not a sales skill. That’s a writing skill. And it’s learnable.

Hope you'll go and use it now!
Till next time, let’s BUILD BETTER!

Cheers,

Pete (aka BFG)

All examples use Fibery as the product. ICP: B2B SaaS companies, 30–150 people. The pattern is the same across every framework: problem before product, always.

BAB — Head of Product, Series A company

Before:

“Hi Jana, loved your recent post on async-first culture. We’re building tools for teams like yours and I think there’s a strong fit here. Happy to jump on a call?”

After:

“Right now: your product context lives in six tools. Notion for specs, Linear for tasks, Confluence for docs, Slack threads for decisions — none of it connected. Six months from now: one place where the spec, the ticket, the decision, and the outcome are all linked. That’s what Fibery does. Is this the kind of mess you’re currently navigating?”

NOR — High-volume, agent-run sequence, targeting Ops/RevOps leads

Before:

“Hi Alex, I work with operations teams and wanted to reach out about our knowledge management platform. We’ve helped companies like yours improve team alignment. Are you free for a quick call this week?”

After:

“Reducing the time your team spends re-explaining context that should already be written down — that’s what we move. Teams using Fibery cut onboarding ramp by ~30%. Right person to look at this?”

4T — LinkedIn DM, VP Engineering at a company with 3 active senior engineer job postings

Before:

“Hey David, congrats on the growth — saw you’re scaling the team! We help engineering orgs stay aligned as they grow. Would love to connect.”

After:

“Saw you’re hiring three senior engineers right now. Most eng orgs that scale that fast tell me the same thing three months later: the new hires are productive on tasks but completely blind to why decisions were made. It’s an undocumented architecture problem, not a skills problem. Seen that pattern yet? [Similar Company] fixed it with Fibery before their Series B. Happy to share how.”

LinkedIn DM (channel shift, problem-first logic unchanged) — Head of Product

Before:

“Hi Sarah! I love what you’re building at [Company]. I work with product teams on knowledge management and thought there might be a fit. Open to connecting?”

After:

“Quick observation from talking to a lot of product teams: the bigger the roadmap, the more the ‘why’ behind decisions disappears into old Slack threads. By the time a feature ships, half the team has forgotten the original constraint. Is that a problem you’re actively solving for, or still on the backlog?”

Let's connect on Farcaster: https://farcaster.xyz/bfg 😉