How to Structure a Newsletter Issue: A Five Part Shape

To structure a newsletter issue, fix a five part shape once and fill it every time: a specific subject line, a short opening, one idea, one call to action and a sign-off with a question. Then each issue becomes "fill the container" instead of "invent the format."

Most of the work of a newsletter is not writing well. It is making the writing routine enough that you will do it forty times without negotiating with yourself. A fixed structure is what makes that possible. It removes decisions, speeds the edit and gives readers a rhythm they come to recognise.

How to structure a newsletter issue in five parts

The playbook gives a shape that works for almost every founder newsletter. It has five parts, and each does a specific job.

Part	Its job	The rule
Subject line	Tell the right person what is inside	Name the specific thing, not a teaser
Opening	Say why this matters to the reader today	Two or three sentences
One idea	Deliver something the reader can act on	One argument, one lesson or one teardown
One call to action	Name the single next step	Stated plainly, placed after the value
Sign-off with a question	Invite a reply	Direct and easy to answer

Fix this once, write it into a template if you like, and resist the urge to redesign it every month. The point of the structure is that it carries you through weeks when you have little energy.

Part one: the subject line

The subject line names the specific thing inside. It has one job, and clever wording usually gets in its way. This part has its own sibling post, how to write a newsletter subject line, so here it is enough to say that the line should tell the right reader what they will get and should not behave like a promotion.

Part two: the opening

The opening is two or three sentences that tell the reader why the issue matters to them today. It is not a greeting, a weather report or a confession about how late the issue is. Because a reader decides quickly whether to continue, the opening has to connect the idea to their situation fast.

A good test is to read only the opening and ask whether the named reader of your newsletter would see themselves in it. If it could be the opening of any email to anyone, it is not doing its job. The playbook's own checklist puts the question this way: does the opening tell the reader why this matters to them in the first few sentences?

Part three: one idea, delivered properly

This is the centre of the issue, and the rule is in the name. A reader can act on one idea, and five feel like none. That one idea might be an argument, a lesson from the week or a teardown of a single example, depending on the backbone you chose. The choice is covered in how to choose a newsletter format.

Delivering it properly means giving the reader enough to use it. If the idea is a lesson, say what happened and what you would do again. If it is a teardown, show what works in the example and why. Cut anything that does not serve the one idea. Founders often feel pressure to add a second and third point to justify the send, and the issue weakens each time they do.

Part four: one call to action

The call to action is a single next step, stated plainly after the value has been delivered. It does not have to be a sale. It could be an invitation to reply, to read a case study or to book a call if the problem is real right now. The craft of choosing and phrasing it is in how to write a newsletter call to action.

For structure, the thing to remember is placement. It follows the value. An issue that opens with an ask spends permission before it has earned any.

Part five: the sign-off with a question

The playbook singles this out as the most commercially important sentence in the issue and the one most people leave out. It is a direct, easy question that invites a reply. It matters because replies are the point of the whole channel: every issue lands where the reader can answer privately, and a small number will if you ask.

The question should be easy. A question that needs an essay in response will get silence. A question the reader can answer in a sentence, about their own situation and tied to the idea they just read, gets answers. How those replies become a measurable outcome is in how to measure a newsletter by replies.

Keep the design plain

Structure is also about how the issue looks. A newsletter that looks like a letter tends to be read like one. Heavy templates and image led layouts signal marketing, render badly on phones and are more likely to be filtered. The advice in the playbook is simple: a clean single column, readable type and an image only when it genuinely helps.

This also supports the five part shape. A plain layout leaves nothing to compete with the idea, and the question at the end stands out because nothing decorative surrounds it.

Before every send

The playbook includes a ten minute checklist for each issue. It makes a useful final pass on the structure.

• The issue delivers one idea the reader can use or think differently about.
• The subject line names the specific thing inside, with no manufactured urgency.
• The opening explains why it matters in the first few sentences.
• The issue keeps the promise, and nothing in it exists only to serve you.
• There is exactly one call to action, placed after the value.
• The issue ends with a direct, easy question.
• Every link works, and I have sent myself a test and read it on a phone.

The test on a phone is not a detail. Many readers will see the issue there first, and a layout that looks fine on a desktop can fall apart on a small screen.

Where to find the material

Structure solves the shape problem but not the content one. The founders who sustain a newsletter are rarely the ones with the most ideas; they are the ones who capture them. Every question a customer asks twice is an issue. Every objection you answered on a sales call is an issue. Keep a running list, add to it the moment something comes up, and the container always has something to fill it.

It also helps to write in a buffer rather than on deadline, which is covered in how to set a newsletter cadence. A fixed shape and a buffer together are what make forty issues feel like a routine instead of forty creative events.

What the structure protects you from

A fixed shape is not only a convenience. It guards against several specific failures that the playbook warns about, and it is easier to see them when they are laid out against the parts.

Part	The failure it prevents
Subject line that names the thing	A vague label that nobody in particular opens
Short opening	A slow start that loses the reader before the idea
One idea	A crowded issue that gives the reader nothing to act on
One call to action	A menu of options that produces no choice
Closing question	An issue that ends in silence, with no reply channel used

If an issue feels wrong and you cannot say why, walk down this list. The fault is usually in one row.

Writing the shape into a template

The simplest way to hold the structure is to write it down as a template that you open each time. Five labelled blanks are enough. Because the shape is the same every issue, writing becomes a matter of filling in blanks, which is exactly the point the playbook makes about forty issues without negotiation.

Add a time budget to it. Decide in advance how long one issue may take, and stop when the time is up. An unbounded edit is how a fortnightly newsletter quietly becomes a quarterly one, and a template with a time limit is a good defence against it.

Frequently asked questions

How long should an issue be?

Long enough to deliver the one idea properly and no longer. The playbook sets no word count; it sets a rule about content. If a paragraph does not serve the idea, cut it.

Can I add a second idea if I have a good one?

Keep it for the next issue. A reader can act on one idea, and a second dilutes the first. Add it to your topic list.

Do I need images?

Only when an image genuinely helps. A plain single column tends to be read like a letter, and heavy layouts signal marketing.

Where does an announcement fit?

As the one call to action, inside an issue that still keeps the promise. It cannot replace the idea.

The full method, with the checklists, is in The Founder's Newsletter Playbook, a free 32-page playbook.