Capacity, not talent

Publish more posts without hiring a writer.

There are four ways to raise output, and each one fails in a different place. None of them is “write faster” — the hours are almost never the constraint, and understanding which one actually is tells you what to buy.

Start with your domain What automation means here

The four options.

Each one is honest for a particular situation. The failure mode is listed because that is the part the comparison usually leaves out.

Do it yourself

Costs almost nothing in money and everything in calendar time: research, outline, draft, images, links, publish.
Quality is the highest of the four when you know the subject — nobody else writes with your context.
Fails when the week gets busy. The output is the first thing to slip, and it does not come back on its own.

Buy the posts

A freelancer costs per post, prices vary by an order of magnitude, and the brief is now your job — which is most of the work.
Scale comes from hiring more writers, and every new one needs the brief, the voice and the review.
Fails in review: posts arrive that answer the query and still need an hour of editing to be true for your business.

Generate at volume

An AI writer with a bulk mode publishes hundreds of pages for the price of a few hours of your attention.
The right answer when the deliverable is programmatic pages — locations, comparisons, glossaries — not a business blog.
Fails on judgement: it writes what you paste in, including a fifth post on a subject you already cover.

Run a pipeline

Something else plans the query, writes to the brief, dates it and publishes it, on a cadence you set once.
Your remaining job is the review and the strategy — the two parts where a person is genuinely better.
Fails if you want to control every word. It is a publishing process, not an editor you direct sentence by sentence.

The bottleneck is almost never the writing.

Ask someone why their blog is quiet and they will say they have no time to write. Watch what actually happens and it is the three tasks around it.

Deciding what to write: The highest-cost step per minute spent: a topic that duplicates a page you already have, or answers a query nobody types, wastes everything that follows. A plan built from the queries your site is missing removes the decision rather than speeding it up.
Finding a slot: An undated topic is not a commitment. The week fills up, the post slides, and the blog has published nothing for two months without anyone deciding that. Publishing days per site fix the slot before the writing happens.
The publishing overhead: Images, metadata, the internal links, the canonical URL, the sitemap entry. Individually minutes; collectively the reason a finished draft sits in a document. This is the part a pipeline does in the same run as the writing.

What actually changes when the cadence runs.

The output of a blog is not the drafts. It is the live pages, which is why this is a publishing problem rather than a writing problem.

Dates you do not have to defend

A plan that is already dated is the difference between “we should blog more” and a page that went live on Tuesday. The queue holds the date: a post that lands late does not push the rest of the month back with it.

A review you can actually do

Ten drafted posts a month is not a review task, it is a second job. With approval on, each post waits for you and publishes on its own date once released — which is how a team of one keeps a weekly cadence without becoming an editor.

Questions this raises.

The two that come up first, and the two that decide it.

Can one person publish four posts a month?

Yes, if the deciding is done for them. The writing is rarely the part that stops a solo marketer — choosing the next query, finding the time to research it, and remembering to publish are. Four posts a month is roughly a day of work when the query, the outline and the date already exist, and two weeks when each one starts from an empty page.

Is an AI writer with a bulk mode the same thing?

No, and the difference matters at this scale. A bulk generator writes what you paste in; it does not know which query your site is missing, and it will happily produce a fifth post on a subject you already cover. Volume tools are the right answer when volume is the goal — hundreds of programmatic pages. This is a page about a cadence.

What if the posts are bad?

Then the cadence is worth nothing, which is why every option here has a review step. On the pipeline side that is an approval setting: posts wait for you and go out on their date when released, instead of publishing unreviewed. Keep approval on for the first month and turn it off when you trust the briefs.

Do I need to hire eventually?

At some point a person who knows the subject is worth more than any tool — for the two or three pieces a quarter that only you can write. The useful split is: the tool covers the searchable questions, and the hire works on the pieces that need an actual opinion. Deciding this after the cadence exists is a much easier buy to justify.

Nothing here is a promise of rankings, traffic or revenue — those are not guaranteed, and no amount of output changes that. What is guaranteed is what gets published and when it goes live.

Related.

The process side of outsourcing, and the two pages that go deeper.

Outsourcing SEO content without losing brand voice — what to put in the brief and the voice guide, whether the writing is done by a person or not.
What an automated SEO content service actually does — the plan, the writing and the publishing, step by step.
How many posts a month a blog needs — what cadence to aim for once capacity stops being the constraint.

Keep the review and the strategy.

A dated plan built from the queries you are missing, posts written to it, and a blog on your own domain. You approve what goes out; everything between the decision and the live URL runs on its own.

Automate my blog

20€ / site / language / month3 days free, no card