Ship the post you keep postponing.
Cedric drafts LinkedIn posts in your voice, for your profile or the company page, and publishes only what you approve, exactly as you approved it.
100K credits ($50) on sign up. No card needed.
- The company shipped something worth saying; the post about it died in a drafts folder. That gap is the whole problem.
- Cedric drafts LinkedIn posts from real material: the release, the changelog entry, the thing the team just did.
- Every format the platform takes: text, link, image, video, and document posts.
- Personal profile or company page, whichever the post belongs to.
- Publishing waits for a yes, always. What goes live is your approved words, not an approximation.
What can a LinkedIn AI assistant do?
Companies do not lack things to say on LinkedIn; they lack the half hour between the thing happening and someone writing it up. A LinkedIn AI assistant closes that half hour. Point Cedric at the material, a release, a milestone, a lesson the team just paid for, and he drafts the post: the hook, the substance, the link, in the voice your page actually writes in.
Format is not a constraint. Text, link, image, video, and document posts are all in reach, to a personal profile or the company page, so the one-page overview can ship as a document post and the launch can carry its screenshot. What an AI employee adds over a scheduling tool is the drafting itself: the post exists because the work happened, not because a content calendar demanded filler.
And he publishes nothing on his own. Every post is held for approval and goes out word for word as approved. The cadence gets easier; the voice stays yours.
The launch post
From changelog to feed, one approval.
Sam Okonkwo9:14 AM
@Cedric draft a LinkedIn post for the company page announcing the reporting feature, from the changelog entry.
CedricAPP9:15 AM
Draft ready. It opens on the problem (the Friday report eating an afternoon), gives three lines on what shipped, and closes with the docs link. If you would rather lead with the visual, I can shape it as a document post carrying the one-page overview instead. Held for approval either way.
Every format
Text, link, image, video, and document posts, matched to what the material deserves.
Profile or page
The founder's profile and the company page are both in reach; each post goes where it belongs.
Held for a yes
Published only on approval, exactly as approved. The feed never hears a voice you did not sign.
Connect LinkedIn in a minute
No setup project, no workflow builder, no field mapping. The flow is the same for every tool Cedric connects to.
- 01
Install Cedric where your team talks
One click. He joins your Slack like any other member, and everyone shares the same Cedric.
- 02
Connect LinkedIn from the dashboard
Open the Integrations page, pick LinkedIn and sign in on its own sign-in screen. Cedric never sees or stores your password, and you can revoke the connection in one click at any time.
Pick Read-only when you connect if you only want him reading. You can switch it later.
- 03
Ask in plain words
Back in the channel, try it: "draft a company-page post about this week's release." You describe the outcome; Cedric picks the LinkedIn actions the ask needs. There is nothing to configure.
Connect for the whole workspace so the team shares it, or keep the connection personal. Two accounts are fine too; each gets a short name.
- 04
Let it become routine
Schedule the recurring version of the ask, and let Cedric fold LinkedIn into bigger jobs that cross your other tools. Anything that would leave your workspace still comes back as a preview to approve first.
Better in company
A launch is one story told three ways: the LinkedIn post, the Facebook and Instagram version, and the Mailchimp send to the people who asked to hear from you. Cedric drafts all three from the same brief, and each waits for its own approval.
Write the announcement once, in the channel, and let the formats fan out from there.
Worth knowing
The connection is for posts. Cedric drafts a post for a profile or a company page and publishes it on your yes, in your words. Connection requests and direct messages stay with you.
The LinkedIn connection sets the scope. Cedric sees what it grants. Access is logged, and you can revoke it from the dashboard at any time.
Nothing sends itself. An email, a post, a change to a record: anything with consequences comes back as a preview for a person to approve.
FAQ
Yes, natively. LinkedIn is one of the apps Cedric knows deeply, with a built-in playbook: connect it once from the dashboard and ask in plain words, with no workflow to build and no fields to map. It sits alongside 3,200+ other connectable apps.
Both. Connect what the post needs: founders often connect a profile for their own posts while marketing runs the page, and each connection stays scoped to its owner's choice.
They converge on you fast, because your edits stick. Cedric learns from what you change before approving, and the workspace remembers, so the fifth draft needs less surgery than the first.
Yes: a standing job can draft the weekly post from what actually shipped and hold it for approval. The routine is automated; the yes never is.
Connect it for the whole workspace and everyone shares it, with one person authorising once. A connection you would rather not share, a personal inbox for instance, can stay personal to you.
Yes. Pick Read-only when you connect, or switch it later on the Integrations page. With write access, anything that changes or sends still waits for an approval.
Every workspace starts with 100,000 free credits (worth $50) on sign-up, no card. Plans start at $19 a month for the whole team, no seats. Each task uses credits in proportion to the work. See pricing.
Give the page a pulse.
Install Cedric, connect LinkedIn, and approve the post about the thing you just shipped.
100K credits ($50) on sign up. No card needed.