Skip to content
Moosewave
Demo

MarketingNewsletter & editorial

A first anniversary email template

A one-year mark with the honest assessment of the 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 first anniversaryIllustrative preview
A first anniversary email template preview

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

A reviewed browser rendition of the a first anniversary 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.

Reading back over twelve issues, the first four are thin and overconfident. Deleting them would improve the archive and would misrepresent how this went.

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
Yarnfold Yearly
Subject
A year in, and the early issues are bad
Preheader
They are still up. That seemed right.

One year

The first four issues are poor and they are staying up

Reading back over twelve issues, the first four are thin and overconfident. Deleting them would improve the archive and would misrepresent how this went.

What was wrong with them

Too confident, too few sources, and written from things I half remembered rather than things I had checked.

What changed

A reader corrected me in issue five, publicly and correctly. Everything since has been more carefully sourced and less certain.

Why keep them

Because an archive that only contains the good work is a portfolio rather than a record. The correction in issue five is the useful part.

Read the first issueRead the correction
Nothing published here is ever deleted. Corrections attach and everything stays.

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