Posting often enough that the page isn’t dead
Something has to go out this week, and the week after that. The gap between your last two posts is the first thing a visitor reads, so the calendar carries as much weight as any single paragraph.
On LinkedIn
LinkedIn marketing automation that posts as you, from your own profile
LinkedIn is the one network where your own posting does the work, and that is the half FounderReply automates. It drafts the post in your voice, attaches the image, and publishes it to your profile from your own OAuth-connected account. Replies on your threads are drafted too, and every one waits in the approval queue.
- Acts on the LinkedIn account you already own — connected with OAuth 2.0 (member scopes), and revocable by you without touching us.
- Finds the LinkedIn threads where you are a genuine answer, and brings the parent in with the draft so you approve a reply in context.
- Every draft lands in one queue. What leaves it unattended is whatever you set, per action, and it starts where LinkedIn’s own rules put it.
Posted
On LinkedIn
What you’re already doing on LinkedIn
None of this is the interesting part of the week. Keeping a company page alive on LinkedIn sits between support tickets and the roadmap, and it is the first thing to slip when a release runs late.
Writing something with an actual point
A platitude about hiring great people costs an hour and earns a scroll. The posts that land are specific: a number that moved, a decision you got wrong, the sentence from a customer that made you rebuild a screen.
Answering the comments it earns
A post that gets replies needs you back in the thread the same day, with an answer rather than a thank-you. That second round is where a comment turns into a conversation and a conversation turns into a call.
LinkedIn, as it looks
Every LinkedIn surface, working
The thread, the reply and the message — drawn as LinkedIn draws them, with the agent's draft arriving in each one. What you see here is what lands in your approval queue.
Published
In the composer
A post going out
The composer, the draft in your voice, the blue Post button, and the card that lands in the feed a moment later. Your agent writes the week’s post and you release it.
Replied
In the comments
An answer under your post
Someone asks a question under your post. The reply is written the same day, lands in the thread with its Like and Reply row, and the comment count moves.
Live
After it lands
Reactions, replies, impressions
Reactions stack one at a time, the thread opens underneath, and the impression count on your own post keeps climbing while you are doing something else.
The case
Why founders need to be on LinkedIn
LinkedIn is where a company’s name gets checked. A buyer opens the page before answering an email, a candidate opens it before a first call, an investor opens it after the intro. What all three find there is whatever you published last.
Your buyers are at work
The audience arrives already in work mode
B2B decision-makers open LinkedIn between meetings, on a work laptop, with a work problem in their head. A post about a migration that went badly finds people there who have had the same week. The same paragraph on a consumer feed is scrolling material.
Checked before the reply
It is the page people open before answering you
A buyer checks it before replying to your email. A candidate checks it before the first call. An investor checks it on the way to a decision. They all land on the same page, and the last thing you posted is the first thing they read.
Standing proof of life
A live page is evidence the company is real
A young company is asked to prove it exists every single week. A page with something considered on it from a few days ago answers that quietly, before anyone asks. Steady posting turns a name someone half-recognises into a company they can picture buying from.
Showing up beats spending
The feed rewards frequency
Distribution here follows consistency. A page that posts every week keeps its reach warm, and each post reaches people the previous one earned. A few months of turning up compounds into an audience that budget alone takes far longer to assemble.
Getting connected
How connecting LinkedIn works
Four steps, and the second one is the only place you do anything. The credential below is the literal artefact the connect flow uses — not a marketing paraphrase of it.
- 1
Start from the LinkedIn account you already have
FounderReply acts on the account you sign in with, under a connection you authorise yourself and can withdraw again from LinkedIn whenever you like. It never makes an account of its own.
- 2
Hand over exactly one credential — OAuth 2.0 (member scopes)
The member flow requests three scopes. Company-page posting needs organisation scopes and LinkedIn marketing-partner approval, which are not requested.
Scopes requestedlib/connectors/linkedin.ts openid profile w_member_social - 3
The agent reads before it writes
Discovery runs on that connection: it finds the LinkedIn threads where you are a genuine answer and pulls the parent in with the draft, so you are approving a reply in context rather than a sentence with no thread attached. Reading is never gated.
- 4
You set the dial, per action
Each action on LinkedIn has its own level, and you can move any of them — including past where LinkedIn’s own rules sit, once FounderReply has named the rule you are crossing and the account risk. Your setting is the one that applies, and every change is logged as yours.
Out of the box
What may run unattended on LinkedIn
One setting decides whether an action happens by itself: your own level for it, per network. Every action ships at what LinkedIn's own rules allow, and you can move any of it — including past that line, once you have been told which rule it crosses. Read from the connector's capability flags and lib/autonomy.ts at render time.
| You start at | LinkedIn’s own rules | |
|---|---|---|
| Publish your own postOriginal content from your connected account | Waits for your approval | Runs automatically |
| Reply on your own postsAnswering comments left on your content | Waits for your approval | Waits for your approval |
LinkedIn’s Professional Community Policies forbid software that automates activity. Publishing your own posts starts unattended; replies on your own threads start held for a human, so a person signs off on everything that lands in somebody else’s notifications.
The room
Where B2B buying conversations are visible
LinkedIn is the one network where a professional identity, a company and a buying role sit on the same profile, which is why B2B founders keep returning to it. The distribution that works there is your own posting, consistently, from an account people recognise — the part this connector automates.
LinkedIn’s Professional Community Policies forbid software that automates activity — automated commenting and automated outreach in particular. That is why publishing your own content is the capability that starts unattended here, and why the engagement-automation tools in this category live outside the rules.
What good participation looks like on LinkedIn
- Publish your own content; do not automate engagement on anyone else’s.
- Treat automated connection requests and InMail sequences as out of bounds — that is exactly what the policy names.
- Post on a cadence you can hold. LinkedIn rewards the account that shows up weekly over the one that arrives in bursts.
- Keep the account human. LinkedIn restricts accounts for automation patterns, not for content.
The gate
On LinkedIn, you are the one who decides.
LinkedIn is reached with OAuth 2.0 (member scopes), on the account you connected. The agent reads freely, drafts in your voice, and stops at your queue — and whether a given action keeps stopping is a dial you own, per action.
- Acts on the LinkedIn account you connected, under a credential you can withdraw from LinkedIn’s own settings.
- Shows you the thread a draft answers, before you approve it.
- Starts every action where LinkedIn’s own rules put it.
- Names the rule you are crossing, and the account risk, before it saves a looser dial — and records the change as yours.
FAQ
LinkedIn, answered plainly
Yours. You authorise FounderReply from your own LinkedIn account over OAuth, and every post and reply goes out under your name. There is no managed profile and no shared identity. Withdraw the permission in LinkedIn’s settings and the agent loses access immediately.
Text posts and posts with an image, published to your own profile through the Posts API under the w_member_social scope. Each draft is written from your product context in the voice the account already uses, and it waits in the approval queue until you release it.
A finished post, in your voice, with its image attached — or, for a reply, the comment it answers shown above it. You edit it in place or release it as written. Nothing reaches LinkedIn until you do, and the schedule is yours to set.
By keeping a person in the loop where the policy asks for one. Your own publishing runs on the cadence you set, replies wait for approval, and FounderReply names the Professional Community Policy rule you are crossing before it saves a change to either default.
Keep reading
X automationWhat the agent does on XRead Reddit automationWhat the agent does on RedditRead Facebook automationWhat the agent does on FacebookRead Social media automation complianceGuide — the platform rules behind the defaultsRead The social agentDiscovery, drafting and the approval queue in one placeRead All supported networksEvery network the agent works, and what it does on eachRead
Ready when you are
Connect LinkedIn and read the first drafts.
The free plan connects one account, and nothing is published to LinkedIn until you release it.
Free to start · Approval on by default · No card required