Campaigns that take five answers, not five meetings.
This is the sharp edge of the stack and it's live in the product today. Your team answers five questions from a phone. The platform does the writing, formatting, scheduling, publishing, and reporting.
You own the brand rules, the proof library every claim is drawn from, the calendar, and the performance record — across every channel.
- Native drafts per channel
- Cited claims and risk scoring
- Scheduled and published for you
Social Campaigns, step by step.
- 01
Answer the five questions
Who's involved, what content you have, when it should run, where it should go, why you're doing it. Dictate it if typing is slow.
- 02
AI drafts per channel
Hook, caption, CTA, and hashtags written natively for each platform from your workspace facts — not one post copy-pasted five times.
- 03
Review with receipts
Every draft carries a risk read and footnoted claims. Regenerate a single channel or edit hook, caption, and CTA in place.
- 04
It runs itself
Approved work publishes on the schedule you set through your connected channels, then reports back per campaign and per channel.
In the engagement.
- The five-question Create Campaign launcher
- Per-channel AI drafting and regeneration
- Proof library with cited claims
- Risk scoring and approval lanes
- Scheduling and live publishing
- Per-channel performance reporting
Every claim traces back to proof.
Each workspace keeps a proof library. Whatever this pillar produces — a page, a post, an email, a report — can only reference verified facts, and claims are footnoted so reviewers see the source before anything ships. We fight boring content; we don't invent statistics.
Pillars that make this one stronger.
Each pillar works alone. Together they close a loop no rented platform can.
Social Campaigns questions.
- Is this actually built, or a roadmap?
- It's live. The launcher, AI drafting, approvals, scheduling, and performance all run in the product today.
- What does my field team have to learn?
- Two steps. Contributors answer Who and What and submit; everything else is handled by admins and the engine.