Enterprise
Content at scale, without losing the voice.
The problem at scale isn't writing more. It's that every team writes a little differently, every approval takes a week, and the AI tools that would help are the ones your policy forbids. This page is what Zolt does about each of those — and, at the end, what it doesn't do yet.
Five problems a content lead actually has
Six brands, four teams, and one style guide nobody reads.
Each brand gets its own workspace with its own Brand Voice, learned from that brand's real website, documents and past content — not a tone slider someone has to remember to set. A writer on the wrong team can't drift into the wrong voice, because the voice lives with the workspace.
Approvals are where content goes to die.
A built-in approval workflow with no-login reviewer links: the person who has to sign off gets a link, reads it, approves or asks for changes. Nothing publishes until they do. No new accounts to provision, no password resets for a stakeholder who reviews twice a quarter.
Your AI policy forbids tools that train on company data.
Your content is never used to train AI models — ours or our providers’ — and it’s never sold. If policy goes further, bring your own model keys and every call runs under your own vendor agreement.
Another tool for the team to babysit.
It reads and acts on Gmail, Google Calendar, Slack and Notion directly, and exposes a production API and webhooks, so it fits the stack you already run rather than adding a tab to it.
Finance wants a number, not a meter.
Enterprise runs on contracted credits with custom limits — one agreed allowance for the term, provisioned to your account, instead of a card on file and a bill that moves month to month.
What's in the plan
Everything on Studio, without the ceilings. Every line here is read from the plan definition the product enforces — not a sales sheet.
Enterprise
What we do, and don't do yet
Said plainly, because a procurement review will ask. You get a named contact who built the product — the founders answer support, not a queue. Invoicing and purchase orders: yes. A data processing agreement: drafted with you at contract time, naming our AI subprocessors, our retention rule and our deletion process, all of which already exist. Not yet: single sign-on — accounts sign in with email or Google — and a SOC 2 report. We publish incident write-ups rather than an uptime number we couldn't yet stand behind.