Write a cold email to enterprise buyers
Produces a cold email calibrated to enterprise physics: initiative-aware opening, outcomes framed as risk reduction in the buyer's currency, peer-grade proof, and an org-chart-respecting CTA that invites routing to the right owner. It also tells you when your proof isn't enterprise-credible yet, instead of letting you overclaim.
You are an enterprise outbound strategist. You know that emailing a director at a 5,000-person company with startup-flavored outbound ('quick question!', 'love what you're building!') is a category error. Enterprise buyers operate in a different physics: they buy to reduce risk more often than to chase upside, they think in initiatives and fiscal years rather than hacks and quick wins, they assume any vendor email will waste their time, and they know a purchase means procurement, security review, and internal selling they'll have to do personally.
Write ONE cold email to an enterprise buyer:
- 70 to 110 words. Enterprise tolerates slightly more length when every sentence is load-bearing.
- Open with evidence of understanding their world: the initiative, regulatory pressure, or structural challenge their function is navigating — sourced from what I tell you, not invented.
- Frame the outcome in their currency: risk reduced, initiative de-risked, cost per unit, audit-readiness — not 'growth hacks' or '10x'.
- Proof must be peer-grade: a company of comparable scale or regulatory exposure, or a credible category metric. A 20-person startup's logo is not enterprise proof.
- CTA asks for the correct next step at enterprise altitude: a brief exchange of perspective or a pointer to the right owner — 'If this sits with someone on your team, happy to be pointed there' respects the org chart and often produces a warm internal forward.
- Banned: exclamation marks, 'quick', 'hack', 'disrupt', emoji, false urgency, and pretending procurement doesn't exist.
Also give me a lowercase subject line that could plausibly be an internal email about their initiative.
Before you write anything, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time:
1. Who is the buyer (title, function, company size, industry), and what do you sell?
2. What initiative, pressure, or mandate is their function under right now — and how do you know?
3. What's your most enterprise-credible proof point?
4. Realistically, is this person the buyer, the influencer, or the router to the real owner?
Once you have my answers, write the email. If my proof is all startup-scale, tell me honestly and frame the strongest available angle instead of overclaiming.How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Research the initiative before answering question 2 — earnings calls, annual reports, and executive LinkedIn activity reveal what the function is being measured on.
- 3
Answer question 4 honestly; emails to routers should optimize for the forward, not the meeting.
- 4
Expect longer cycles: pair this email with a patient multi-touch cadence rather than judging it on week-one replies.
Best practices
Public companies publish their pressures — one hour with the annual report's risk section outperforms any enrichment tool for initiative intel.
The routing CTA is a feature, not a concession; a forwarded email arrives with implicit internal endorsement no cold touch can match.
Mind compliance overlays in regulated industries — banking, healthcare, and government buyers may have strict rules about vendor contact.
Multithread from the start: send peer-level variants to two or three stakeholders in the same account rather than betting one contact.
Example: what this looks like in practice
An AE at a data governance platform targets a director of data at a publicly traded insurer. The annual report flags a modernization program and regulatory findings around data lineage. Her email opens 'Most carriers mid-way through core modernization hit the same wall: lineage documentation that satisfied the old auditors doesn't satisfy the new regulators', cites a top-ten insurer that cut lineage audit prep from six weeks to four days, and closes 'If this sits with your governance lead, happy to be pointed there.' Subject: 'lineage audit prep'. The director forwards it internally; the governance lead books the call — a warmer entry than any direct reply.
Best fit
This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.
Apply for a Pilot Spot → →Frequently asked questions
Enterprise buyers weigh risk over upside, think in initiatives and fiscal years, and know a purchase drags in procurement and security review. Startup-style urgency and 'quick win' framing actively repels them. Effective enterprise emails demonstrate awareness of the buyer's initiative, offer peer-scale proof, and request a next step that respects how large organizations route decisions.
More cold email writing prompts
Get your cold email critiqued and scored like a skeptical prospect
Runs your cold email through a three-pass review: a brutal line-by-line read from a busy prospect's perspective, a five-dimension strategic score, and a rewrite that fixes the weakest dimensions. You learn why the email underperforms, not just that it does — the pattern transfers to every email you write after.
Write a complete cold email from scratch
Produces a complete, send-ready cold email of 60-100 words with the four-part spine that books meetings: reason, problem, proven outcome, soft ask. The five-question interview forces you to articulate the 'why now' most campaigns skip, and the prompt refuses to write until that angle is real.
Audit and rank your subject lines before you hit send
Puts every subject line candidate through a brutal pre-send audit: a 1-10 plausibility score, its biggest weakness named, spam-pattern flags, and a fixed rewrite. You get a ranked list with a clear verdict — two to test, the rest to kill — instead of sending on gut feel.