12 B2B direct mail examples (and why each one works)

Most 'direct mail examples' posts are one of two things: a photo gallery of clever mailers with no explanation of what they were for, or a list of claimed campaign wins with numbers you can't check. Neither helps you design your own send. What actually transfers from one team to another isn't the artifact — it's the pattern: who the piece was for, what job it did, and the psychological mechanism that made it work.

So a ground rule before the list: everything here is an illustrative pattern, not a case study. When we say a cybersecurity vendor targeting CISOs might send a printed threat briefing, that's a play you can adapt — not a claim about a real campaign or its results. Each example names the persona, the moment, and the mechanism, so you can judge whether it fits your pipeline before you print anything.

Opening doors: cold outreach examples

1. The exec-to-exec letter

Imagine a founder selling data infrastructure who wants a meeting with the CEO of a 500-person logistics company. The play: a one-page letter, founder to CEO, written like correspondence rather than copy — here's what I've noticed about your industry, here's why I'm writing to you specifically, here's the fifteen minutes I'm asking for. Why it works: status matching plus costly signaling. A courier envelope from one operator to another reads as peer correspondence, not campaign output, and the visible cost of sending it says 'I chose you' before a word is read. There's a letter template worth stealing for exactly this format.

2. The threat briefing for CISOs

A cybersecurity vendor might send a printed two-page briefing on an attack pattern hitting the recipient's specific industry — with the product mentioned only in the final paragraph. Why it works: CISOs professionally distrust unsolicited digital contact; a security leader who clicks strangers' links is bad at their job. A physical document sidesteps that reflex entirely, and leading with genuinely useful information makes the sender's competence the pitch. The mechanism is the information gift: utility first, credibility as the residue.

3. The CFO math letter

A spend-management vendor pursuing CFOs might send a single page of arithmetic: the estimated cost of the status quo for a company of the recipient's size, with every assumption stated and an invitation to correct them. Why it works: CFOs are professionally allergic to adjectives and professionally drawn to models. Showing your math is a credibility play — an argument that invites checking signals confidence — and 'correct my assumptions' is a lower-friction ask than 'take a demo.' It gives a numbers person a numbers-shaped reason to reply.

4. The committee send

An enterprise vendor pursuing one large account might send five envelopes on the same day — one per stakeholder, each containing a one-pager written for that person's role: risk posture for the CIO, migration path for the VP of engineering, pricing structure for procurement. Why it works: it manufactures an internal conversation. When three colleagues discover they each received a different, role-relevant piece from the same sender, the vendor becomes a topic — which is the whole game in buying-committee campaigns, where deals die from silent stakeholders, not vocal objectors.

Striking while it's warm: timing examples

5. The pre-conference calendar letter

Two weeks before a major industry conference, a martech vendor might mail its top forty prospect accounts a letter proposing a specific meeting at the show: a named time, a named place, a one-line agenda. Why it works: scarcity and specificity. Executive calendars for a conference fill before anyone boards a plane, so the early, concrete ask wins by default — and a specific proposal ('Tuesday, 2pm, the lobby bar') is psychologically easier to accept than 'let's connect at the show,' because accepting requires no work.

6. The 48-hour follow-up

After the event, every badge scan receives the same templated email from every vendor within a week — a wall of identical follow-up. A team running the event follow-up play might instead land a printed recap of the booth conversation, with a relevant case study, on the prospect's desk within two days of the show closing. Why it works: recency plus channel contrast. The memory of the conversation is still warm, and the envelope arrives through the one channel none of the other two hundred scanners are using.

7. The new-leader welcome

When a target account hires a new VP of sales, an outbound team might send a letter in her first month: a genuine congratulations, one sharp observation about what leaders inheriting her situation usually change first, and an offer to share what comparable teams are doing. Why it works: trigger timing. New leaders arrive with a mandate to change things and no loyalty to incumbent vendors — and in week three, a considered physical letter gets read while email number four thousand does not. The mechanism is being present at the exact moment the buying window opens.

8. The champion-relocation letter

Your product's happiest power user changes jobs. The champion job change play: a note to their new office in the first weeks — congratulations, no ask, one line acknowledging what they built at the last company. Why it works: reciprocity banked early. Arriving before you need anything makes the gesture read as relationship rather than pipeline management, and when that champion later needs your category — which is often why they were hired — you're the vendor who showed up on day one at their new desk.

Rescues and lifecycle examples

9. The over-the-top envelope

A deal has been 'with legal' for two months and the champion has gone quiet. A stalled-deal play: send the economic buyer a one-page summary of the business case their own team assembled — the problem, the numbers, the internal sponsors — framed as 'your team has done serious work on this; here's where it stands.' Why it works: pattern interrupt plus internal social proof. The executive learns their organization already invested in the evaluation, which reframes inaction as waste. Handle with care: position it as supporting your champion, never as going around them.

10. The what's-changed letter

Six to twelve months after losing a deal, a vendor running closed-lost re-engagement might send a short letter that names the original objection and what has changed since: the missing feature shipped, the pricing model evolved, the team doubled. Why it works: it respects the earlier no. 'You were right then; here's new information' licenses the buyer to reopen the conversation without admitting error — and new information is the only socially acceptable reason to reverse a decision one's colleagues watched them make.

11. The no-show envelope

A prospect books a demo and doesn't show. Instead of the fourth 'looks like we missed each other!' email, the no-show recovery play: a printed one-page version of the agenda they missed — 'here's what we would have covered, in three minutes of reading.' Why it works: it converts an awkward moment into value delivered. The prospect feels mild social debt about the miss; the envelope resolves it without shame, proves the vendor prepared, and makes rebooking the natural way to reciprocate. Loss aversion does the rest — the agenda shows them what they almost had.

12. The renewal-math one-pager

Ninety days before a renewal, a customer team might send the economic buyer — not the day-to-day admin — a one-page summary of the year: usage, outcomes, and what's planned next. Why it works: authority routing. Renewals are frequently decided by an executive who never attends the QBRs, working from a budget spreadsheet and a vague impression. Physically landing the outcomes summary on that specific desk means the decision-maker forms the impression from your page, not from the line item. The mechanism is choosing the reader, which only a named-recipient channel can do.

What the twelve have in common

Strip the personas away and every example runs on the same chassis. Each one targets a named person, not an account or a title bucket. Each sends information dense enough to justify the envelope — a briefing, a model, an agenda, a recap — rather than an object. Each is tied to a moment: a trigger event, a stall, a show, a renewal window. And each assumes the follow-up is part of the play, timed to the delivery scan, while the piece is still on the desk.

To adapt one to your own pipeline: pick the pattern that matches the meetings you're missing — the booking-demos-with-target-accounts motion is the usual starting point — then decide what to send and either upload your own design or have the materials generated. Before you print anything, sanity-check the economics with the cost-per-meeting math: these plays are built for accounts worth real money, and the math should say so before the first envelope ships. And once more for the record — the twelve above are patterns to steal, not campaigns to cite. The results will be yours.