Upgrade Plan

Changing plans involves aligning subscriptions with rollout stage and desired outcomes. This page explains when upgrading or adjusting plans makes sense, what to expect, and how to think about the trade‑offs.

When to Change Plans

Consider a plan change when one or more of these signals appear:

Adding more screens or new locations and higher limits are needed.
The team needs features not available on the current tier (for example, advanced integrations, API usage, or governance controls).
Support expectations have grown (response time, dedicated guidance).
Budgeting or procurement requirements shift (centralized invoicing, ACH/wire, vendor onboarding).

Choosing the Right Fit

Use priorities to guide the choice rather than feature checklists:

Priority	What to consider	Typical tier
Scale	Device count, content bandwidth, storage headroom	Standard → Premium
Integrations	API usage, webhooks, SSO, advanced workflows	Premium
Governance	Roles/permissions, auditability, compliance needs	Premium → Enterprise
Support	Response times, onboarding help, program design	Premium → Enterprise

What to Expect

Upgrades: Generally take effect immediately and unlock features right away. Billing is commonly prorated for the time remaining in the current term.
Downgrades: Typically scheduled for the next renewal to avoid disruptions. Device counts, storage, and integrations must align with lower‑tier limits before the change.
Data and configurations: Existing content and settings remain intact through an upgrade; for downgrades, ensure limits and feature availability are compatible.

Self‑serve vs. Enterprise

Self‑serve plans are optimized for speed: standard terms, card payments, quick upgrades.
Enterprise plans are designed for organizations with procurement, security, or compliance requirements. Expect custom terms, invoicing options, and a guided implementation approach.