The Autonomous Blog Agency

You do not have a motivation problem. You have a production line problem.

For years the advice was the same: put your work online, share what you know, build something that markets you while you sleep. Good advice. It ignores the arithmetic.

Finding the topic, researching it, drafting it, editing it, illustrating it, publishing it, then doing it again next week, for months, before the first reader shows up. One person cannot be researcher, writer, editor, designer and SEO technician in the same evening after a client day.

So I stopped trying, and built the department instead.

What this actually is

Ten agents, each with one narrow job and a written set of instructions. Nine production stages. Three points where the chain stops and waits for a human decision. Everything else runs unattended.

It has been running my own blog for months. Every failure mode in this kit is one I hit first.

What is in the kit

The architecture, explained. Three layers and why they stay separate. The data model, field by field, with the constraint that costs everyone a day when they discover it themselves. Nine stages, one owner each, and why visuals come before SEO.

The ten instruction files, printed and shipped. Roles, scoring rules, closure checklists, constraints, and the failure modes that produced them. Printed in full so you can judge them, and delivered as editable Markdown so you never retype a line.

A Notion template you duplicate in one click. Three databases, every property typed, every select option pre-created, the relation already wired, plus worked examples at each gate.

A starter repository you fork. Folder structure, a frontmatter schema that renders, a .gitignore that already excludes your secrets, and one example article to publish by hand before any agent touches anything.

The parts that are not automated, and why. Images stay manual. I spent days trying to make generation consistent and still need three or four attempts per usable picture. That failure rate has no place in a pipeline, so the kit tells you to curate the bank yourself and automate only the selection.

An LLM-assisted build path. Two prompts: one that interviews you until your setup is fully specified, one that hands the result to your agent gateway to build the agency. Both as files, not text to retype.

Written for someone who has never handled an API token

The kit does not assume you know what a repository is. There is a glossary, a full walkthrough from nothing to a blog that publishes from a commit, and a credentials annex with the exact path for each service and the specific trap each one sets. The step everyone skips, and the error it produces three hours later, is called out by name.

You will not write code. It is not a no-code project either, and the first page says so plainly rather than letting you discover it on page eighteen.

Start with two agents, not ten

The title says ten because that is where it ended up, not where it began. Two agents are enough to publish: one that writes, one that assembles and commits, with you supplying the angle. That version takes an evening and proves the whole chain end to end. The kit specifies it exactly, then gives you the order to add the rest.

What it costs to run

About five dollars a month on a cheap fast model, at one to two articles a week, research included. Nothing extra if your agent gateway can use a subscription you already pay for. The knowledge base is free, the hosting is free, the repositories are free.

The comparison is not against a freelance writer at two to five hundred euros an article. It is against the article you were never going to write.

Honest about the trade

Checking becomes your main activity. It feels thankless if you are used to building things, and it is the price of the arrangement. The kit says so in the governance section rather than in a footnote, because that is the part people quit over.

What you get

The 66-page PDF, the ten instruction files, the two prompts, the Notion template link, and the starter repository. One price, no subscription, no upsell.