Home
Resources
Agent Skills
Writing voices
Poppy — the warm, practical marketing letter

Poppy — the warm, practical marketing letter

A blog-writing style skill that makes an AI agent write in the warm, practical marketing-letter voice of Ann Handley: it opens on a small real moment or a reader's question, talks to the reader as a friend who knows the craft, keeps the asides and the humour on, then turns into a handful of bold, arguable points with plain examples and Not/Instead pairs, closing on a conviction or a question and an optional P.S. It works on any business topic. The skill gives a fingerprint table, a seven-step build, sentence rules, truth rules that forbid invented anecdotes, reader questions and data, a worked opening and a revision pass. It reproduces the moves, never the writer's sentences, coinages or sign-offs.

In the voice of Ann Handley

Updated 5 October 2026 · By Sadeq

When to use it

Write a blog post in Poppy's voice: the warm, practical marketing letter. Open on a small real moment or a reader's question, talk to the reader as a friend who happens to know the craft, keep asides in parentheses and the humour on, then turn it into a handful of bold, arguable points with plain examples — "not this, this instead" — and close on a conviction or a question, often with a P.S. Use when someone asks for a post "in Poppy's style", a newsletter issue, a friendly how-to for marketers or small-business owners, an answer to a customer question, or a post that should feel written by a person rather than a brand. Works for any business topic. Do not use it for formal reports, legal or medical guidance, or when nobody can supply a real moment or question to start from — the voice depends on them.

Complete file

SKILL.md

---
name: poppy
description: >
  Write a blog post in Poppy's voice: the warm, practical marketing letter.
  Open on a small real moment or a reader's question, talk to the reader
  as a friend who happens to know the craft, keep asides in parentheses
  and the humour on, then turn it into a handful of bold, arguable points
  with plain examples — "not this, this instead" — and close on a
  conviction or a question, often with a P.S. Use when someone asks for a
  post "in Poppy's style", a newsletter issue, a friendly how-to for
  marketers or small-business owners, an answer to a customer question, or
  a post that should feel written by a person rather than a brand. Works
  for any business topic. Do not use it for formal reports, legal or
  medical guidance, or when nobody can supply a real moment or question to
  start from — the voice depends on them.
license: MIT
metadata:
  author: daena-digital
  version: "1.0"
  collection: blog-style-voices
---

# Poppy — the warm, practical marketing letter

Poppy writes like someone who has done the work, likes the reader, and
cannot resist a joke on the way to a useful point. The post feels like a
letter from a friend: it starts with something that happened, wanders
for a paragraph (on purpose), then gets very practical very fast.

Studied from Ann Handley's newsletter and blog at annhandley.com. This
skill reproduces her *moves*, never her sentences, coinages, section
names or sign-offs.

## When to pick Poppy over another voice

- The reader is a practitioner — a marketer, a founder, a shop owner —
  who wants to do one thing better by Friday.
- There is a real question behind the post: a customer asked it, a
  colleague got it wrong, the writer changed their mind about it.
- The brand wants to sound like people, not a department.

Pick Ezra (the plain essay) to argue an idea without the warmth and the
jokes. Pick Wren for one short provocation. Pick Hazel when the point
rests on a story from history rather than from this week.

## The fingerprint

| Trait | Poppy does | Poppy never does |
|---|---|---|
| Length | 1,100–1,800 words | Under 800 (it reads as a tease) or past 2,200 |
| Opening | A small, real moment from the writer's week, or a reader's question quoted briefly — then the topic arrives within three paragraphs | A definition, a statistic, "In today's fast-paced world" |
| Person | "I" for the writer, "you" for the reader, "we" for "people who do this job" | The corporate "we" that means the company |
| Structure | Intro, then 3–8 points under **bold headings that state a claim**, sections split by a centred `***` | Neutral topic labels ("Overview", "Benefits") |
| Points | Each one: claim, one plain reason, one concrete example, often a **Not:** / **Instead:** pair | Theory without an example, or an example without a rule |
| Paragraphs | Varied: several one-line paragraphs for punch, a few of 3–5 sentences for substance | Wall-of-text, or every paragraph one line |
| Asides | Frequent parentheticals and em dashes that add a joke, a caveat or a confession | So many the point gets lost — one aside per paragraph at most |
| Humour | Self-deprecating, specific, affectionate. A playful made-up word or a short ALL-CAPS outburst once per post | Sarcasm at the reader, mean jokes about competitors |
| Opinion | Takes sides plainly, admits bias, grants the other side first | Fence-sitting, or certainty with no reasons |
| Data | Used when it exists, cited by name, then interpreted with a sentence of what it means for the reader | Invented figures, or numbers left to speak for themselves |
| Ending | A short return to the opening moment, then a one-line conviction the writer would defend or a question to the reader | A pitch, a recap of every point, "In conclusion" |
| P.S. | Optional. One extra thought, a follow-up question answered, or a small human note | A second call to action disguised as a P.S. |

## How to build the post

1. **Get the real moment.** Ask the user for one: a customer's question,
   a conversation with a colleague, something they noticed this week, a
   mistake they made. If they have none, use a question their customers
   genuinely ask and say so plainly ("A client asked me last month…" only
   if it happened). Do not invent an anecdote and present it as true.

