Not for lack of ideas. Because a post is four jobs pretending to be one: decide the angle, do the reading, write it, then fill in the title, slug, category and meta description before it will publish.
Set the column once — topic, angle, voice, structure. Every run researches the week and delivers the finished post and its publishing metadata together, so the gap between reading it and shipping it is a paste.
A schedule is a promise about the future, which is why it breaks. Twice a week is right for an average balcony in an average July, and nobody gardens on an average balcony in an average July.
Thursday's 11mm changes the answer for the following four days. A calendar alert can't know that; it fires anyway, you water anyway, and the tomatoes split.
The useful instruction isn't “water on Tuesdays”. It's “skip today, the soil is still holding Thursday's rain, and go heavy on Saturday because it's 34° with wind.”
The rosemary wants neglect. The basil wilts if you look away. A single schedule flattens all of that into one wrong number…
Ask a chatbot for a blog post and you get a blog post: a block of text you now have to title properly, slug, categorise, write a meta description for, and check for structure. That last twenty minutes is where posts die on a Tuesday evening. This template treats those fields as part of the output, because they are part of the job.
Our public writing is one weekly routine running the Article template. It reads our own product, imagines a person with a recurring decision, and publishes why a routine solves it. Nobody sits down to write it.
Go and read a few. It's the honest version of a sample — you can judge the voice, the structure and the sourcing on posts we actually shipped rather than a demo we curated.
No — and deliberately. Each run lands as a draft for you to read. Copy it out when you are happy with it. Automatic publishing is the fastest way to put something wrong on your own site under your own name.
That is the real risk with a recurring column, so the brief carries your voice and the routine reads what it already published — it will not repeat a topic or reuse an angle. Leave a note on any post and the next one shifts.
Yes. joris explains on this site is a Routine running this exact template — a post a week, written and published by joris. Read it and judge the output before you sign up for anything.
Only if you turn that on for the routine. A column built on your own experience does not need it; one that tracks a fast-moving field does. When it is on, claims are grounded in the sources it read and linked.
A 14-day free trial of everything, no card. After that one flat price — less than a single commissioned post, for a post a week.
People who run this routine tend to add one of these within a fortnight.
Your topic, your voice, your structure. It researches the week and drafts the whole issue — subject line, preview tex...
Explore →Different job, different document. Tell us the output you'd want waiting for you and we'll build the template.
Ask us →Release notes from a changelog. A monthly customer story. A docs page that tracks a moving product. Anything you'd publish on a schedule if writing it weren't four jobs — describe it and we'll design the output template.
Set the column once — topic, voice, structure, rules. Every run researches the week and lands the finished post with its publish fields filled in. You read it, cut a paragraph, ship it.
Start free