Controlled workflow
How it works
InfoQast helps an agency operator move one selected brand brief through drafting, review, delivery, and evidence. This page separates the current open beta workflow from the roadmap.
1. Start with one real client idea
Select an isolated client brand and describe the post you need. InfoQast uses that brand’s instructions, examples, rules, and connected destinations to produce the first reviewable result. Month-long Campaign and ContentBrief planning remain roadmap work.
2. One master post, compiled for selected channels
The Copywriter produces a structured version and the compiler creates network-native variants with the relevant length and policy checks. Creative Studio can attach brand-aware template graphics or generated images. You can edit any variant; protected fragments survive recompilation.
The goal is to keep adaptation and review in one inspectable path; no time-saving outcome is claimed before customer evidence exists.
3. Your approval gate
The current release has one conservative, human-gated workflow: AI proposes, a person approves, and an operator publishes or schedules. The levels below explain the design direction; they are not a per-brand setting in the current product.
L0Suggest
Current workflow
AI drafts; a human explicitly approves, then an operator publishes now or schedules.
L1Prepare
Concept
A future option may prepare a release queue while preserving a separate human approval step.
L2Publish routine
Roadmap
Pre-approved content types go out on schedule; anything new or sensitive still stops at the gate.
L3Autopilot
Roadmap
Full-cycle publishing for a brand — an explicit opt-in, guarded by preflight checks, moderation, and a kill switch.
The client-link approval surface is restricted to the exact invited brand and variant. It should be enabled only for explicitly invited reviewers.
4. Publish via official APIs, report with real numbers
Approved variants go out on schedule through official platform APIs. The verified scope is none while platform evidence is stale. YouTube remains gated until required credentials and review are ready; other destinations follow the labelled roadmap. InfoQast records provider-confirmed results and available metrics; automatic branded client reports are not part of the current release.
Your methodology becomes an asset
Brand voices, hooks, content structures, taboos — everything your agency knows lives as skills: versioned files the agents actually use. Review them, edit them, roll them back. These instructions are reviewable and reusable today. Automatically proposing or applying learnings from a month's metrics is a later, separately governed loop.
Built for trust
Preflight checks
Every variant is validated against each network's rules and your brand policy before it can be scheduled — problems surface at the draft stage, not at publish time.
AI moderation layer
A separate compliance pass reviews content before delivery; a kill switch stops all publishing for a brand or a workspace instantly.
Audit trail
Every agent action, approval, and publish is logged. You can always answer "who did what, and why" — to yourself or to your client.
Official APIs only
We publish through each platform's official API and never automate personal profiles or work around limits. Your clients' accounts are not an experiment.
Usage is attributed per client brand so operators can inspect it. No included AI budget, overage price, Stripe checkout, or self-hosted plan is presented as available.
Developer access keeps the same boundary
MCP and CLI are separate release surfaces, but neither can bypass tenant scope, capabilities, rate limits, revocation, or audit. Both are currently in development and have independent public availability gates.
See MCP and CLI statusYour next client brief
Put the workflow in one control room.
Open Beta account creation is temporarily paused. Request an update when registration reopens.
Registration update request · No response time is promised