2. **Open small and specific.** Two to four short paragraphs on the
   moment: where, who, what was said. One self-deprecating or funny
   detail. Then a one-line turn into the topic — often a question the
   moment raised.

3. **Say what you think, early.** By the end of the intro the reader
   knows the writer's position. Grant the opposing view a fair sentence
   first ("I get it. X is tempting because…"), then disagree.

4. **Write 3–8 points, each under a bold heading that is a claim.**
   *"Shorter isn't kinder. Clearer is."* not *"Length."* Under each:
   - why, in one or two sentences;
   - one concrete example from the reader's world — a subject line, a
     product page, a sentence before and after;
   - where it helps, a **Not:** line and an **Instead:** line.

5. **Keep the voice on between the points.** A parenthetical aside, an
   honest admission ("I've done this. Recently."), a short joke. Split
   major shifts with a centred `***`.

6. **Come back to the opening.** One or two paragraphs that return to the
   moment from step 2 and say what changed, or what the writer would tell
   that person now.

7. **Close on a conviction or a question.** One line of belief, or a
   question that asks the reader to do one specific thing this week.
   Optionally add a **P.S.** with one extra, useful thought.

## Sentence-level rules

- **Talk, don't announce.** Write the sentence the writer would say out
  loud to a smart friend across a table. Contractions everywhere.
- **Vary the beat.** After two long sentences, a short one. Then a
  fragment. Like that.
- **One aside per paragraph, at most.** Parentheses for a joke or a
  confession; em dashes for a sharp turn — like this one.
- **Concrete over clever.** Every joke should sit next to a specific
  thing: a real subject line, a named tool, a time of day.
- **Admit the bias.** If the writer sells the thing being recommended,
  say so in a sentence. The voice's trust comes from saying it first.
- **Praise the reader, criticise the habit.** "You're busy and the
  template is right there" — then why the template is costing them.
- **Plain words for the craft.** Explain any marketing term the first
  time it appears, in a parenthesis if short.

## What Poppy never licenses

The warmth makes invention tempting. Don't.

- **No invented anecdotes, reader questions or colleagues.** The opening
  moment and any quoted question must come from the user or be framed
  openly as hypothetical ("Say a customer asks you…").
- **No invented data.** A statistic needs a named, checkable source. If
  there is none, make the point without a number.
- **No borrowed sentences, coinages, section names or sign-offs** from
  the writer this voice was studied from. Make up your own playful word
  if the post wants one.
- **No fake intimacy.** Don't claim feelings, family details or habits
  the user hasn't given you.

## A short illustration

The opening and first point of a Poppy post for a bakery that sells
wholesale to cafés. The bakery and the phone call are invented to show
the shape; in a real post the moment must be the user's own:

> **Your price list is not a sales email**
>
> On Tuesday a café owner rang me — not emailed, *rang*, which at this
> point is basically a telegram — to ask whether we still did the rye.
>
> We do. We've done it every day for three years. It's on the price list
> we send every café, every month.
>
> So I opened that price list and read it the way she would: on a phone,
> between two customers, with flour on her thumb. (Okay, the flour is
> mine. Still.) Forty-one items. No photos. The rye is line 27.
>
> Which raised a question I don't love: how many of our "monthly
> updates" have quietly been nobody's update at all?
>
> I get why we send it. It's thorough. Nobody can say we didn't tell them.
> But "we told them" and "they know" are different things — and only one
> of them sells bread.
>
> \*\*\*
>
> **One thing per email beats everything per email.**
>
> A café owner gives your email about the length of a coffee pour. Use it
> for one thing they can say yes to.
>
> **Not:** "October price list attached — 41 items, see inside."
> **Instead:** "The rye's back on weekends — want it Saturday?"

Note what it does: a real moment with one funny detail, a parenthetical
confession, the position stated after granting the other side, a `***`
break, a bold heading that is a claim, and a Not/Instead pair the reader
can copy today.

## Revision pass

1. Is the opening moment real and supplied by the user, or openly
   hypothetical? If neither, stop and ask for one.
2. Could the reader name the writer's position after the intro?
3. Is every bold heading a claim someone could disagree with?
4. Does every point carry a concrete example — ideally a before and an
   after?
5. Count the asides. More than one in a paragraph? Cut one.
6. Does the ending return to the opening, then stop on a conviction or a
   question? Any pitch after it? Remove it (a P.S. may stay if it is
   useful, not promotional).
7. Is every number sourced and every quote real?
8. Word count between 1,100 and 1,800?

Knowledge base

What we read to learn Ann Handley’s voice

Don't Outsource This Part of WritingPersonal opener, abundant asides, bold takeaways, a hopeful rallying close
Make Posteingänge Sexy Again: 9 Ingredients for an Email Readers Want to OpenReader question opener, playful word-love, bold numbered principles
AI Slop, Accusations, And A Better WayHandling a contested opinion: reframe, then two reflective questions
Why Care About The Stupid Em Dash Anyway?Validate the worry, then a practical test, closing on a conviction
Is the Age of Reading Actually Over?Scene from her week, data cited and interpreted, circles back to the opening
How To Secure More Speaking GigsMailbag advice in numbered points with Not/Instead contrasts
New Data Just Dropped! Latest Blogging ResearchHeaders that state a claim; data with jokes and caveats; a useful P.S.