When one social update has to reach many accounts

The job is fan-out. One approved brief has to land on several accounts a company already owns, each with its own crop, caption length, and login.

Teams ask for “social media automation.” That is not a job. The job has a source post, a list of destinations, and a person who is still responsible when one account goes out of brand.

What we check on a consultancy call

How many accounts are actually in scope this month, and who owns each password. Whether you will only publish through official connectors. What must change per surface — Arabic vs English, a different crop, a link the other grid cannot use. Who is allowed to stop one account without stopping the rest.

If you cannot name the source of truth for the week — a folder, a Notion row, a WhatsApp approval — a scheduler will publish yesterday’s guess.

If the brief is already written and the stall is hours of logging in, a one-to-many pipeline can be enough. The custom solutions work includes this shape: one input, many accounts, format per channel. We will not treat one desk’s account count as a target for yours.

This is not the Instagram generate-caption-post loop. That job creates the asset. Fan-out assumes the asset already exists. We will not collapse them on a first call.

What we will not recommend yet

We will not start with an agent that comments, DMs, and follows on every handle. That is a different job, and a policy risk. We will not wire unofficial posters to dodge a platform API. If the platform closes that door, you own the outage.

If a person still rewrites every caption, keep them in the loop and automate only resize and schedule. If the accounts are real and the brief is one object, we scope approve → adapt → publish through official connectors. That is AI consultancy first, then a narrow automation if the fan-out is mechanical.

Bring the list of handles and last week’s one brief that had to go everywhere. Book a consult or email hello@jamilglobal.com.