AUTOMATION April 5, 2026 · 5 min read

Why My AI Writes All Our Blog Posts at 10am Every Morning

I got tired of relying on motivation for content. So I had Ari build a daily publishing pipeline that runs whether I feel like writing or not.

Why My AI Writes All Our Blog Posts at 10am Every Morning

Motivation Is a Terrible Content Strategy

I used to treat content like a mood.

If I felt inspired, I'd write. If I had a packed day, I'd skip. If ad fires popped up, blog was dead for a week.

That works if content is a hobby. It doesn't work if content is an acquisition channel.

So I stopped pretending I was going to "be more disciplined" and did what I always do when a repeated task annoys me: I told Ari to automate it.

Now every morning at 10am, one article gets produced and published from a pre-built queue.

No hype. No "batch day" theater. No waiting for a creative window.

Just output.

The Core Rule: Queue First, Writing Second

The pipeline only works because the queue is decided ahead of time.

I had Ari build projects/machine-earned/blog/article-queue.md as the source of truth for the month:

That one file solves 80% of the usual content chaos.

Most teams get stuck because they ask "what should we write today?" every day. That's a strategic question pretending to be an operational one.

We answer strategy once, then execute daily.

What Actually Runs at 10am

Here's the real flow:

  1. Read the queue and find the next unpublished article
  2. Pull source context (scripts, docs, prior notes)
  3. Draft the article in my voice (first person, founder perspective)
  4. Generate a hero image with KIE nano-banana-2 (16:9, dark/tech)
  5. Build the static article HTML
  6. Rebuild blog index
  7. Deploy to the server
  8. Mark that queue item as [PUBLISHED]

The important part is this is one deterministic run, not a dozen manual mini-tasks.

Why This Is Better Than "AI, Write Me a Blog Post"

Most AI content setups fail for one of three reasons:

I designed around those failures.

1) Constraint: Voice + rules are explicit

I force a specific voice: me as founder/operator.

Not "an AI assistant sharing tips."

Not "a neutral editorial voice."

Not fake thought-leadership fluff.

The framing is real: I decide, Ari executes, we ship, we review outcomes.

2) Source-grounded writing

When an article references systems, scripts, or results, Ari has to read the actual files first.

That keeps posts tied to reality:

The quality jump from this alone is massive.

3) Built-in publish step

If the article isn't live, it's not done.

I had Ari wire the builder/deployer script (scripts/publish_me_article.py) so the same run that writes the article also compiles and deploys it. No handoff. No "I'll publish later." No orphan drafts.

The Build/Deploy Layer (Simple on Purpose)

I didn't want a heavyweight CMS workflow for this site.

The Machine Earned blog is a lightweight static publishing flow:

Could I overengineer this with a full content backend, editorial UI, webhooks, preview environments, etc.? Sure.

But that's not the game right now.

The game is publishing useful content every day with near-zero friction.

The Image Step Matters More Than People Think

Most auto-generated blog workflows either:

I wanted consistency without turning image creation into a design project.

So I standardized hero generation with one command against KIE nano-banana-2:

This gives every post a coherent visual identity without me touching Figma.

The Hidden Win: Reduced Decision Fatigue

People talk about automation like it's only a speed thing.

For me, the bigger win is cognitive load.

When content is manual, you burn energy on low-value decisions:

Multiply that by 30 days and it's a tax on execution.

The 10am system removes all those micro-decisions.

I front-load the thinking into the queue, then let the machine run.

Where Humans Still Matter

I'm not pretending this is "set and forget forever."

I still review outcomes and adjust the system:

Automation handles repetition.

Direction still comes from me.

That's the right split right now.

What Broke While Building It

A few practical lessons from implementation:

None of this is glamorous. All of it is the difference between a demo and a working pipeline.

If You Want to Copy This

Steal this structure:

  1. Create a 30-day queue in markdown
  2. Add a one-line brief and source notes for each entry
  3. Enforce one voice/persona
  4. Build a deterministic publish script
  5. Make publishing state explicit ([PUBLISHED])
  6. Run daily on a fixed schedule

You can do this for:

The specific tools don't matter as much as the operating model.

Why 10am?

Because consistency beats cleverness.

10am is late enough that overnight infra issues are usually obvious, and early enough that content is live during the business day.

Mostly though, it's just a fixed anchor.

Once the system has a stable trigger time, the rest of the workflow becomes predictable. Predictable systems compound.

Final Take

I don't want to "work on content" every day.

I want the business to have content every day.

Those are different goals.

The first depends on my mood.

The second depends on systems.

So I had Ari build the system.

And now, at 10am, it ships.

---

I’m building systems that let one operator do the work of a small team. If you want the behind-the-scenes playbook as we ship in public, follow along at machineearned.com.

Get the playbook. Every experiment. Every number.

I send one email per week breaking down exactly what my AI co-founder built, what it earned, and what failed spectacularly.

Subscribe Free →