The job
You have the week’s content. A blog post. Customer story. Announcement. Your own observations. Tools. Links. The ingredients are there. The newsletter just needs assembly. A headline. An intro that makes someone open it. The pieces arranged in order. A closer that makes sense. Someone needs to spend an hour on this every week.
The station can do this. Not write the individual pieces. Not decide what ships. But given the pieces and the format, assemble something that reads like a person wrote it. Something warm enough to open. Smart enough to read through. Clear enough on what to do next.
The recipe
All seven ingredients still apply. The leverage on this dish is Context (Ingredient #2). The station needs to know what it’s writing about. Not just the pieces. The week. The moment. What matters right now.
Training still matters. The newsletter needs to sound like the Chef. Examples show the station the structure and flow you prefer. But the context does the load-bearing work. Feed the station the context and it won’t assemble a generic newsletter. It will assemble one that makes sense for this moment.
Guardrails matter too. Things you never do in a newsletter. You never promise something that one of the pieces contradicts. You never bury the announcement. You never ask them to do something unclear.
How to build it
- Gather the week’s source material. The actual pieces you want in the newsletter. The links. The announcements. The personal observations if you have them. Collect it all. This is the Context block.
- Add contextual notes. What’s happening in the market. Customer signals from this week. Why this particular week of content matters. One paragraph. This context helps the station write the opener.
- Pull the last three newsletters you sent. Real ones. Note the structure. How many pieces. Where the announcement lives. The tone of the closer. The station will learn the rhythm.
- Define guardrails. “Never bury the announcement in the middle.” “Never ask them to do something without context.” “Always include a personal note if you have one.” 4-5 rules.
- Feed the source material, context, examples, and guardrails to the station.
- Review the draft. Does the opener make you want to read? Does the flow make sense? Does the closer land? Are guardrails intact?
- If the draft is 70% there, ship it with one pass of Chef editing. If it’s softer, update Training or Context and rerun.
What breaks it
- Context is missing. The station gets a blog post, a case study, and a link. It doesn’t know why these three pieces matter this week. The newsletter reads like a bulletin board, not a gift.
- Examples are too thin. You pull one newsletter from last month and one from three months ago. They were written in different moments with different intent. The station has no pattern to learn. The assembly is random.
- Guardrails live in training, not guardrails. You say “warm and personal” in the Training block. The station has no idea what not to do. Better guardrail: “Never make an announcement feel transactional. Always give context on why we’re doing this thing.”
When it’s working
By week two, the Chef is editing the draft, not writing from scratch. Most newsletters go live with one or two line edits. By week four, the Chef is reviewing for tone and guardrail fit, not structure. By week eight, the Chef is mostly spot-checking, and the newsletter is consistent week to week because the station learned the rhythm.
The signal that the recipe is sharp: a subscriber replies to the newsletter like the Chef wrote it personally. The flow was clear. The pieces made sense together. The closer landed.
Monday Move
Gather this week’s pieces. Blog. Case study. Links. Announcements. Write down the context. What’s happening this week that matters. Give that to the station. Ask it to assemble a draft newsletter. Review for flow and tone. Make edits. Send it. Review the next week’s assembly to see what the station learned. By week four, you’re making line edits, not rewrites.
Dish 4 of 10 on the Marketing Station. Build-note leverage: Context (Ingredient #2).