The AI CMO

Enterprise

One operation across every brand and market you own.

On a warehouse that is yours alone, with a record your auditors can read.

On The AI CMO, acquisition, retention and customer support run as one operation – planned, produced, sent, answered and proven on your own data. Enterprise adds what a large operator needs before the first send: a dedicated data warehouse, roles enforced in the API, volumes written into the contract, a named success manager, and a security review your team can vet. A plan for your whole market and a journey for every customer, through one approval queue.

M

Meridian Group · Enterprise

Live

2,418,304,112

Events · dedicated warehouse

6 brands

Own voice, data, senders

31 live

Campaigns in market

Shipped · this week

Q3 growth plan drafted for review · Meridian Home

✓

14 lifecycle emails shipped · Meridian Travel

✓

Paid search restructured – CPA −18% · Meridian Home

✓

Churn-risk segment refreshed · 1,204 people · Meridian Finance

✓

Creative variants for spring campaign · Meridian Travel

✓

Your team approves. The system ships. The warehouse keeps score.

1:1

a journey for every customer

each one moved by what they did, through one approval queue

Millions

of events a month on your own cluster

the warehouse is sized to the contract, not a plan tier

Unlimited

brands and seats

every brand in its own lane, every seat in its own role

99.9%

uptime, backed by SLA credits

the SLA is public – read it before you sign

Several brands, one operation

Multi-brand marketing on one operation.

Multi-brand marketing asks for two things that usually pull against each other: each brand kept apart (its voice, its customers, its senders, its rules) and one team that can see and work all of them. On The AI CMO the brands belong to the organization and people hold roles against them, so both hold at once, in every market you run.

01

Each brand in its own lane

Its own voice, customer records, lifecycle stages, verified senders and do-not-contact lists. Messaging, personalization and automation always work from one brand's data.

02

One team across all of them

Owners, admins and managers see every brand; everyone else sees the brands they are given, enforced at the database and in the API. Support and Data seats stay confined to their desk.

03

A play proven once, used again

A journey copies to another brand as an unpublished draft, with the brand-specific choices marked for setup. Blacklists copy across brands, and a verified sending identity can be shared rather than set up twice.

04

Every conversation, every brand, one queue

The Helpdesk opens on All brands: one queue across them, each conversation naming its brand, with that brand's canned replies, knowledge and reply address.

05

Budgets and usage per brand

An admin sets each brand's credit budget, and the admin portal shows usage by seat and by brand: what each brand spent, and who spent it.

06

One customer across brands, only with your say-so

By default each brand keeps its own books. Where your brands belong to one legal entity, an owner or admin can turn on a cross-brand view of a customer – a view, never a merge.

Security and governance

The answers your security review asks for, before the demo.

The AI CMO is built and operated by ROGA AI LIMITED. SOC 2 Type II and GDPR programs are underway with Comp AI. Live status, policies and controls are in the Trust Center, so nothing on this page can drift from what the auditor sees.

01

Roles enforced in the API

Owner, Admin, Manager, Member and Viewer, plus confined seats for Support and Data that see nothing else. Each seat sees exactly its job, in the product and in the API alike.

02

Tenant isolation at the database

Row-level security on every table. Each organization's data is scoped to it, and each brand's data to that brand – in the product and in the warehouse.

03

A dedicated warehouse

Your own cluster when scale or isolation demands it. Assignment follows your organization; nothing re-points.

04

Encryption and sessions

AES-256 at rest, TLS 1.2+ in transit. Multi-factor authentication on our own admin surfaces, and the check fails closed, never open.

05

Keys that expire

Ingestion keys rotate, expire and pin to IP ranges. Model and connection credentials never leave the server.

06

Suppression in the send path

Unsubscribes, STOP replies, the blacklist and self-exclusion are enforced where the send happens. If the list cannot be read, the send does not go.

07

An append-only record

Every action, its actor, the trust level it ran at and the policy it passed. Entries cannot be edited or removed, including by an owner. Your auditors can read it.

08

The paper

