Enterprise
One coworker for every team. Under your policies.
Wopie rolls out channel by channel under your identity, approval and data rules. Every action runs through the permissions your admins set, and lands in an audit log you can export.
The problem is rarely the model.
Three things stop AI getting past a pilot in a company your size. None of them are about how well it writes.
Shadow AI is already happening
Teams are pasting customer data into consumer chatbots today. No permissions, no logging, and no way to answer what left the building.
Wopie gives them a sanctioned place to delegate, where every request and every output is recorded against a named person.
Pilots do not survive security review
A tool that cannot say where data goes, who may approve what, or how access is revoked does not get past procurement.
The DPA, the sub-processor list and our security documentation are published before you ask for them.
Nobody can say what it did
Once an AI acts across live systems, “it seemed fine” stops being an answer an auditor will accept.
Every request, draft, approval, decline and action is written to a log you can read and export.
Governed from day one
Every team covered. Nothing ungoverned.
One coworker the whole company shares, acting inside the access each person already has.
Identity your admins control
SSO/SAML-ready sign-in with per-person access controls, managed centrally and revoked the moment someone leaves.
It inherits access, it never escalates
Wopie sees only the channels it is invited to and acts through the permissions each teammate already has. It can never reach further than the person who asked.
Approval policy, per channel
Your admins decide what runs and what waits for a named human. Customer sends, spend changes and deletions are held by default.
An audit trail you can export
Who asked, what it read, what it produced, who approved it and when. With retention periods you set for both the data and the log.
Start in one channel. Grow without a migration.
There is no platform project at the front of this. The first workflow is live in minutes, and the controls are identical on day one and at full scale.
- 01
Pilot one channel
One recurring job, one owner, one channel. Installed in minutes with the approval rules already on.
- 02
Expand the department
The rest of that team's recurring work, under the same permissions and the same log. No new tooling to learn.
- 03
Roll out across the org
Team by team, as each workflow proves itself. The controls do not change as the footprint grows.
Keep control
Autonomous where it's safe. Paused where it matters.
Every channel gets rules. Internal work runs on its own. Anything external, financial or irreversible waits for a human, and every decision lands in the audit trail.
Permission rules
#sales · set by adminsAudit trail
- Every decision is recorded here with who, what and when.
Each one references the last conversation and the open question, not a template. 7 follow-ups written.
Paused. These send from each owner's inbox. Each owner reviews and edits their own before anything sends.
ApproveEditEvery approval, edit and rejection is recorded with who, what and when.
- SOC 2-ready controlsControls mapped to SOC 2 criteria; audit evidence available for review.
- ISO 27001-aligned policiesSecurity policies written against the ISO 27001 control set.
- GDPR-aware data handlingData minimisation, export and deletion on request, EU-aware processing.
- DPA publishedOur data processing agreement is public at wopie.ai/legal/dpa and can be countersigned for your procurement review.
- SSO / SAML-readySingle sign-on flows ready for identity-provider setup.
- Audit trail availableEvery delegated request, output and approval is recorded.
- Built on independently audited providersAWS, Vercel, Supabase, Anthropic, Slack, Microsoft and Stripe each hold their own SOC 2 and/or ISO 27001 attestations for the layers they run. Those are theirs, not ours; Wopie's own attestation is in progress.
The answers, before you ask for them.
What your legal, security and procurement teams will want, already written down and published.
- A published DPA, countersigned on request, covering GDPR and UK GDPR with the SCCs and the UK Addendum
- A published sub-processor list, kept current as the service changes
- Security documentation plus written answers to your security questionnaire during procurement
- Customer Data is never used to train foundation models, and our model providers are contractually prohibited from training on it
- Retention periods you choose for Customer Data and the audit trail, with deletion on request
- Per-person access controls and per-channel approval rules, set and changed by your administrators
Take it to your reviewers
Everything here is published, not promised. Send your team the documents directly.
Need a questionnaire completed or the DPA countersigned? Talk to us.
Every department
One employee. Every team's recurring work.
Flick through the departments. Each one shows the ask, the tools Wopie reads, the finished output, and where a human stays in the loop.
growth Weekly report@wopie build this week's growth report from HubSpot and Stripe and post it to #leadership before standup.
Questions
Enterprise questions, answered.
Minutes to pilot one channel. Then department by department, as each workflow proves itself.