Busy readers skim for evidence that you understand their world. Specific nouns beat vague benefits, and a real reason for this reader at this moment beats a generic pitch. The whole email should pass one test: can the reader answer why me, why now, and what would replying accomplish, in seconds? If it reads like something you could send to a thousand people, it will be treated like it. Three moves do most of the work.
- Name a plausible operating situation, not a benefit. "We help fast-growing companies streamline workflows" says nothing. "When implementation teams onboard enterprise customers while CS is still measured on retention, handoffs become the bottleneck" shows you understand the reader's world.
- Give a reason for this reader and this moment. Tie a real trigger, a product launch, a hiring pattern, a market move, to a business implication. Do not mention news just to prove you researched; connect it to something that changed for them.
- Make the ask fit the trust level. Cold and senior contacts get a low-friction ask (permission to send an example, a short question), not a 30-minute meeting request. Match the size of the ask to how much trust you have actually earned.
Personalize only when it changes the logic
Useful personalization uses information a business contact would expect you to use and changes the substance of the message. "I loved your LinkedIn post, very inspiring!" is decoration. "Your post argued that CS should own expansion signals earlier, not just renewal saves; that usually creates a data problem, since usage, support, and CRM signals live in different systems" connects to the reason for the email. Avoid personalization based on private, sensitive, or surveillance-like information. When in doubt, use a role-level or company-level business issue instead.
Keep claims narrow and evidenced
Do not overstate pain you cannot know, and do not turn a single case result into a promise. "Your proposal process is costing you deals" assumes too much; "if proposal consistency is getting harder as enterprise deal volume grows, this may be relevant" stays honest. Instead of "we increase revenue by 40% in 90 days," write "in one similar rollout, the team identified at-risk renewals 45 days earlier; I would not assume the same result without comparing your workflow." Choose one claim, make it concrete, and keep it inside what you can support. A comparable customer problem is more useful than a famous logo.
Use accurate subject lines and openings
Subject lines should create accurate recognition, not manipulation. Prefer "Enterprise onboarding risk" or "Reducing manual renewal reporting" over fake "Re:" or "Fwd:" threads, "Following up" when there was no prior exchange, or "Urgent" when the urgency is really yours, not the reader's. Openings should earn attention fast: skip company history, exaggerated courtesy, and "I know you're busy," since everyone is. Explain only enough product to justify the next action, usually the problem, the outcome, the mechanism in one plain sentence, one relevant proof point, and the next step. A sales email is not a product tour.
Let follow-ups evolve, and do not fake the register
A follow-up is not the first email with "just bumping this" added; it adds one new reason to write, a sharper angle, a proof point, a resource, or a respectful close. Stop when there is nothing new to say. And skip over-translated deference like "Dear Respected Sir," "please kindly," or "we are honored to present." B2B politeness comes from clarity and respect for time. A minor grammar slip does less damage than an unclear intent, an inflated claim, or an email with no real ask.