A data model for every line of business.
Not a template gallery. Each Vertical Data Model brings its own objects, screens and AI surfaces, and activates on the same marketing OS in one row. 46 are catalogued today. The ambition is one for every line of business — and the reason that is achievable is below.
Where each one stands, plainly.
A suite is production when it has been through the full build and audit cycle. Beta means the objects and screens are real but the audit is not done. Building means it runs on the whole marketing OS today while its industry layer is written.
Production
Built out and in use by named customers.Beta
Real objects and screens; not yet through the full audit.Building
Runs on the full marketing OS today; the industry layer is being built.The cost of the next vertical is bounded. That is the whole claim.
A VDM is five things. Everything underneath — identity, permissions, isolation, residency, quota, audit, the send pipeline, the AI credential resolver — is inherited, not rebuilt. The team that built the Healthcare suite never wrote a permission check.
Domain objects
Real tables with their own columns, indexes and relations — a patient, an insurance authorisation, a listing, a showing. Not custom fields on a contact.
Endpoints
The suite’s own API surface, registered like any other route — behind the same identity gate, the same permission resolver, the same brand-scoped client.
A command center
A full working surface, not a filtered view of the generic one. A clinic and a brokerage do not work the same way, so they do not get the same screen.
Paro surfaces
The points in that workflow where an industry judgement is made — drafting a recall protocol, matching a buyer to a listing — running on your own AI key.
An activation record
One row. A brand turns the suite on, and the data layer refuses writes to its objects until it does. Turning a vertical on is a row, not a release.
One generic object model with industry content painted on. Adding an industry is a content exercise — it never gets deeper than the fields everyone already had.
Genuine depth, but each industry is a separate product with its own team, its own contract and its own price. Depth bought by multiplying the product line.
One operating system, models added to it. Depth without a second product — which is why the catalogue can keep growing rather than forking.
A suite still being written is not an empty product.
Every brand gets the full marketing OS the day it signs up, whichever vertical it runs. That is why a suite on the roadmap is still worth activating — and why the industry layer, when it lands, lands on something already working.
See every industry →- CRM — contacts, companies, deals, pipelines
- Campaigns — email and SMS, templates, A/B testing, sequences
- Journeys, landing pages, forms and scheduling
- Analytics across account, enterprise, brand and workspace
- Identity — SSO, SCIM provisioning, scoped access policies
- Isolation, residency, quota and a tamper-evident audit trail
The rest of the library, already scoped.
These are not a wish list — they are the lines of business named in the product's own roadmap, grouped by the domain whose core objects they build on. Order is driven by what customers ask for, which is why the form below matters.
Your line of business isn’t listed?
Tell us which objects your work actually revolves around — the thing you would be annoyed to store as a contact with extra fields. That description is what a VDM gets built from, and what moves a line of business up the order.
You can start on the full marketing OS today either way.