Write once. Shape it for each channel.
Start a post from a brief, add a version for every connected account, attach media from your library, and run the platform checks. Then send it for approval, schedule it, or publish when allowed.
LinkedIn
X
Medium
Dev.toThree steps.
Draft
Give the post a title and a brief. It is saved as a draft for your organisation.
Add versions
Pick an account and write the version for that platform, with media attached.
Validate & submit
Run the checks, then send for approval and set a time.
What you get.
From the Reach dashboard, as it works today.
Per-account versions
Each connected account gets its own text and media instead of one post forced everywhere.
Eight providers in the picker
X, LinkedIn, Dev.to, Hashnode, Medium, YouTube, Newsletter and Discord.
Media from the library
Attach images and video you already uploaded; nothing is uploaded twice.
Platform checks
Validation returns a real verdict for each version before anything is queued.
Schedule or now
Pick a time, or leave it blank to publish as soon as the approval allows.
Approval enforced
Publishing before approval is refused by the server, not just hidden in the interface.
Accounts you can publish to.
ConnectedConnected and proven on staging. Publishing is checked separately from analytics, which waits on a LinkedIn permission.
In the composerIn the Composer provider list. Posts and threads.
In the composerIn the Composer provider list. Video uploads with title and description.
In the composerIn the Composer provider list. Long-form articles.
In the composerIn the Composer provider list. Developer articles.
In the composerIn the Composer provider list. Developer blog posts.
In the composerIn the Composer provider list. Announcements to a server channel.
In the composerIn the Composer provider list. Email editions.
The other screens.
Your channels, on one calendar.
AI drafts. A person approves. Reach publishes on time and keeps the record.