Calculate your monthly NodesOrbit package before onboarding.

Pricing is organized around operating services and company size, with room for enterprise bundles and phased rollout planning.

• The proposal starts from the service areas you want to activate, such as Command Center, Operations, Projects, Inventory, Finance, HR, Security, Communities, or Reporting.
• Company size, number of teams, entity complexity, and activation support shape the final package.

Yes. Teams can begin with the services that matter most, such as command center, operations, projects, inventory, finance, HR, security, communities, or reporting, then expand when ready.

• A phased rollout keeps adoption realistic and prevents teams from paying attention to services they are not ready to operationalize.
• New service areas can be added later with the right permissions, owners, and reporting expectations.

Yes. The calculator uses the same catalog source as dashboard onboarding, then dashboard onboarding recomputes the final monthly total before activation.

• The public estimate is based on selected company size and catalog services only.
• Activation, account setup, and any future billing changes still happen inside the dashboard.

Resident Mobile is separate from dashboard seats and is priced in USD using activated unit-day usage.

• Resident and household accounts do not consume dashboard seats.
• The dashboard add-on page shows the current USD unit-day rate, active units, promo impact, and month-to-date usage.

Yes. NodesOrbit is designed for service expansion after the initial rollout, as long as ownership, permissions, data readiness, and reporting needs are clear.

• Teams can add domains such as procurement, inventory, HR, finance, security, or additional reporting as the operating model matures.
• Expansion should be planned so new services do not create duplicate data or unclear responsibility.

Team size helps define seat guidance, support expectations, permission complexity, and the amount of activation help needed across services.

• A small team may need a focused service package, while a larger organization may need multiple roles, entities, approval paths, and reporting layers.
• The final proposal should match how many people actively operate, review, approve, and report inside NodesOrbit.

Yes. Enterprise packaging should reflect operating responsibility, service ownership, and rollout phases rather than only seat counts.

• Enterprise planning can include multiple entities, different service owners, role design, governance expectations, and phased activation.
• The goal is a package that matches how the organization will actually run NodesOrbit after launch.