$ man poke-the-bear

Poke the Bear

A personalization variable that challenges a contact's current approach or status quo. Different from an icebreaker (observational) and a pain point (problem identification). Poke the bear is a pattern interrupt — it makes the reader feel the cost of their status quo without pitching a solution.

by Shawn Tenam

not everyone is ready to buy. but that doesn't mean they're not ready to know you exist. if you can't sell to your ICP right now, at least educate them. the poke the bear variable is how you stay on their radar without being pushy. it's the middle ground between "here's our demo" and "never mind." it creates tension — makes someone feel the cost of inaction — without offering the fix. that tension is what gets the reply. an icebreaker says "I see you." a poke the bear says "I see what you're ignoring."

I run a 3-variable personalization model across every campaign. {icebreaker} goes in email 1 (observational, personal — proves research). {poke_the_bear} goes in email 2 (challenging, thought-provoking — creates urgency). {pain_point} goes in email 3 (problem-focused, specific — names the real issue). the poke the bear is the hardest to write because it has to be specific enough to feel researched but edgy enough to create discomfort. example: "Most $200M CPG brands are still paying 2019 3PL rates on 2026 volume — and calling it a logistics strategy." that's not a pitch. it's an observation that makes someone pause. I generate these with research prompts that map to the target's industry bucket — CPG gets supply chain pokes, SaaS gets tool sprawl pokes, enterprise IT gets deployment pokes. bucket-specific pain mapping is what makes the poke feel personal instead of generic.