MCP

Signatures and P.S.

TL;DR

  • Cold-email signature: name, role, company, at most one link. No logos, banners, or badge rows.
  • At most one P.S., one sentence long — a softer alternative ask, or the personalization detail that didn't fit the body.
  • Evidence status: practitioner consensus; no strong data corpus either way.

Be clear about the evidence here: unlike subject lines or body length, no large published corpus isolates the effect of signatures or P.S. lines in cold email. What follows is consistent practitioner guidance — the cold-email guide from Will Allred's team at Lavender [1] and Corey Haines' open-source skill (2025-26) [2] among the sources — not measured deltas.

The minimal signature

A first cold email should end quietly: name, role, company, and at most one link. Image-heavy signatures — logos, certification badges, banner CTAs — add weight a spam filter counts against an unknown sender, and visual noise that competes with your single CTA; the deliverability mechanics, along with whatever your jurisdiction requires in the footer, live in Deliverability and compliance essentials. The signature's job is to prove a real, findable person sent the email — not to market. One link gives a curious reader somewhere to go; more than that gives a filter and a skimmer reasons to bail.

The P.S.

The P.S. is a classic second slot precisely because it sits apart from the body: visibly optional, read on the way out. Two uses earn it: a softer alternative ask than the body's CTA (a referral question instead of a meeting), or the one personalization detail that didn't fit the body's focus. Keep it to a single sentence, and never stack a second P.S. — two postscripts read as a gimmick. If the P.S. is carrying the email's main argument, the body is broken; fix it with a proper structure from Body frameworks rather than patching from below.

References

  1. Lavender — Cold email 101 (guide, n.d.)
  2. Corey Haines — marketingskills cold-email skill (open-source skill pack, MIT, 2025-26)