Deployment & pricing

Start focused.
Build the right environment.

Pricing is scoped to your users, selected Suites, infrastructure, integrations, and support requirements. Start with a useful workflow and a clear definition of success.

Deployment packages

Three starting points.

Pilot

Prove a useful workflow.

One team and a focused scope. Establish what the work needs, what success looks like, and how the environment should operate.

  • Workflow discovery
  • Selected Suite capabilities
  • Deployment and access planning
  • Acceptance criteria and review

Scoped to your deployment

Discuss Pilot →
Enterprise

Plan across environments.

Define the architecture, capacity, and operating responsibilities for multiple teams, tenants, or sites.

  • Environment and capacity planning
  • Broader integration requirements
  • Governance and retention mapping
  • Rollout and support planning

Scoped to your deployment

Discuss Enterprise →

Scope guide

Shape your starting scope.

Suggested starting packagePilot

10 users · 1 Suite · One local environment

This is a scope guide. A written proposal confirms availability, fees, responsibilities, and support.

Request a scoped quote ↗

Planning your deployment

What goes into a proposal.

People and roles

User count, administrative responsibilities, team structure, onboarding, and training.

Capabilities and compute

Selected Suites, models, infrastructure, storage, and concurrency requirements.

Data and connections

Source systems, migrations, identity, mail, file storage, and optional third-party services.

Operation and support

Deployment locations, monitoring, recovery planning, maintenance, and support coverage.

Bring your next workflow.

Start with the work your team needs to finish. We’ll help define the right capabilities, deployment, and next step.