Your team's next two weeks, proposed from what you already publish.

Give it the link where your team publishes and it reads your recent pieces, counts how often and on which days you publish, and proposes two weeks of pieces that build on your own work, each waiting on its day for one tap. The open days light up. Pitches from the board, from Cue's chat or from a Slack channel land on their days too, a pitch made twice folds into one, and nothing goes on the calendar until the approver says so.

What it does

• Read what you already publish and count your rhythm: how often, and on which days.
• Propose a piece for each usual day in the next two weeks, built on your own work.
• Put every pitch on the day it names, folding a pitch made twice into one.

What you get

• Your next two weeks on one calendar, with the open days lit.
• Every piece traced to the message or the published piece behind it.
• Approved pieces for your own X or LinkedIn posted from your chat at their time.

What it needs

• The link where your team publishes
• Pitches from the board, the chat or a Slack channel
• Your time zone

Proposes at install, again every Monday for the days still open, and at once when a pitch arrives.

Nothing goes on the calendar until the approver approves it, with one tap.

Who runs it

Cue works in one private chat with you, because reading your Slack and posting with your own X or LinkedIn connection only happen in a chat you are in. Your team works on the board.

• One chat, one calendar: The board link, a channel import, your pitches and every post going out run through the chat. Your team pitches and sees the two weeks on the board.
• A person approves every piece: Suggestions and pitches land dashed on their days and wait on the approver. Cue never approves, and posts only the words you put on a piece.

What stays yours

• Built from your own work: Each suggestion says which of your published pieces it builds on, quoted with its date, and why. Nothing is connected to start.
• Your rhythm, counted: How many pieces a week and on which days is counted in code from the dates you published, so the open days are real gaps, not guesses.

Questions

Do I need Slack or anything else connected?

No. The calendar starts from the link where you publish. A Slack channel is optional: Cue reads its last 30 days once in your chat, read only, and pitches kept anywhere else can be pasted there.

Does the app post for me?

No. The app plans. Cue posts approved pieces for your own X or LinkedIn from your chat at their time, with the words you set, and asks you there to allow posting the first time. Anything else is marked posted by whoever posted it.

Who can approve?

The person who set it up, unless you name others. Anyone in the workspace can pitch on the board.

See your next two weeks before they arrive.

Install it, give it the link where you publish, and watch two weeks of pieces land on their days in under a minute.

Browse all Bolter blueprints