Feature announcement
Feature announcements are not press releases. The reader is not interested in what Visualist shipped. They are interested in what they can do now that they couldn't before. Lead with the outcome, not the build.
- Name the outcome, not the feature. "Proposals in half the time" beats "Introducing: Proposal Builder." One is about the reader; the other is about us.
- Earn the announcement before making it. If the first sentence is "We just launched X," the email is already in trouble. Open with the problem the feature solves. By the time you name the feature, the reader should already want it.
- Don't perform excitement. Remove "we're thrilled," "we're excited," and any variation. The feature speaks for itself.
Name the outcome, not the feature name.
- The problem or friction point the feature addresses (one sentence)
- What the feature does, in the reader's terms (one to two sentences)
- What to do next (one CTA)
Hi [name],
We're thrilled to announce our newest feature, Sticky Notes! Our team has been working hard to bring you this game-changing tool.
Learn more and get started today!
The Visualist Team
Hi Priya,
Client feedback has a habit of arriving everywhere: email, WhatsApp, verbal notes, and then disappearing into a revision thread nobody can find.
Sticky notes in Visualist fix this. Your client leaves notes directly on the file. You see them in context. No threads, no reconciliation.
Try it on your next project: it takes about thirty seconds to set up.
Standalone, or two-part: the announcement, followed by a single follow-up to non-openers only with a different subject line and a different angle. Never send the same email twice.