Multi-agent environment

Four agents run your LinkedIn.
You just approve.

LinAgent sets the direction, finds the topics, writes the posts and schedules them. Finished drafts land in a queue and wait for your call — nothing publishes on its own.

4
agents in a single run
0
posts published without your approval
1 click
from one run to a queue you can review
Awaiting approval 1 of 3 in queue Tue 11:30
TM
Your brand
company page · LinkedIn

We cut order fulfilment from 48 hours to 12. We did not buy a new system. We changed three things: picking starts before the payment clears, the courier gets one pickup window a day, and the warehouse is arranged by turnover rather than by category. The hardest part was convincing the team that fewer steps does not mean less control. #logistics #ecommerce #operations

Pillar: Case studies generated with Gemini
✓ Approve ✕ Reject ↑ Publish “Publish” unlocks once the post is approved

How it works

One run, four agents, one decision at the end

You start a run in the panel. The agents work in sequence, each handing its output to the next. What comes out is not a publication — it is a queue of finished posts for you to review.

01

Strategist

Sets the brand positioning and the content pillars — what is actually worth talking about on LinkedIn.

→ direction and pillars
02

Researcher

Finds the topics: customer questions, observations from the market and the threads with traction that week.

→ a list of topics
03

Writer

Writes the posts with Gemini — against a specific pillar, with a strong opening line and a call to action.

→ finished copy
04

Planner

Builds the schedule: assigns publication slots and orders the queue so the pillars alternate.

→ a scheduled queue
The last step belongs to a person. Every post waits in the queue marked “pending”, and you approve, reject or publish.

Agents

Each one has a single job and does it well

The panel shows every agent's status live — who is working and who has finished. The log records exactly what each one did and why.

Agent 01 idle

Strategist

Keeps the communication pointing in one direction instead of becoming a pile of unrelated posts.

Produces: brand positioning, target audience, tone of voice and content pillars.
Agent 02 idle

Researcher

Turns “I have no idea what to post about” into a concrete list of topics for the coming weeks.

Produces: topics mapped to pillars, each with a reason it should land.
Agent 03 idle

Writer

Writes finished posts, not drafts you have to rewrite. Substance, length and rhythm built for LinkedIn.

Produces: posts generated with Gemini, complete with hook, body and hashtags.
Agent 04 idle

Planner

Keeps the cadence steady and stops the brand saying the same thing three times in a row.

Produces: a schedule, publication slots and an ordered queue ready for approval.

What you get

Your LinkedIn presence stops depending on a free evening

A steady presence without writing every day

A single run produces several days' worth of posts. You do not disappear from LinkedIn in the week everyone is buried, because the content is already written and waiting in the queue.

Content that matches the brand strategy

Every post is written against a pillar the Strategistist has set. Instead of scattered updates you get communication that adds up to a coherent picture of the company.

Full control over what goes out

You read, approve or reject — post by post. Rejected ones can go back into the queue. Nothing leaves the panel without your decision.

Content generated with Gemini

The Writer works through the Gemini model using the brand context and the chosen pillar. You supply your own API key; without one the panel runs in demo mode.

The approval gate

No post reaches LinkedIn without approval

This is not a setting that can be switched off by accident — it is how the panel works. The agents prepare the content, but publishing is a human decision and takes a deliberate click.

A new post enters the queue marked “pending” — never as published.
The “Publish” button stays disabled until the post has been approved.
A post can be rejected and later restored to the queue if you change your mind.
Every decision and every agent step is recorded in the live log.