MCP

Templates vs frameworks

TL;DR

  • Reuse the reasoning (frameworks), not the words (templates). Verbatim templates decay as they saturate a market.
  • A template is safe only inside a narrow segment, with a genuinely differentiated offer, and with someone rewriting it the moment replies dip.
  • Default to frameworks; adopt a template with an expiry mindset, never as your default writing strategy.

Every template was once one good email. The question is what survives reuse: the structure does, the sentences don't.

The schools

Framework school (Will Allred's team at Lavender, n.d. [1]; Corey Haines, 2025-26 [2]) — "Frameworks over templates" is the Lavender line: the team's guide teaches named, reusable frameworks rather than finished emails (n.d.), and Haines' open-source skill likewise ships patterns, not copy (2025-26). The argument: a template's exact words leak into thousands of inboxes and burn out — recipients have seen that email before — while a framework encodes why the email works and regenerates fresh copy per segment. Writing skill compounds; template libraries depreciate.

Fits when: teams (or agents) that can write; competitive, over-emailed markets. · Avoid when: there is no writing capacity at all and volume must ship this week.

Recognizable by: emails from one campaign sharing a shape but not sentences; wording varies beyond the merge fields.

Template school (offer-led volume lineage: Alex Berman's Email10k [3]; ColdIQ, 2026 [4]) — A proven template aimed at a tight segment with a strong offer scales cheaply: the template is only the delivery vehicle, and the offer does the selling. Berman's framing puts the offer ahead of the copy — what is offered matters more than how it is worded (n.d.). ColdIQ publicly maintains a 34-template library in this tradition (2026); it carries no open license, so treat it as reference material, not raw material.

Fits when: narrow segment, genuinely differentiated offer, and a live feedback loop on replies. · Avoid when: broad lists, me-too offers, or nobody watching for decay — the failure is invisible until reply rates have already sunk.

Recognizable by: identical emails across recipients, with only {{FIRST_NAME}}-style merge fields changing.

Default if the user has no preference: frameworks — a template is a special case you qualify into (segment fit, offer strength, expiry watch), not a default you drift into.

The bridge both sides accept

A template is a frozen framework plus a bet that the segment is uniform. The bet holds while the segment stays narrow and the offer stays differentiated (Offer and messaging owns offer strength); it expires when replies dip, which is why measurement (Measurement and iteration) is the template school's real cost of admission. The structures worth reusing are cataloged in Body frameworks.

References

  1. Lavender — Cold email 101 (guide, n.d.)
  2. Corey Haines — marketingskills cold-email skill (open-source skill pack, MIT, 2025-26)
  3. Alex Berman — Cold email: offer, copy, timeline (blog, n.d.)
  4. ColdIQ — GTM skills & template library (repo, no license — reference only, 2026)