Your content plan goes in as ideas; what comes out is a pack per idea — the LinkedIn version, the Instagram caption, the Telegram post, the X thread — each written to that platform’s length, format and register, with hashtags and a visual brief attached. Nothing publishes itself: the pack lands in a review queue where your editor edits, approves or kills it, and the approved posts go into the scheduler.
Writing the idea takes twenty minutes. Reshaping it for five platforms takes two hours, every time, and it is the least interesting work in the team.
LinkedIn ends up corporate, Instagram ends up chatty, and neither sounds like the brand. With three people writing, the drift compounds until nobody can define the voice at all.
A post ready on Tuesday goes out Friday because somebody had to log into four platforms. The calendar becomes a wish list, and consistency — the one thing social rewards — is the first casualty.
We turn your voice into rules a model can follow: vocabulary, sentence length, what you never claim, how you handle numbers and links, examples of posts that are right and posts that are wrong. Without this step the output is fluent and generic.
Ideas come from wherever they already live — Notion, Airtable, a spreadsheet — with the angle, the audience and the goal for each. The system reads the plan, not your mind.
Each platform gets its own draft: length, opening line, formatting, hashtag conventions and call to action, plus a short visual brief for the designer. Threads are threads; captions are captions.
Everything stops in a queue. Your editor edits inline, approves or rejects with a reason — and the rejections are what we feed back into the rules, so the drafts get closer to publishable each month.
Approved posts go into Buffer, Later or the platform APIs at the planned times. Engagement comes back per post and per angle, so the plan is built on what performed rather than on what felt right.
We build in your stack rather than moving you onto ours. The list below is what this solution most often connects to — other systems are a scoping question, not a blocker.
They will if the style guide is thin, which is why the first week of the project is spent building it from posts you already like. Your editor still reviews everything, and every edit tightens the rules.
We use cookies for analytics — to see which pages bring enquiries. Nothing else, and nothing before you agree. Cookie Policy