The challenge

An online media company ran a social channel that sent real traffic back to its site. Going quiet on it had a cost, so the drafts had to keep coming.

Full automation was never on the table. A public account that speaks for the brand with nobody reading first is a risk no marketing lead signs off on — one bad post costs more than a quiet week. The manual version had the opposite problem: writing, checking and posting all needed someone at a desk, which is the first thing that slips on a busy day.

So the question was not whether a model could draft posts. It was who says yes, and how long saying yes takes.

What we built

A publishing loop with one human gate, running in the client's own cloud account:

Drafts are prepared ahead of the morning and queued.
The queue is delivered as a message on Telegram — the chat app the team already had on their phones. No new tool, no dashboard to log into.
A person approves or discards. Approve publishes to the account; discard drops the draft.
Nothing in the queue reaches the public account without that approval.

The gate is the product. Everything before it is work the client never has to watch. Everything after it happened because a person said yes — and that is not a rule someone has to remember, it is how the system is wired. There is no code path that publishes an unapproved post.

The approval sits on a phone on purpose. A gate that requires a desk is a gate people route around; a gate that costs one tap is one they actually use.

The results

This is the smallest build in our portfolio and we are not going to dress it up. There is no volume number on this page: how much gets published is the client's editorial decision, not a property of the build.

What the build settles is the question every marketing lead asks before signing anything — who controls what goes out in our name. The answer here is a person, on every post, at the cost of one tap.

Number	What it measures
1 tap	from an approved draft to a published post
Every post	reviewed by a person before it ships
0	paths in the system that publish without approval

What you get

The publishing loop on your channels, with the approval step in the chat tool your team already uses. Process audit first, scope in writing, and 30 days of support. The same human gate runs in front of the rest of the Marketing Automation package.

Nervous about what an AI would post in your name? Start with the free AI Audit, or book a call.