Skip to content
Moosewave
Demo

MarketingNewsletter & editorial

A failure explained email template

An honest account of a project that did not work.

See the full preview Use it with MCP

Illustrative example. Replace the fictional sender, dates, amounts, locations, and account details before use.

Responsive design preview

See the message before you make it yours.

Compare the desktop and mobile compositions, or unfold the full design. The complete starting copy remains readable below.

A failure explainedIllustrative preview
A failure explained email template preview

Auto follows your screen width. Scroll inside the frame to inspect the complete email.

A reviewed browser rendition of the a failure explained structure. It is not a send receipt or an inbox-placement claim.

Want to change the copy and style?

Try one of the editable browser templates.

This page is a read-only reference. The five hands-on studios let you edit a local preview, compare desktop and mobile, and review every change before continuing.

See editable templates

Message anatomy

A useful starting point, with the important parts named.

Failures are usually described briefly and vaguely. This one is described at length because the reasons are more useful than another account of something that worked.

What you can change

  • Brand name
  • Subject line
  • Preheader
  • Eyebrow
  • Headline
  • Supporting copy
  • Primary action label
  • Primary action URL

What to keep clear

  1. Campaign context
  2. Headline and editorial premise
  3. Three skimmable sections
  4. Primary and secondary action
  5. Preference and unsubscribe footer

Complete starting copy

Read it as text, not only as a picture.

Sample details are fictional. Replace them with reviewed customer and event data before use.
From
Hollowfield Notebook
Subject
The project failed, and here is why in detail
Preheader
Eighteen months and about £4,000.

What went wrong

Eighteen months, four thousand pounds, and it did not work

Failures are usually described briefly and vaguely. This one is described at length because the reasons are more useful than another account of something that worked.

What I was trying

To map every hedgerow in the parish by species and estimated age, and to link that to the enclosure record.

Why it failed

The species counting is far less reliable on this soil than the literature suggests. Two hedges of known age gave counts four centuries apart.

What was salvaged

The enclosure mapping, which is sound and is published. The dating claim is withdrawn entirely and the data is marked accordingly.

Read the full accountSee the salvaged data
I write monthly, including about the things that did not work. You can change that below.

Moosewave MCP

Give an agent the structure, the job, and a stopping point.

A compatible MCP app can inspect this reference and create a separate workspace draft when it has permission. The brief cannot send.

The brief asks for a new draft and stops before send.

Read the complete brief

Connected work

Take the design beyond the canvas.

AutomationsPlace this message inside a journey with a clear trigger and exit.AudiencesChoose who should receive it, and who should be left out.AnalyticsMeasure the response that matters after the send.MCP for agentsAdapt the structure through a compatible assistant with limited workspace access.

Keep exploring

Browse all 1405