MSA, a standard Article 28 DPA with enterprise options, the sub-processor list and a public SLA. No customer data is used to train models.

The contract

Volumes written in, not looked up.

An enterprise account is provisioned by hand to the contract. Volumes, seats and term are set by your account manager, never by a card on file, and the usage meters your team sees show the contract's numbers.

Warehouse events per month on a dedicated cluster, sized to your volume

Behavioral web events from the Website SDK at contract volume

Email, SMS and WhatsApp volume from your own domains and senders

AI credits allocated to the contract, with per-brand budgets you set

Unlimited brands and seats

A named success manager and an executive sponsor who know your account

99.9% uptime, backed by SLA credits

Support hours and concierge data feeds where the contract says so

MSA, DPA and procurement support

Custom integrations and onboarding built around your systems

Roadmap requests that move to the front of the line

Adoption

Who ran what, per seat and per brand.

The question after month one is whether the platform is used. The admin portal answers it: net credits per brand against its budget, who spent the organization's credits and when they last did, which door the credits went through, and every charge and refund newest first – the view finance asks for. Under it, the ledger holds every action a specialist or a person took, with the trust level it ran at.

SeatActionsCredits
Anna M.2141,180
Retention specialist1,3062,940
Tomáš R.380
Support desk9260

Net credits per brand · this month

Meridian Home3,120 of 5,000
Meridian Travel1,840 of 3,000
Meridian Finance610 of 2,000

Proof

Why they chose The AI CMO.

The business case

“Choosing The AI CMO represents an important step in building a marketing operation that can scale across our online and land-based businesses. Its unified approach will allow us to coordinate acquisition and retention across brands and markets, increase the leverage of our teams, and measure impact against incremental margin.”

Vojtěch Krňoul

Director of Online Casino · NET and GAMES

The technology case

“After spending enough time in this industry, you eventually start to think you’ve seen it all. You know your field, you understand how things work, and it becomes increasingly difficult for something to genuinely surprise you. And then The AI CMO comes along. Their platform somehow makes you feel like Alice in Wonderland all over again. Not because it simply does more than the tools you already know, but because it feels like it’s playing an entirely different game.

What gives The AI CMO such a remarkable head start is that it was built from the ground up with AI, specifically for AI agents to use. AI isn’t an extra layer added to an existing marketing platform – it’s the foundation. The result is a breathtaking all-in-one tool combined with an actual AI execution team: specialized agents with access to an incredible amount of information, using the platform to make decisions and execute at scale.

And then there’s the speed at which it keeps evolving. The platform is expanding so rapidly that it’s almost difficult to comprehend – at a pace most companies can only dream about. Not only has The AI CMO caught up with the established leaders in the market, they’re already pulling away from them.”

Jan Matějíček

Head of Marketing Technology · NET and GAMES

The first weeks

From the first conversation to the first approved plan.

01

The conversation

Brands, markets, volumes, and the systems your data lives in today.

02

The paper

MSA, DPA, and the volumes and term written into the order form. Your success manager is named.

03

Provisioning

The organization, its warehouse and its limits are set to the contract on the day it is signed. Your people are invited under their roles.

04

Data and sending

Feeds connected by push, pull, files or the SDK, including a table in your own database. Sending domains verified.

05

The first plan

Approve it, the week runs, and every action lands in the ledger.

Pricing

From $80,000 a year, on a contract.

A twelve-month agreement, priced by the volumes the contract carries: warehouse and web events, messages, AI credits, support hours and dedicated infrastructure. Brands and seats are never a line item. The Manager plan, for a single brand, stays on the pricing page for teams that do not need a contract.

What sets the price

Event volume

warehouse events and web events per month

Message volume

email, SMS and WhatsApp per month

AI credits

the monthly allocation, budgeted per brand

Infrastructure and support

a dedicated cluster, support hours, concierge feeds

Start operating at your scale.

Tell us the brands, the markets and the volumes, and we will walk you through the operation on a demo built around them.

Enterprise runs on a dedicated warehouse, with a ledger your auditors can read.