Marketing operations for regulated teams
Publish across every channel. Nothing goes live without approval.
Write LinkedIn posts, WhatsApp statuses and website banners in one place. Every word is checked against your rules as you type, signed off by a named compliance officer, and watched after it goes live.
Nothing you write is published until a compliance officer approves it.
- gates between a draft and the live post
- 4gates between a draft and the live post
- named approver for each exact version
- 1named approver for each exact version
- starter compliance rules, editable by your officers
- 12starter compliance rules, editable by your officers
- days of live watch after every post goes out
- 30days of live watch after every post goes out
Where risk gets in
The risky post is rarely the one you checked. It is the one that changed after you did.
- 01
A banned phrase slips into a caption
The checker underlines it under the exact words as they are typed, and submit stays locked until it is gone.
- 02
The disclaimer gets cut to save space
Required disclaimers are enforced per channel. Adding one takes a single click.
- 03
Someone edits the copy after sign off
An approval covers one exact version. Change a word and it goes back for review.
- 04
The live post is changed on the platform
Live watch rereads it for 30 days and alerts compliance the moment it stops matching.
Compliance should read every word before your customers do. Now it reads them as you type.
How it works
Three steps, and a record of every one.
- 1
Write with the checker beside you
Start from a brief, a channel template or a blank page. Prohibited phrases and missing disclaimers are flagged while you type, not after you submit.
- 2
A named officer approves one version
Your compliance officer approves or sends it back with a reason. The approval records who and which version, and nobody approves their own work.
- 3
Publish, then keep watching
Connected channels publish on schedule; the rest get a guided copy and post flow. Every live post is reread for 30 days.
Safeguards
Built for the day an auditor asks.
Every safeguard is enforced on the server and covered by automated tests, so it holds whoever is clicking.
Rules that apply the moment they change
Add a phrase today and anything already scheduled with it is stopped at publish time, with the reason logged.
An audit trail a regulator can read
Every action with who, when, and the before and after state. Append only inside MySQL, exported to CSV in one click.
AI drafting inside the same rules
Groq drafts from a brief and suggests fixes. Its output is checked exactly like yours, and it never approves anything.
Roles that keep everyone honest
Creators draft, officers approve, publishers publish, admins manage people. The rules are enforced on the server, not just hidden in the interface.
Accounts that protect themselves
Five wrong passwords lock an account. A password change ends every older session. Channel tokens are stored encrypted.
A watch that keeps going after you publish
The live post is reread every six hours for 30 days. If it is edited or removed on the platform, compliance hears about it once, with the exact difference.
Channels
Automatic where platforms allow it. Guided where they don't.
LinkedIn
Publishes automatically once an admin connects an account. Posting as your company Page needs LinkedIn's approval, which the console is ready for.
Website
Publishes approved banners, heroes and promo blocks through your CMS, never raw HTML. The live page is watched afterwards.
WhatsApp
WhatsApp does not allow posting to Status through its API, so the console prepares the caption and media and records who posted it.
Questions
What compliance teams ask first.
Can anything go live without approval?
No. At the moment of publishing the console checks the status, the named approver, that the approved version is the current one, and every rule as it stands today. If any check fails, nothing goes out and the reason is logged.
What happens if our rules change after something is scheduled?
It is checked again when it is due. If it now breaks a rule, it is blocked, sent back to its author, and the reason goes into the audit log.
Does the AI ever approve content?
No. AI drafts from a brief and can suggest fixes for flagged text. Only a compliance officer can approve, and never their own content.
Can we post to LinkedIn automatically?
Yes, to a connected personal profile today. Posting as your company Page switches on as soon as LinkedIn approves your app for company posting.
Why is WhatsApp Status posted by hand?
The WhatsApp Business Platform has no way to post to Status. The console prepares everything, and the publisher confirms once it is live.
Where is our data kept?
In your own MySQL database. Passwords are hashed, channel tokens are encrypted, and the audit log rejects any edit or deletion at the database level.
What can we hand to an auditor?
A CSV export of every action: who did it, when, and the state before and after. Each approval names the officer and the exact version they approved.
Ready when your next campaign is.
Sign in with your work account. If you do not have one yet, your admin can add you in a minute.
Sign in to the consoleNothing you write is published until a compliance officer approves it.