Frequently Asked Questions

CommandOS reduces the delay between something happening in your business and leadership understanding why it happened. It helps executives investigate performance changes, identify operational issues, compare branches, and access important information without waiting for manual reports.

The initial version is designed primarily for COOs, vice presidents of operations, CEOs, and other senior leaders responsible for operational performance across branches, teams, and departments.

Yes. CommandOS can support branch managers and other operational leaders, although the initial implementation is typically tailored around the questions and workflows of senior executives.

CommandOS is not currently designed as a technician-facing application. Its primary purpose is to give leadership and operational decision-makers clearer visibility into business performance.

CommandOS can answer questions about revenue, technician performance, conversion rates, callbacks, branch performance, capacity, utilization, gross margin, booking rates, dispatch outcomes, and other operational metrics available in your connected systems.

Yes. Leaders can investigate an issue through a sequence of related questions, moving from a high-level performance change into the branches, teams, technicians, or operational factors contributing to it.

Yes. During implementation, CommandOS is configured around your metrics, terminology, organizational structure, reporting logic, and the way your leadership team evaluates performance.

CommandOS can be refined as your organization uses it. New definitions, business rules, common questions, and reporting requirements can be incorporated so the platform becomes more aligned with how your leadership team operates.

CommandOS is an operational intelligence platform built specifically for field service companies. AI chat is only one part of the platform. Alongside executive dashboards, reports, alerts, and operational insights, it provides an AI assistant that understands the context of your business and can help investigate operational questions through natural follow-up conversations. Rather than being a general-purpose AI, CommandOS delivers operational intelligence tailored to field service operations using your company's data, metrics, and workflows.

No. CommandOS is designed to work on top of systems such as ServiceTitan, Housecall Pro, and other field service platforms. Your existing software remains the system of record.

No. Power BI and other dashboard tools remain useful for visual reporting and predefined analysis. CommandOS complements them by allowing leaders to ask new operational questions directly without navigating multiple dashboards or requesting another report.

Power BI is excellent for dashboards, visualizations, and predefined reporting. CommandOS serves a different purpose: it helps executives investigate operational questions directly, explore follow-up questions, and reach an answer without waiting for a new dashboard or report to be created.

CommandOS can be integrated with field service platforms, business intelligence tools, spreadsheets, databases, CRM systems, accounting platforms, and other sources containing relevant operational data. Supported integrations depend on your existing technology stack and implementation scope.

ServiceTitan integrations can be evaluated and configured during implementation based on your available data access, reporting requirements, and the operational questions you want CommandOS to answer.

Housecall Pro integrations can be evaluated during implementation. The specific approach depends on available APIs, exports, data access, and the information your leadership team needs.

Depending on your environment, CommandOS may connect to the underlying data sources used by Power BI or work alongside your existing reporting infrastructure. The appropriate integration method is determined during implementation.

Yes. Spreadsheets can be included as data sources when they contain important operational information that is not available elsewhere or is currently maintained manually.

Yes. CommandOS can be configured to work with supported databases and data warehouses, subject to your infrastructure, access controls, security requirements, and implementation scope.

Yes. One of the platform's primary purposes is to help leadership analyze operational information that may currently be fragmented across field service software, spreadsheets, dashboards, databases, and other systems.

CommandOS uses data from the systems approved during implementation. These may include your field service platform, reporting tools, databases, spreadsheets, CRM, accounting software, or other operational sources.

CommandOS is intended to analyze and interpret operational data, not replace or modify your systems of record. Any write-back capability would require separate approval, configuration, and safeguards.

Update frequency depends on the connected systems, available integrations, and your operational requirements. During implementation, we determine whether each source should be updated in real time, on a schedule, or through another appropriate method.

You retain ownership of your business data. CommandOS uses the data only to provide the agreed operational intelligence services and according to the applicable contract and security requirements.

Yes. Where historical data is available and reliable, CommandOS can use it for comparisons, trend analysis, performance investigation, and identifying changes over time.

Security requirements are reviewed during implementation. The deployment can include encrypted data transfer, controlled access, authentication, permissions, logging, and other safeguards appropriate to the agreed architecture.

