Why in-house blogging quietly stalls at month four

The pattern is so consistent it is almost a law. A company decides to take content seriously. Two or three months of real posts appear. Then the fourth month has one post, the fifth has none, and by month seven the blog is a liability that makes the company look dormant.

Nobody involved was bad at their job. The failure is structural, and it is worth naming precisely, because the wrong diagnosis leads to the wrong fix — usually hiring another writer, which does not help.

Nobody owns a calendar that isn't in a system

Ask who owns the blog and you will usually be told a name. Ask where the publishing schedule lives and the answer gets vague: a spreadsheet, a Notion page nobody has opened since the kickoff, or somebody's intention.

An intention is not an owner. Real ownership means a specific person has a specific obligation on a specific date, and somebody notices when it is missed. Almost no in-house blog has that. The blog is in everyone's objectives and nobody's calendar, which means it is the first thing that yields when a week gets tight — and every week eventually gets tight.

The work is invisible, so it loses every prioritisation fight

A blog post that ships produces no visible event. Nothing breaks if it does not ship. No customer emails to ask where it is. The feedback loop is measured in months and the attribution is contested even then.

Now put that against a launch date, a customer escalation, or a board deck. In any honest prioritisation, the post loses, and it loses correctly on the day. The problem is that it loses correctly every day, and the accumulation of individually reasonable decisions produces an outcome nobody chose.

This is why exhortation does not work. Telling the team the blog matters does not change the arithmetic of any particular Tuesday.

The approval chain was never designed

Most in-house blogs have an accidental approval process: the writer sends a draft to whoever seems senior enough, that person is travelling, the draft sits, the moment passes, and the post publishes late or not at all.

Notice this is a bottleneck that gets worse the more seriously people take the blog. A post nobody reviews ships fast and might embarrass you. A post that needs three sign-offs ships never. Almost no company sits down and designs the middle path — one named approver, a fixed window, and an explicit default for what happens when they do not respond.

The subject list runs out before the enthusiasm does

The first ten subjects are easy, because they are the ten things everyone has been meaning to write. Nobody plans the next thirty.

By month four, the meeting where subjects get chosen has become the bottleneck rather than the writing. It is a genuinely hard meeting — it requires someone with judgment about the business, and those people are expensive and busy. So it gets postponed, and without subjects there is nothing to write, and the silence begins there rather than in the writing.

What actually fixes it

Not another writer. If writing were the constraint, the first three months would not have worked.

The fixes are boring. Put the schedule in a system that acts without being reminded. Name one approver with a deadline and a default. Build the subject list forty deep, in one sitting, from the questions your sales team answers repeatedly — that meeting is worth more than any individual post. And pick a cadence low enough that you would be embarrassed to miss it, rather than one that sounds ambitious in a plan.

You can do all of that in-house. Some companies do, and their blogs are excellent. The honest observation is that it requires somebody to own the boring parts permanently, and "permanently" is the word most plans quietly omit.

What we are actually selling

Not writing ability. The engine writes well, but so does a good freelancer, and so does your marketing manager on a good day.

What we sell is that the calendar acts on its own, the subject list is maintained rather than rediscovered, and the approval step is ten minutes with a default. Those are the three things that failed — not the prose. Any solution that fixes the prose and leaves the other three alone will stall in month four too.