Run the content engine on a real cadence
Content that talks to nobody ranks for nothing, and one great post that never repeats is a fluke, not an engine. Build from real buyer language, publish on a rhythm, and grow the list that actually opens it.
Run the content engine on a real cadence
Content that talks to nobody ranks for nothing, and one great post that never repeats is a fluke, not an engine.
Build from real buyer language, publish on a rhythm, and grow the list that actually opens it.
Details
Details
Details
Details
Seven figures influenced
The same content system that earned that number: buyer language turned into briefs, then a publishing cadence that keeps shipping and growing the list.
The real language
Writer-ready briefs
A growing audience that opens what you send
Every piece rewritten in your voice before it ships
The workflow that solves it, one step at a time.
Each step is the plain question you are already asking. The skills answer them in order, one handing its receipt to the next.
Who to talk to, a non-leading interview guide, and how to turn transcripts into positioning and messaging inputs.
Turns a keyword or topic plus an audience into a writer-ready brief that kills the back-and-forth.
The subscribe offer, the growth loops, the content rhythm, and the metrics that matter beyond list size.
Removes the hedging, the rule-of-three, and the sycophantic openers, then rewrites the draft in your voice.
The real language, writer-ready briefs, a growing audience that opens what you send, and every piece rewritten in your voice before it ships.
- All 4 chained skills resolve to real, scored skills.
- Has a problem, an outcome, 2+ steps, and proof from a real build.
- Ships an example chat showing the play run in Claude.
- Reads in plain operator voice, grounded in a real build.
We did not just check the structure. A judge read this play against the full text of every skill it chains (composition), then ran it on a real scenario end to end (simulated). It passed both. Test scenario: Sam, Content Marketing Manager: blog gets traffic that doesn't convert, wants to fix it at the root and build a real publishing cadence.
This play runs across the org, not inside sales.
Every function below owns a piece of the play. Skip one and it stalls where most GTM plays stall: in the handoff.
Without it: Briefs run on guesses and the content reads like it.
Without it: The engine runs out of real language in a quarter.
Without it: The engine cannot defend its budget when cuts come.
Watch the skills answer in order.
Describe your situation in plain language. The right skill fires on its own and hands its receipt to the next.
Before you run it, I ran it for real.
This workflow is genericized from a real build. Here is the number it moved, and what I actually did.
WHAT I DID ›
AEO and GEO are not SEO with a new coat of paint. The machine answering your buyer only quotes what it can source, in the buyer's own words, so start by understanding the customer, rewrite the positioning to be quoted rather than ranked, reallocate your prompt budget to Defend, Intercept, and Define, name the AI only where it earns the line, and lock the story to one versioned source. Get found where the buyer actually looks now.
Dig into the full build →The cadence is only as good as the writer holding it
Customer-research and the brief hand writers the exact words buyers use and a start-ready outline; the pipeline comes from a reader deciding this person gets my problem. Here is how a marketing leader keeps the engine shipping weekly without drifting into content nobody recognizes.
Before any brief goes to a writer, someone reads the buyer quotes it was built from out loud against the outline. If the brief could have been written without the research, it goes back.
- 01Train writers on the transcripts
Give writers the raw customer-research language, not just the brief. A writer who has read ten buyer quotes stops inventing pain points.
- 02Protect the weekly ship
One brief in, one piece out, every week, and the slot does not move for a better idea. The engine is the rhythm; the fluke is the exception.
- 03Run the voice gate before publish
Humanize-draft is a gate, not a suggestion. Nothing ships until the AI tells are stripped and the piece reads like one person wrote it.
- 04Inspect opens and language monthly
Review which pieces got opened, replied to, and cited by sales, and watch what newsletter-growth added against what it kept. Feed the winning language back into the next round of briefs.
One plugin. 4 skills, bundled.
The whole playbook installs as a single plugin in Claude Code, no copy-pasting 4 times. Or grab any single step above. It runs on what you paste; connect your stack to go live.