Social posting on a schedule, after someone approves it
We run social as a queue. An agent workflow drafts the posts, and a person approves them before they publish. If nobody approves them, the brand will eventually say something it can't take back.
A system with an approval step
The social posting system is a Model Context Protocol server and the tooling around it. Related servers in the same kit talk to WordPress, voice synthesis, image generation, and media processing. The repository name is withheld on purpose.
Posts are drafted in the workflow a client already uses. They do not go live because a cron job felt ambitious. Approval is the product.
Which networks
The networks are the ones you already use. This page does not list a dozen logos. A connector to a social API is part of the build; the exact accounts are confirmed when the work starts. If a network has no working connector, it is not promised.
Social is also not a substitute for the site. A post disappears down a feed. A page on your domain is the thing search and answer engines can return next year. The content and YouTube service is the sibling for video channels.
Proof in the portfolio
Questions
Which platforms do you post to?
The ones your organization actually uses, where a connector exists. The posting system is an MCP server with an approval step. The network list is confirmed per engagement rather than printed as a logo wall. If a platform cannot be connected honestly, it is left out.
Who approves posts?
A person. That can be you, or Dashworth, depending on the engagement. The default design doesn't publish an unreviewed draft. The approval step is the point of the system.
The work stays with Dashworth.
Call or text 650-393-3378. We meet in Northeast Florida and San Mateo, and we take contract roles inside larger companies. No account managers, no handoffs.