Only pay for the services you actually run.

Pricing is organized around workspace scale and selected service modules, with room for guided rollout planning.

• The proposal starts from the active service modules you want to request: Community, Inventory, Projects, HR, and Finance.
• Workspace scale, number of teams, entity complexity, and activation support shape the final estimate.

Yes. Teams can begin with the active service modules that matter most, 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 modules 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 workspace scale and catalog service modules 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 active service modules as the operating model matures.
• Expansion should be planned so new modules 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 setup, 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 proposals 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 workspace setup that matches how the organization will actually run NodesOrbit after launch.