pitch

Pitch Email Patterns That Respect Busy People

Published · 7 min read

An email is a pitch compressed into the space between someone’s previous task and their next one. They’re reading it fast, with half their attention, and they’re making a binary decision: does this earn a reply, or does it earn the archive?

Most pitch emails fail not because the underlying idea is bad but because the email is written from the sender’s perspective. It explains who the sender is, what they do, and why they think the recipient should care. The recipient, meanwhile, is asking one question: does this person understand my situation well enough that a conversation with them is worth my time?

These patterns are designed around that question.

Who it’s for

Founders, freelancers, and ICs who need a first or second touch without sounding like a mail merge. Also useful for internal pitches sent by email — the same principles apply when your recipient is a busy executive three doors away.

The rule before any pattern: earn the right to write

An email without a specific, true signal is noise. Before you write anything, you need one concrete reason why you are writing to this person, now. Not “I saw you’re in [industry].” A real signal: a post they published, a product they shipped, a job they posted, a metric they shared publicly, a change at their company, a problem a mutual contact mentioned.

If you cannot name a specific, true signal, you are not ready to email. Research first. The signal is not decoration — it is the proof that you are not random.


Pattern 1: Cold outreach (no prior connection)

What it’s trying to do: Create enough credibility in three sentences that a total stranger decides this is worth twelve minutes of their life.

The skeleton:

Subject: [Specific signal] → [their outcome]

Hi [Name] — [One true, specific observation about them or their company].

Teams in [their situation] often hit [pain point in plain, un-dramatic language]. [One sentence on what you do differently, written in terms of what changes for them — not features you have].

Worth a 12-minute call [specific day] or [specific day]? If this isn’t your area, who should I be talking to?

What makes it work:

Example:

Subject: Your SOC2 post → readiness without the sprint chaos

Hi Maya — Saw your note on the SOC2 certification timeline — specifically the pen test scheduling problem.

Engineering teams preparing for Type II often find pen tests queue behind features for 6–8 weeks, which kills the audit timeline. We run a two-week readiness sprint with daily pass/fail checks so you don’t lose the window.

Worth a 12-minute fit call Tuesday 10a or Thursday 3p? If this isn’t yours, who owns compliance prep?


Pattern 2: Warm outreach (mutual contact or prior interaction)

What it’s trying to do: Activate the trust already implied by the connection without leaning on it so hard that it becomes awkward.

The skeleton:

Subject: [Mutual contact] thought we should connect

Hi [Name] — [Mutual contact] mentioned you’re working on [specific thing]. I’ve spent [time] on this problem at [context], so when [mutual contact] suggested we talk, it made sense to reach out.

[One sentence of relevant experience that isn’t a resume line — something you learned, built, or solved].

Happy to share what worked and what didn’t, no agenda. Are you open to a 20-minute call [specific day]?

What makes it work:


Pattern 3: Internal pitch email (to someone in your organization)

What it’s trying to do: Get a busy colleague or executive to give you calendar time or a decision — when they’re operating under the assumption that their time is already fully committed.

The skeleton:

Subject: [Decision/topic] — need 30 minutes before [date]

[Name] — [One-sentence framing of why this is time-sensitive and what the consequence of delay is].

I’ve mapped out [what you’ve done]: [list in 3 bullets max]. The decision I need your read on is [specific binary or choice].

Can we find 30 minutes before [date]? I’ll send a doc the day before so you’re not coming in cold.

What makes it work:


Pattern 4: The second touch (following up on silence)

See the dedicated article on follow-up after silence. The short version: one new piece of information, one narrower ask, one default action.


Common mistakes

Using the same email for every contact. Batch personalization — where you swap out the name and one sentence — is usually detectable. Genuine signal-finding takes five minutes per contact. That’s the price of not sounding like a mail merge.

Three asks in one email. One ask. If you want a call, a referral, and a doc review, send three emails on three separate occasions. The reply rate to a single clear ask is dramatically higher than to a menu of options.

Fake personalization. “Loved your LinkedIn profile” or “I’ve been following your company for a while” without specifics reads as exactly what it is: a template with a name filled in. Use a real artifact — a specific post, a specific product feature, a specific number they shared. If you can’t find one, find a different contact.

The paragraph that explains who you are. Busy people do not read company descriptions. If your third sentence starts with “We are a [category] company that [verb] for [market],” your email is already in the archive. Replace it with the outcome they get.

Not having an escape hatch. “Who should I be talking to?” is one of the most valuable sentences in cold email. It converts a dead end into a referral.

Practice prompt

Find the last outbound email you sent that didn’t get a reply. Run it through these questions: Does the subject line contain their signal or your pitch? Is the pain described in their language or your marketing language? Is there exactly one ask? Is there a specific time option rather than “when are you free”? Rewrite it using the pattern that fits. Do not send it yet — sit with it for an hour, then read it again as if you’re the recipient.