Choose Enterprise when the workflow needs governance
Enterprise is for teams where catalog work is high-volume, cross-functional, security-reviewed, procurement-led, or operationally sensitive.
The same product principle applies: pay for catalog work, not seats. The enterprise conversation scopes how much work Central should run, which outputs need governance, how review should operate, and what support model the team needs.
What gets scoped
| Scope area | What to define |
|---|---|
| Token volume | Monthly or annual volume, top-up rules, overage policy, and renewal needs. |
| Catalog shape | SKU count, variants, locales, categories, and source types. |
| Governance | Review roles, approval rules, audit needs, and field-level control. |
| Channels | Supported channels, custom feeds, hosted outputs, and active SKU bands. |
| Security and access | SSO/SAML, user management, support route, and procurement requirements. |
| Custom work | Custom AI models, integrations, support, or implementation assistance where agreed. |
Bring proof into the sales motion
Enterprise should not start with an abstract platform demo. Bring real products, current records, feed errors, PIM exports, or channel targets.
Central can show how the record changes: sources found, facts verified, claims held, review states created, and outputs generated. That proof helps scope tokens, channels, support, and governance.
Proof artifact: enterprise pilot product
| Enterprise input | Central proof | Enterprise scope signal |
|---|---|---|
| 20 representative SKUs across categories and variants. | Source trail, confidence, conflicts, held claims, enriched fields, and output previews. | Token volume, review needs, and source complexity. |
| PIM export plus channel targets. | Gap audit and channel readiness preview. | Integration, write-back, feed, and governance requirements. |
| Compliance-sensitive claims. | Claims marked verified, needs source, or hidden. | Approval rules and legal review path. |
Enterprise vs Professional
| Professional is enough when | Enterprise is right when |
|---|---|
| 20,000 monthly tokens and standard support fit. | Token volume, overage policy, or channel bands need custom terms. |
| The team can use standard access and billing. | SSO/SAML, procurement, SLA, or dedicated support are required. |
| Standard workflows cover the catalog. | Custom models, custom integrations, or governed review paths are needed. |
Bring real products to the enterprise conversation.
Central will scope token volume, governance, channels, and support around the catalog work your team actually needs.
Questions before you start
Is Enterprise required for high SKU counts?
Not always. Professional may fit some higher-volume self-serve teams. Enterprise is for custom volume, governance, security, support, or procurement needs.
Does Enterprise include SSO/SAML?
SSO/SAML is an Enterprise scope item in the active pricing model. Confirm final availability and requirements before implementation.
Can Enterprise include custom models?
Custom AI models are an Enterprise scope item. Do not imply they are automatically included without a contract.
Can we run a pilot first?
Yes. Use representative SKUs to inspect source trails, confidence, review states, and output previews before final scope.