The case study air drop playbook
Last updated July 20, 2026
The case study air drop is run by ABM or demand-gen marketers paired with SDRs, and the trigger is a fresh, customer-approved case study with a specific, real outcome in it. You print your customer's own story - their logo, their words, their results - and FedEx it to a tight list of accounts that look exactly like that customer: same industry, similar size, same problem. The proof does the selling; the envelope makes sure it actually gets read.
One rule is absolute: the asset is your customer's real, approved story. No invented outcomes, no composite 'customers,' no rounding results upward. The play works precisely because a named peer with a verifiable result is the one thing a skeptical buyer can't dismiss as marketing.
Key takeaways
- Run it only when you have a customer-approved case study with a concrete, real outcome - the play is the proof.
- Build the list as lookalikes of the featured customer: same industry, similar headcount, same buying-committee titles.
- Print the story as a one-pager, FedEx it to named contacts, and call the day the dashboard confirms delivery.
- Follow the physical piece with a digital copy so your contact can forward it to the rest of the committee.
- Never mail a story the customer hasn't signed off on for external use.
Who runs it, and when
Marketing owns the asset and the lookalike list; SDRs or AEs own the calls and follow-up. The trigger isn't a date - it's an asset. The moment a strong customer story clears approval (customer sign-off for external use, a named champion, a before-and-after a stranger can follow in thirty seconds), it's air-drop material. Weak, logo-only 'case studies' with no concrete outcome don't qualify; wait for a better story rather than mailing a vague one.
List construction is the other half. Start from the featured customer and work outward: their industry, their size band, their stack or business model, the same titles that drove their purchase. Thirty to seventy-five accounts is the sweet spot - tight enough that every recipient genuinely resembles the customer in the story, large enough to produce meetings. A logistics-software story mailed to logistics operators lands; the same story mailed to a generic 'mid-market' list is just expensive noise.
The cadence
D0 is the day the envelope lands, confirmed per-piece in the tracking dashboard. Because envelopes arrive account by account, treat delivery days as rolling - each account's clock starts when its envelope lands.
| Day | Channel | Move |
|---|---|---|
| D-10 | List | Build the lookalike list from the featured customer's profile: industry, size band, buying-committee titles. Upload for address verification before anything prints. |
| D-7 | Asset | Confirm customer sign-off covers print distribution; adapt the case study into a one-pager with their logo and headline result front and center. |
| D-4 | Optional warm-up to the primary contact: one observation about the problem the story solves. No attachment, no ask. | |
| D0 | — | The case study lands in a FedEx envelope addressed to the named contact. Dashboard confirms delivery. |
| D0 or D+1 | Phone | Delivery call: name the customer in the first sentence - 'I sent you [Customer]'s story because you run the same operation they do.' |
| D+2 | Reply-style note quoting the headline result from the story and asking one question about their version of the problem. | |
| D+4 | Phone | Second attempt, different time of day. Voicemail references the printed story, not a generic pitch. |
| D+6 | Send the digital version of the same case study so your contact can forward it to the rest of the buying committee. | |
| D+9 | Direct message to non-responders: two sentences, the customer's name, and a single meeting ask. | |
| D+14 | Close: one last note offering a call with reference-level detail; unresponsive accounts roll into next quarter's list. |
What to send
The core asset is the customer's case study printed as a one-pager - use the case study one-pager structure template (/templates/case-study-one-pager) to lay it out: their logo and headline result in the top third, the before-and-after in the middle, a single next step at the bottom. Pair it with a short cover letter adapted from the cold outreach letter template (/templates/cold-outreach-letter): three or four sentences on why you sent this particular story to this particular person, signed by a human.
What not to send: your product brochure stapled to the story (it dilutes the proof), and any 'case study' the customer hasn't approved for external use. If the story is real but thin, mail the letter alone and save the air drop for a stronger asset.
The delivery call
'Hi [First name], [Your name] from [Company]. A FedEx envelope from me landed on your desk today - it's [Customer]'s story, the [industry] company that [one-line description of the outcome]. I sent it to you specifically because [Prospect company] runs the same model they did before the change.' Then stop pitching and ask: 'Does the before picture in that story look familiar?'
If the answer is yes, offer the natural next step: a short call walking through how [Customer] did it, with the detail behind the one-pager. If the contact hasn't opened the envelope yet, don't summarize the whole story - give them the headline and let the printed piece do its job.
KPIs and failure modes
The signal to watch is whether replies reference the story. 'How did [Customer] handle X?' means the play is working; generic 'send me some info' replies mean the lookalike match is off. Track delivery-day call connects, story-referencing replies, forwards of the digital version, and meetings with accounts that genuinely match the customer profile.
- Weak lookalike match: if recipients don't recognize themselves in the story, the proof has no pull - tighten the list before blaming the asset.
- A vague asset: a case study without a concrete outcome reads as marketing and gets recycled; wait for a story with a real result.
- Skipping customer sign-off: mailing a customer's name and logo without explicit approval can damage the relationship that produced the story in the first place.
Frequently asked questions
Whose case study gets mailed in this play?
Your customer's - the play mails your own customer's approved success story to accounts that resemble them. It is never a B2BMail case study, and it should never contain invented or embellished outcomes. The entire mechanism is that a real, named peer with a real result is credible in a way marketing copy can't be, so anything fabricated defeats the play.
How many accounts should be on an air drop list?
Thirty to seventy-five is the working range. Below that, one busy quarter at the target accounts can starve the play of at-bats; above it, the lookalike criteria have usually been stretched until the story no longer matches the reader. B2BMail verifies a deliverable business address for every contact before printing, so a tight list also means no budget leaks into envelopes that can't land.
What if my best case study can't be named publicly?
Anonymized stories ('a mid-market logistics operator') can work in cold email, but they're weak air-drop material - the physical, printed format promises substance, and an unnamed logo undercuts it. Ask the customer whether they'd approve print-only use with their name; if not, run a different play, like the founder letter play, until a nameable story exists.
Land on every prospect's desk
B2BMail puts your message in a FedEx envelope on the desk of every decision-maker at your target accounts — with per-piece tracking and every address verified before it ships.