Startup growth agent

LinkedIn posting

Writes and publishes a LinkedIn post from the day’s growth topic.

Running since Jun 20, 2026·LinkedIn·Risk: Medium

What this solves

Posting on LinkedIn consistently is the first thing to slip when there is no one dedicated to marketing. Gaps of a week or more make a company page look abandoned right when buyers are checking it.

Who it’s for: Early-stage founders and small teams who want a steady LinkedIn presence without a standing content calendar meeting.

How we use it: This is the first growth agent we built, and it has been posting to our own company page since June 2026 — it works from a fixed topic calendar rather than improvising each day, so the voice stays consistent.

How it works

What happens on every run.

Reads a shared topic calendar and takes the next topic marked pending.
Writes a single post from that topic: a hook as the first line, no links, no dashes, a short conversational body, and two to four hashtags — no call-to-action pitch at the end.
Checks that a browser is already logged into LinkedIn on a dedicated profile.
Opens the composer, types the post, and publishes it as the company page.
Marks the topic posted in the calendar, so the next run picks the one after it.

Skills and scripts

What it’s built from.

A Claude Code workflow (markdown instructions) plus a browser-automation script. Not packaged for public download yet — the setup guide below describes what it does; the managed tier runs it for you today.

Setup guide

Running it yourself.

Runtime

An agent runner that can follow a written workflow and drive a browser — we use Claude Code.
Node.js, for the browser-automation tooling.

Browser setup

A dedicated Chrome profile, separate from your everyday browsing, kept logged into LinkedIn.
Chrome launched with remote debugging enabled on a fixed port, so the agent can attach to the already-logged-in session instead of automating a fresh login (which is what trips LinkedIn’s bot detection).

Account setup

A LinkedIn account authorized to post as your company page.
No API access needed — the agent posts the same way a person would, through the composer.

Configuration

A topic calendar: a simple list of topics and angles, each marked pending or posted.
A short brand-voice brief — audience, tone, the handful of things never to say.
A daily or weekly posting cadence, and the active hours it is allowed to run in.

First run

Run it once with one topic and review the drafted post before it publishes.
Confirm the post appears on the company page, and that the topic calendar updated.

Common questions

LinkedIn logged me out between runs — what now?

Log back into LinkedIn in that same Chrome profile by hand; nothing else needs to change.

LinkedIn showed a captcha or a verification check.

Solve it once in the browser window yourself. This is why the agent runs at a human pace with daily caps rather than back-to-back — frequent challenges usually mean the posting rate is too aggressive.

LinkedIn changed its composer and the script stopped finding the right button.

The automation targets specific page elements, so a LinkedIn redesign can break it. Expect occasional maintenance; this is the most common failure mode for any browser-driven agent.

Risk notice

What to watch for.

LinkedIn’s terms do not permit automation. We keep a daily cap, randomized timing within active hours, and default to reviewing drafts before they post.
A platform redesign can silently break the script — we treat a missed run as a signal to check it, not just retry.

Run it

Do it yourself, or have us run it.

Have us run it Questions about setting it up yourself

Run log for this agent: coming soon