HUNGR Framework Guide

What is HUNGR?

HUNGR is a 5-step methodology for building high-intent B2B outbound campaigns without relying on static ICP lists or spray-and-pray tactics.

Instead of asking "who might want this?" ask "who has the problem right now?"

H - Help the right business

The core shift: don't build a list of companies that fit a profile. Build a list of companies actively experiencing the pain your product solves.

This is intent signal-based prospecting. An intent signal is any observable behavior that indicates a company would have a need to buy your product right now.

Three signal categories

Hiring signals - A company hiring for a role that implies your solution. A company posting for a UGC Content Creator wants content at volume but hasn't discovered they can automate it for a low monthly price.

Behavioral signals - A company posting about the problem on social media, asking for recommendations in communities, or churning a competitor tool.

Structural signals - Fundraising, product launches, geographic expansion - triggers that reliably create new budget and new needs.

Why this beats ICP profiling

"DTC brands with 10-50 employees" might be 50,000 companies. "DTC brands actively hiring for a UGC content role right now" is 500 companies - every single one is in the exact moment of pain.

U - Understand and become that business

Before reaching out to anyone, research exactly how the people you're targeting describe their own problem. Not how you'd describe it - how they describe it.

Voice of Customer sources

• App store reviews of your competitors
• Reddit threads in relevant communities (r/ecommerce, r/dropshipping, r/Entrepreneur)
• Twitter/X complaints, questions, and frustrations
• Trustpilot and G2 reviews for tools in your space

What to extract

• The exact phrases they use ("creative fatigue" not "ad creative performance decline")
• The specific fears they have ("looks clearly AI", "burned through credits")
• The dream state they describe ("brief it once, get a month of content")

When you reach out using their language, it reads as if you've been listening in. Because you have.

N - Navigate signal sources

Each intent signal type has different sources. Map which ones will give you the volume and quality you need before writing a line of pipeline code.

Signal source reference

G - Gather and qualify at scale

Build collection scripts that pull from each source automatically. Deduplicate. Score. Split into two buckets.

Bucket A - has company domain: Run through Apollo to filter by headcount (5-50 employees) and pull decision-maker contacts (Founder, CEO, CMO, Head of Marketing).

Bucket B - platform handle only: DM directly on the platform. LinkedIn DM, Twitter DM, or wherever the signal came from.

Pipeline output

• LinkedIn Jobs (20 keywords x 4 pages): ~490 leads
• YouTube (300+ channel audit, content drought filter): ~50 leads
• Twitter/X (10 queries x 2 pages): ~290 leads
• Total per run: ~830 leads in 15-20 minutes
• API cost: ~$0.30

R - Reach out with value

Intent signals only help if your outreach reflects them. Three rules:

Rule 1 - Lead with the signal, not the pitch. Reference what you observed before you say what you sell. "Saw you're hiring for a UGC Content Creator" beats "I help companies with content."

Rule 2 - Ask easy yes/no questions. Protects domain reputation. More replies means better inbox placement. "Can I send this over?" outperforms "Would you like to hop on a call?"

Rule 3 - No links or attachments in the first email. Kills deliverability. Save the case study for after the first reply.

Signal-specific openers

• Hiring signal: "You're hiring for [exact role title]. What if you didn't need to?"
• Content drought: "Your channel hasn't posted in [N] days. What's blocking the pipeline?"
• Competitor churn: "Saw your [Creatify/Arcads] review. What specifically didn't work?"
• Twitter pain: "[Quote their exact words.] We built something for exactly that."
• Ad fatigue: "[Brand] has been running the same creative for [N] days. Your audience has probably memorized it."

Built with Claude Code in one live session. Companion scripts available in the Pipeline Setup Guide.