Encryption requirements for data in transit and at rest are addressed as part of the implementation and deployment architecture. Exact controls depend on the systems being connected and the agreed environment.

Access can be limited to approved users such as the CEO, COO, vice president of operations, branch leaders, or other designated personnel. Permissions are configured according to your organizational requirements.

Yes. Access can be structured so users only see the information appropriate to their role, department, branch, or level of responsibility.

CommandOS should be configured to expose only the information required for approved operational use cases. Sensitive customer data can be restricted, masked, excluded, or governed according to your requirements.

The storage and deployment approach is determined during implementation based on the agreed architecture, connected systems, security requirements, and any applicable contractual or regulatory obligations.

Implementation typically includes connecting approved data sources, defining business metrics, mapping terminology, configuring permissions, validating data, testing answers, and tailoring CommandOS to the questions your leadership team regularly asks.

A typical initial implementation takes approximately two to four weeks. The timeline depends on data access, integration complexity, stakeholder availability, and the number of initial use cases.

Some IT or technical involvement may be required to provide secure access, approve integrations, clarify data sources, and review deployment requirements. The level of involvement depends on your existing systems and infrastructure.

Yes. Initial onboarding and training are included so approved users understand how to ask effective questions, interpret responses, and use CommandOS within their operational workflows.

After launch, the platform is monitored and refined based on usage, data quality, new questions, and evolving operational requirements. Ongoing support is provided according to your subscription agreement.

CommandOS helps leadership identify operational issues earlier, investigate performance changes faster, reduce dependence on manually prepared reports, and make decisions with more complete and timely information.

A dashboard shows metrics and views that have already been defined. CommandOS allows leaders to ask new questions, investigate unexpected changes, and explore follow-up questions without requiring a new report to be created.

Initial value can appear as soon as the connected data is validated and leadership begins using the platform for real operational questions. The speed and scale of the return depend on your use cases, data quality, and adoption.

ROI can be measured through faster issue detection, reduced reporting delays, fewer hours spent gathering information, improved visibility across branches, and the financial impact of acting on operational problems earlier.

No. Operational and financial outcomes depend on your data, processes, decisions, adoption, and execution. CommandOS provides faster access to information, but leadership remains responsible for deciding and acting on that information.

Pricing includes a one-time implementation fee and an ongoing subscription. The final scope may depend on the systems being connected, implementation complexity, number of users, and required capabilities.

CommandOS is not an off-the-shelf login. Implementation includes integrations, data validation, metric definitions, permissions, business terminology, testing, and configuration around how your leadership team actually operates.

The standard implementation structure is 50% due to begin the project and the remaining 50% due according to the agreed implementation milestone or launch terms.

Subscription terms can be structured monthly or annually depending on the agreement. Annual billing may include preferred commercial terms, while monthly billing provides a lower initial commitment.

Contract terms are defined in the commercial agreement. Any minimum commitment, renewal terms, cancellation notice, or annual option will be clearly documented before implementation begins.

Yes. Additional executives, branch leaders, managers, or other approved users can be added as the deployment expands, subject to permissions, training, and the applicable subscription terms.

Ongoing support includes assistance with platform usage, issue investigation, configuration questions, and reasonable refinements related to the agreed implementation. Exact support terms are defined in the service agreement.

Yes. Onboarding is part of implementation and includes stakeholder alignment, use-case definition, system configuration, validation, and training for the initial group of users.

Product improvements and platform updates are delivered as part of the ongoing service. Updates that materially affect integrations, workflows, or functionality will be communicated when appropriate.

Yes. The initial implementation can focus on a limited set of executive use cases and data sources. Additional departments, users, systems, metrics, and workflows can be added as priorities evolve.

The first step is a discovery call to review your systems, operational priorities, leadership questions, data availability, and implementation scope. If there is a fit, we provide a clear implementation plan and commercial agreement.

Yes. Demonstrations can be tailored around common HVAC, plumbing, and home service use cases so your leadership team can evaluate how CommandOS would fit into its existing operating process.