When a draft should land on Medium, not your own CMS

The job is a piece you already wrote. Medium needs a title, a subtitle, a hero, tags, and a publish time. The words should not be invented again.

Teams ask for “content automation.” That usually means a new article from a keyword list. This job starts from a draft that already survived a person.

What we check before a publisher exists

Where the canonical draft lives — Google Doc, Notion, a CMS you already own. Whether Medium is a mirror or the only home. Which tags you actually use. Who may press publish. What happens to the hero image.

If you cannot point at last month’s posts and the drafts they came from, a publisher will only invent volume. We will pause.

If the drafts are real and the stall is formatting and the Medium API, a narrow automation can format, tag, and queue. A human still owns the first live send until the house style is boring.

This is not the human-review blog draft queue. That job researches, drafts, and waits for an editor before WordPress. Medium fan-out starts after the words are already approved. We will not glue them on a first call.

When we tell you to keep pasting by hand

If every post needs a different subtitle voice, or legal has to see the Medium cut, a queue will go stale faster than a person. If you have no canonical draft, fix that first.

Kuwait and GCC brands often want the same piece in English on Medium and Arabic on their own site. That is two destinations and two crops. Name both. Do not ask for “syndicate everywhere.”

AI consultancy writes the source, the tags, and the stop rule. A Medium job is a later, thinner build. We have already shipped that shape as a custom solution.

Bring two published Medium URLs and the drafts they came from. Book thirty minutes or write hello@jamilglobal.com.