One post.
A week of momentum.

Something worth telling happens maybe once a week. What stops it being told is not the writing — it is the rewriting: the same news, re-shaped by hand for every place your business shows up, until posting becomes an afternoon and the afternoon does not happen.

Compose is the desk where that collapses back into one job. Your connected channels sit at the top; you write the caption once, in your own voice, and tick where it should go. The idea, the offer and the call to action travel together — what changes per channel is the telling, which is exactly the part you did not want to do by hand.

You are never sending blind. As you type, the preview shows your words the way a chosen channel will carry them, against that channel’s own length limit — and the screen says plainly that a preview is a guide, not a guarantee, because each network lays a post out its own way. Choose a post, a reel or a story; add the hashtag row; done.

And when the box is blank, Maven sits in the composer with you: caption starters for the empty morning, and a Write with Maven control that drafts from what you give it. You still say yes to every word — it is your name on the post.

A queue is only useful if it tells the truth. This one keeps waiting, held, sent, failed and drafted as five separate states, and a piece of writing sits in exactly one of them. Nothing is still described as scheduled after it has gone, and nothing is described as sent when it never left the building.

It is grouped by the day it goes out rather than by the day it was written, which is what makes the gaps visible. An empty Thursday looks like an empty Thursday, and a week with everything crowded into one morning looks like that too — before it happens, while it is still free to move.

The same week reads as a calendar when the shape matters more than the list: which places you are showing up in, how far apart, and where the open slots are. It is the same queue underneath, so a piece moved in one is moved in the other.

And it is editable from where you are reading it. Change the wording, pull something back out, or let it go — without opening another screen to find the piece you were already looking at.

Posting in bursts and then vanishing is not a strategy. It is what happens when the plan lives in somebody’s head and the week gets busy. The planner moves the plan somewhere better: one ongoing calendar of what you intend to say, with each intention sitting on the day you meant it for.

A grid is honest in a way a list is not. A day with something planned shows what it is; a day with nothing offers you the space. Spacing the message out stops being arithmetic you do in your head and becomes something you can see — and the gap in the middle of the month is visible to you long before it is visible to anybody else.

The hardest part of showing up was never the writing. It is deciding, every single day, what the thing should be. So you can hand that decision over once: say what the stretch is about, what you want out of it and how often you want to appear, and the month comes back drafted — a title, an opening line, the kind of piece, the day. Each run is kept as its own plan, so the thinking behind last month is still readable when you sit down to do the next one.

And a plan is a proposal until you say otherwise. Nothing in it goes anywhere on its own. You open a slot and send it to the composer to make it yours, or you hand a whole week across in one motion — and only then does any of it become something waiting to go out.

Everything else in this workspace is written before the fact. The planner decides what the weeks are about, the calendar puts pieces on days, the queue holds what is going next. All of it is intent, and intent is not evidence. This screen is the other half: it is written as things happen, one line per piece, and it is the only place that can tell you a thing is genuinely out rather than genuinely scheduled.

Each line is built to be read without opening it. The headline says where the piece went, so a run that fanned out across several audiences reads as several lines and you can see the shape of it immediately. Under that sit the opening words of the piece itself, which is almost always enough to recognise it, and beside it the moment it went. Reading the week’s publishing becomes reading a list, top to bottom, instead of opening things one at a time to find out which is which.

And because it is a record of attempts rather than a list of wins, it is also where the awkward cases surface: the product keeps every attempt, every delivery and every hold on this same timeline, so something that did not go — or has been held back — sits in the run where you will actually see it, next to a control that takes you to it. The shipped picture above is a clean run, with nothing held and nothing failed.

Name the push and it becomes a place. The social series for it, the letters it sends and the landing pages that catch what it brings in are grouped under the campaign’s name — instead of scattered across tools that do not know they are working on the same launch.

Mid-launch, the question you actually ask is “how is it going” — and this screen answers it without an audit. Each campaign carries its own one-line brief, its state, and the plain counts of what has been written, what has gone out and what is still scheduled. A push that has not started sending says so, in its own row, rather than looking like one that has.

And the row is where the work carries on. Compose straight into the campaign and the new piece belongs to the push from its first word; open the campaign on the calendar and the whole run is laid over your week, each piece where it will land.