The Editor's Stack
The AI content machine. Yours to own.
An SEO-led, agent-native marketing stack that publishes daily, ships a weekly newsletter, and runs on infrastructure you control.
Most marketing teams have an AI problem that isn't really an AI problem.
They've subscribed to six tools. They're producing more content. The content sounds like everyone else's content. Their analytics look the same as last quarter.
The bottleneck wasn't writing speed. It was clarity, taste, and ownership.
The Editor's Stack solves a different problem. How do you build a system that produces work in your voice, on infrastructure you own, that compounds over time without you typing every word?
Five components. One stack.
The Editor's Stack is a complete content and distribution machine. The components hand off to each other through a shared file system, so the agents stay in sync without you orchestrating them by hand.
Your website
Designed using Claude Design. Built using Claude Code. Deployed on Cloudflare Pages, connected to GitHub. AI-assisted from design to deploy. Owned by you, not your CMS provider.
The SEO Agent
Picks the keywords your buyers actually search for. Optimised for both traditional search and AI answer engines. Builds your content queue automatically.
The Writer Agent
Takes a keyword from the queue, writes the blog post in your voice, publishes it to your site. Daily, if you want it daily.
The Social Agent
Takes each new post and creates distribution drafts. X posts go out automatically. LinkedIn and Reddit drafts land in a review queue for you.
The Newsletter Agent
Produces a weekly newsletter. Industry news, curated and summarised. A thought leadership article in your voice. Ready for you to edit.
What each agent does, and what you do.
The SEO Agent
Finds the keywords your buyers actually search for. Prioritises uncontested terms first, builds toward higher-volume terms over time. Optimised for AEO (AI answer engines like Perplexity, ChatGPT search, Google AI Overviews) as well as traditional SEO.
Most marketers either guess at SEO or pay an agency to guess for them. This is a system that works on your behalf, daily, with a strategy you can audit.
Review the keyword queue once a week. Approve or redirect.
The Writer Agent
Takes a keyword from the SEO queue, writes a blog post in your voice, publishes it to your site. Trained on your tone of voice guide, your past writing, and your editorial guardrails.
The bottleneck for most marketers isn't ideas. It's the time to turn ideas into published content. This removes the bottleneck without removing your editorial control.
Review, edit, ship. Or hand it back for a revision. You're the editor.
The Social Agent
Takes each new blog post and creates distribution drafts. X posts go out automatically. LinkedIn and Reddit drafts land in a review queue.
Most blog content dies in the publishing tool. This makes distribution part of the system, not an afterthought.
Review the LinkedIn and Reddit drafts. Edit if needed. Publish.
The Newsletter Agent
Produces a weekly newsletter. Industry news, curated and summarised. A thought leadership article in your voice. Drafted, ready to edit.
The newsletter is the asset you actually own. Email is the only channel you don't rent. This makes weekly newsletter production sustainable.
Edit the article. Ship the newsletter.
Two stacks. Running today.
The fastest way to evaluate the Editor's Stack is to read what it produces.
MissingLinkz
Campaign link infrastructure for marketing ops and developers.
The Writer Agent updates the blog daily. The SEO Agent drives the keyword strategy, focused on uncontested high-intent terms. The Social Agent distributes across X, LinkedIn, and Reddit. The site itself was designed using Claude Design and built using Claude Code.
Visit MissingLinkz →GoodVibeMarketer
The site you're reading right now.
The Newsletter Agent produces the weekly newsletter — the same one you can subscribe to below. The Writer Agent posts to the blog. The Social Agent handles distribution. Same architecture as MissingLinkz, different voice.
Read the latest newsletter issue →If you want to see what the system actually produces, that's it. The output is the proof.
Three ways to own the stack.
The Blueprint
The architecture document. Free.
A detailed architecture document covering the full Editor's Stack, agent by agent.
- →The system architecture diagram
- →Each agent's role, prompts, and configuration
- →The tech stack (Cloudflare, GitHub, Claude Code, Beehiiv, Stripe)
- →The handoffs between agents
- →The editorial guardrails
- →Deployment and ongoing operations
Enough detail for a determined marketer to attempt it themselves. Free. Drop your email and you'll be reading it in the next ten seconds.
Build it yourself
A cohort-based course. Four to six weeks. We build the stack on your domain.
The course is for marketers who want to build the Editor's Stack themselves, with my help, on their own infrastructure.
- →Designing your stack (architecture, agent roles, editorial guardrails)
- →Building your site (Claude Design + Claude Code, deployed on Cloudflare)
- →Configuring the SEO Agent for your audience
- →Configuring the Writer Agent in your voice
- →Configuring the Social Agent for your channels
- →Configuring the Newsletter Agent for your weekly cadence
- →Editorial workflow, review queues, and the day-to-day
- →An AI-built website on Cloudflare, on your domain
- →A working SEO agent picking keywords for your audience
- →A Writer agent publishing in your voice
- →A Social agent distributing your content
- →A Newsletter agent shipping your weekly issue
Format: Cohort-based. Live Q&A. Four to six weeks. Beta cohort capped at 10 to 20 people.
Pricing: Beta cohort gets launch pricing. Standard pricing applies thereafter.
Done for you
I build the Editor's Stack for you.
For marketers and in-house teams who want the system but don't want to build it themselves.
- →Architecture and stack design, scoped to your business
- →Site build (Claude Design + Claude Code, deployed on Cloudflare)
- →Agent development and configuration (SEO, Writer, Social, Newsletter)
- →Voice and editorial guideline integration, trained on your existing content
- →Handover, training, and ongoing support options
Engagement: Four to six weeks. We start with a qualifying call to scope the work and confirm fit.
Pricing: Discussed in the qualifying call. This is a senior implementation engagement, not a freelance project. If that framing works for you, apply below.
Sensible questions, asked.
01 Why "stack" instead of "tool"? +
A tool is something you rent. A stack is something you own. The Editor's Stack is infrastructure, not a subscription.
02 Do I need to be technical to run it? +
Less technical than you'd think. The course teaches you the system. The DFY removes the build entirely. Day-to-day operation is editing in a browser. If you can use HubSpot, you can run the Editor's Stack.
03 What if I already have a website? +
We can layer the agents on top of an existing site or migrate it. Most existing sites benefit from the migration anyway. We'll cover this in the course or the qualifying call.
04 What if I don't have a brand voice yet? +
We build one. Voice is part of the configuration, not a prerequisite. The Writer Agent is only as good as the voice guide that trains it.
05 Who owns the system after build? +
You do. Your domain. Your code in your GitHub. Your hosting on Cloudflare. Your content. The Editor's Stack isn't a SaaS product. It's infrastructure you keep.
06 Why Cloudflare? Why not WordPress? +
Cloudflare gives you free hosting, free CDN, edge computing for the agents, and serverless functions that the agents can call directly. WordPress was designed for a different era of the web. The Editor's Stack runs on the modern stack because the modern stack is faster, cheaper, and easier to extend.
07 What if the AI changes? Will the stack still work? +
The architecture is model-agnostic. The agents call language models through standard APIs. If the model improves, the stack gets better. If the provider changes, you swap the API. The stack survives the model.
08 Can I just buy access to your agents? +
No. The agents are configured to me, my voice, my audience. The Editor's Stack is a system you build for yourself or have built for you. Renting someone else's voice was never the offer.