What this station holds
A CMO I worked with had a problem. Her brand had a voice. Specific, earned through five years of positioning work. Editorial sharp. Operator-first. Then she handed it to the station. Six weeks later, she was getting content that was accurate, on-brand according to a rubric, and completely generic. The station had learned the format. Not the voice.
That’s the Marketing Station’s job. It holds six functions. First three are high-volume, low-judgment work. Repurposing. Calendar drafting. Inbound response. You point them at source material and they run. Dishes four through six cross into the land of measurement and feedback loops. Newsletter assembly. SEO blog drafting. Ad copy variation. The station is producing for a market now. Quality matters. Then dishes seven through ten are the taste work. Customer stories. Brand-aware response on public channels. Positioning audits. Annual planning. The station is a thinking partner, not a factory. The Chef never leaves.
The dependency property within the Marketing Station is ruthless. Pull the Chef (the taste, the judgment call on what the brand does and doesn’t say) and the station generates compliant content that no one reads. Pull the Sous Chef (the person managing context flow and guardrail maintenance) and the station breaks its own rules every other day. Pull the Training ingredient (the house style, the voice the station learned on day one) and everything that follows is vanilla. This station does not work without all three layers intact.
The dependency property within the station
The difference between this station and Sales is the persistence of the voice problem. A rep can skip ten discovery questions and still close a deal if their relationship is sharp. A brand can skip voice training and nothing recovers. The output multiplies but the identity doesn’t.
Pull the Chef, and you get efficient publishing. No direction. Pull context management (the Sous Chef feeding the station with positioning briefs, competitor moves, market signals) and the calendar drafts itself into irrelevance. Pull the Training ingredient and even a perfect guardrails structure can’t save you because the station has no memory of what you sound like.
Most operators do deploy this station. They just deploy it at DOING, not DISPATCHING. The Chef writes the first two newsletter templates by hand. They review the first four blog drafts line by line. They personally approve every reply to a public question. By week four, nothing is automated because the Chef never stepped back to write the recipe. The station never learned the pattern.
The real threshold is DIALING. The Chef tastes the output, makes edits, updates the recipe (the Training, the Guardrails, the Examples) based on what’s missing. By week six, the Chef is reviewing headlines, not headlines and body. By week twelve, the station is plating content with minimal interference because it learned what quality looks like at this company.
That transition from DISPATCHING to DIALING is where most marketing AI deployments fail. The Chef has a thousand things to do. The station keeps asking for direction. So the Chef walks away. Then it’s all DOING again. Disguised as automation.
The dish order
The Marketing Station follows the same sequence as every station. Dishes one through three run on what already sits in your business. Podcast transcripts. Published blog posts. Customer emails. The training set is already written. You just have to point the station at it.
Dishes four through six cross the threshold. Input gets messier. A newsletter needs context piped in. Blog drafting needs positioning grounded in your actual point of view, not consensus. Ad copy needs to be measured or you’ll keep shipping mediocre. Quality starts to matter because the output is public.
Dishes seven through ten are taste work. Strategic narrative, brand voice across reply channels, positioning audit conclusions. The station is a thinking partner, not a deliverable factory. The Chef stays in DIALING or DECIDING on every plate.
- Repurposing. Take a long-form asset. Return social, email, and short-form versions. See repurposing.md.
- Content Calendar Drafting. Given positioning and releases, produce four weeks of content with titles, formats, and channels. See content-calendar-drafting.md.
- Inbound Response Drafting. Read an inquiry or pitch. Draft the appropriate reply. See inbound-response-drafting.md.
- Newsletter Assembly. Take the week’s wins and content. Return a draft newsletter that sounds like a person wrote it. See newsletter-assembly.md.
- SEO-Grounded Blog Drafting. Produce a draft on a target keyword grounded in your actual point of view. See seo-grounded-blog-drafting.md.
- Ad Copy Variation. Generate ten variants of headline, body, and CTA. Each one different in angle. See ad-copy-variation.md.
- Customer Story Drafting. Turn a recorded interview into narrative case study. See customer-story-drafting.md.
- Brand-Aware Response Generation. Draft replies for reviews, comments, DMs in brand voice. See brand-aware-response-generation.md.
- Strategic Positioning Audit. Read your site and competitors. Return where you’re crisp, where you’re generic. See strategic-positioning-audit.md.
- Annual Planning Narrative. Produce the strategic story behind next year’s plan. See annual-planning-narrative.md.
What breaks this station
House style collapse. The station learned Training from three existing pieces. One was a thought leadership essay. One was a product announcement. One was customer education. They were three different voices. The station averages them. The next forty pieces sound like none of them. Pull examples from one house style. Train on ten pieces in the same lane before deploying.
Context starvation on calendar drafting. The station got a positioning brief from six months ago and a list of upcoming releases. It produces a calendar based on generic marketing moves: case study, thought leadership, announcement, customer story, repeat. The calendar drafts itself into mediocrity because the Chef never told it what’s actually happening in the market or what the positioning actually requires.
Guardrails written after deployment. The rep replied to a negative review in brand voice. Sounds authentic. Makes a promise the company can’t keep. Nobody set guardrails. Nothing was scaled. The Chef should have written what the brand never says before the station ever touched a reply.
Measurement death on ad copy. The station generated ten headlines. The team loved number three. They ran it. Never tracked if it actually converted better than the control. By month three, the station is still using the same pattern it learned on day one. What worked stays unknown. What broke stays broken.
Chef retreat on positioning and planning. The Chef has been in DIALING all quarter. Tasting the output, updating the recipe, getting better each week. Then September hits. Budget planning. The Chef walks away. Tells the station to keep publishing. By October, it’s plating content with no direction because it never learned where the business was heading. Come January, the annual planning narrative reads like strategy if you squint. It doesn’t read like your strategy.
The Monday Move for this station
Start with a dish the Chef already owns. Something the Chef has been publishing every month. A blog post. A newsletter. An email sequence. Whatever the Chef touches regularly. Capture three real examples the Chef wrote. Use dish one, Repurposing, to test the station. Feed it one recent long-form asset. The station produces social clips, newsletter breaks, email subject lines. Compare what the station made to how the Chef would have broken it down. Adjust Training (the examples, the guardrails on what the Chef never does). Run it again. By week three, the Chef is comparing output quality, not direction. The station is running. The Chef is DIALING. This is what month four looks like.
Original framework. Distilled from client work. Companion to The Station Plan and The Professional Recipe.