We build the boring layer that makes content programmes work

It started with a queue that never moved

AutoBlogJet began as an internal tool. Our founder was running content for a group of niche publishing sites and kept hitting the same wall: the strategy was fine, the writers were good, and yet the queue barely moved. Briefs lived in one document, drafts in another, approvals in email, and publishing in whoever happened to be online.

The fix was not a better writing tool. It was a pipeline: one place where a keyword becomes a brief, a brief becomes a draft, a draft gets checked and approved, and an approved post publishes on a schedule. Once that existed internally, the publishing rate roughly doubled without hiring anyone.

We released it publicly in 2024. Today AutoBlogJet is used by in-house teams, agencies and independent publishers who care less about clever output and more about a queue that keeps moving.

Built by people who ran the queue themselves

Our team is deliberately small and split between product engineering and customer support. Everyone who works on the product has, at some point, been responsible for a publishing calendar that was behind schedule.

That background shows up in the details: briefs you can reuse, approvals that survive a handover, and error messages that tell you what to fix rather than what went wrong.