The content engine that works the week you already had
Every other tool waits for you to open it. This one goes through the calls you were on and the things you published, writes the week, and hands it to you Monday morning.
Your week is drafted. 4 posts inside.
From 2 calls and 1 article you published last week.
- MonProblemYour reporting is late because nobody owns the number
- TueProofNine days to two, and the part that actually did it
- WedStoryThe QBR where the customer explained our product to us
- FriOpinionMost dashboards measure the work instead of the outcome
You did not open anything. There are posts waiting anyway.
You bought the tool. It works. You opened it four times in January and twice in February, and the last time you opened it you sat looking at the empty box trying to remember something worth saying. It is not that writing the post is hard. It is that starting from nothing, every week, forever, is a job nobody keeps doing.
A blank box is not a tool, it is a chore with a subscription
Every writing tool in this category has the same shape. You arrive with material. It helps you shape it. Which means the tool works exactly as often as you remember to show up, and the part that actually breaks, showing up, is the part it does not touch.
An engine runs whether or not you think about it. This one goes and gets the material itself, from the calls you were already on and the things you already published, writes the week from it, and arrives Monday morning without being asked.
You did not open anything. There are posts waiting anyway.
How it works
Point it at where your week already happens.
Your meeting recorder, your blog’s feed, your own notetaker. Connect it once. It does not ask you again.
It works over the weekend.
It reads what came in, finds the ideas worth a post, throws away the ones that are not, and writes what is left in your voice. Nothing is padded to fill a slot.
Monday, it is in your inbox.
Read them, change a line if you want to, approve what you want. Approving is the first work you do all week.
- Discovery callTue, 34 min
- Customer QBRWed, 51 min
- What we learned shipping v2Your blog, Thu
It picks these up on its own. There is no weekly step for you here.
The week you had nothing to say is the week it matters
No calls, no articles, nothing published: the digest still arrives. It draws on the stories you have already banked, favouring ones you have never told, and it will not retell anything from the last three months. Two of the five weeks this has run in production were exactly that week.
It decides what is not worth posting
The reason an engine can run without you is not that it writes fast. It is that it throws things away.
Your reporting is late because nobody owns the number
Nine days to two, and the part that actually did it
The QBR where the customer explained our product to us
Nothing in this week’s material was worth a post here.
Most dashboards measure the work instead of the outcome
It leaves the slot empty rather than fill it
Every idea is graded before anything is written. A day with no genuine candidate stays blank. Four real posts beat five where one is filler, and filler is what readers learn to scroll past.
Two posts from one call cannot be the same post twice
They are written one after the other, the second able to see the first. Afterwards a check flags it anyway if they lean on the same figures.
It checks new drafts against what you already published
A match only counts if the checker can quote the specific line that appears in both texts. A verdict it cannot evidence is thrown out, not shown to you as a maybe.
It never quietly retells an old story
Stories you have told are held back for ninety days. When one does come round again, it is because it was the best thing available, not because the queue needed filling.
That is the difference between a system you can leave running and a tap you have to watch. The screens on this page are examples, not customer data. The engine is young and we would rather show you how it decides than a number we made up.
Nothing is published without you
The engine writes. It never posts. Every draft waits for an explicit approval, and that is a position we hold on purpose, not a setting you can switch off.
What it will not do
The limits, stated plainly, so you can decide before you sign up.
It will not run daily.
Once a week, Monday. If your plan is three posts a day, this is built on a different belief about what works, and you should know that before you sign up.
It will not start from a prompt.
If you have not been in a meeting, published anything, or banked a story, there is nothing for it to work from. It is an engine, not a generator.
It will not publish anything you have not read.
Every post waits for your explicit approval. That is a position we hold on purpose, not a setting.
It will not invent a number.
Claims are checked against your own source material before a draft ever reaches you.
It will not write about someone else’s week.
No trending topics, no viral swipe files, no rewriting a post that worked for somebody else. Only your material.
Text posts, your profile, LinkedIn.
No carousels, images, video or documents. Personal profile, not company pages. One network, done properly.
Works with
Meeting notetaker
It writes the post, not the minutes. Your calls become post material.
A shaped week
A shape for the week, so it isn't five versions of the same post.
Queue
One tap, and it's handled.
Brand memory
Your stories, numbers and opinions, kept. A quiet week still has something to say.
Questions
What is an AI content engine?+
A generator waits for you to bring it something. An engine collects the material itself, on a schedule, and produces finished drafts without being asked. PublishFlow reads your meeting transcripts and published articles each week and writes next week’s posts from them.
What does it need from me to start?+
One source connected, and then nothing weekly. Most people connect their meeting recorder and their blog’s feed once and never touch the setup again.
What happens in a week where nothing happened?+
The digest still arrives. It draws on the stories already saved from your past material, preferring ones you have never posted, and it will not retell anything from the last ninety days.
Can I get the digest more often than weekly?+
No. Weekly is the product, not a limitation we plan to remove. A daily engine produces a feed of filler, and filler is what makes people stop posting.
Does it post to LinkedIn by itself?+
Never. It writes and it queues. Publishing needs your explicit approval on every single post.
Which meeting tools does it read?+
Fireflies, Fathom and tl;dv by API key, plus PublishFlow’s own notetaker, plus any RSS or Atom feed for what you publish. API access on tl;dv requires their paid plan, not ours.
What happens when my trial ends?+
The digest keeps arriving, with the posts previewed rather than opened. Upgrading unlocks them, including the ones from the weeks you were away.
Next Monday is going to happen either way
Fourteen days free. No credit card.
Start freeNothing is published without your approval