Evaluate a New HVAC Product Before Adding It to Your Offering

Describe the problem the product is intended to solve. Examples might include an outdoor placement constraint, a room that needs a different conditioning approach, or an owner who needs clearer control of operating schedules. The need should exist independently of the product’s marketing language.

Then describe the alternatives already available to the company. A useful comparison asks what changes for the customer and for the people doing the work. A longer feature list is not necessarily an improvement if the extra features do not address the application.

Avoid starting with a claim such as “AI improves every system.” Ask what the specific function does, what inputs it uses, what equipment it supports, and what happens when the connection or sensor is unavailable.

Collect the manufacturer’s current product data, installation instructions, approved combinations, control requirements, and service information. Distinguish a family brochure’s maximum rating from the rating and operating characteristics of the proposed combination.

The AHRI Directory of Certified Product Performance provides a way to search certified equipment performance. Use the applicable record alongside manufacturer application information; a certified rating does not answer every question about site suitability or installation.

Record document versions and unresolved questions. If a capability depends on an accessory, subscription, network connection, or particular indoor unit, make that condition visible in the offering. Do not assume a feature shown on a demonstration system is included in every box.

Choose a suitable application, responsible technical lead, and review criteria before the first job. A trial should test the process the company intends to repeat: selection, ordering, installation, startup, customer instruction, and later service access.

Use an actual job only with the required application review and customer agreement. Do not treat a paying customer as an unannounced experiment or bypass manufacturer requirements because the product is new to the team.

A hypothetical introduction might reveal that the equipment installs as planned but the proposal omitted a control accessory and the customer handoff did not explain account ownership. Those findings call for changes to the quote and handoff, not an unsupported statement that the product is unreliable.

Include an ordinary service scenario in the introduction review. Ask the team to locate the correct service document, identify the supported diagnostic path, determine who can obtain a replacement part, and explain how the customer will get help. If those answers rely on one employee’s personal contact or password, the offering is not yet supported by a repeatable company process.

Also ask what happens when the product’s connected features are unavailable. Confirm the documented local operating behavior and the owner’s responsibilities. The answer belongs in customer expectations before installation, not in a surprise explanation after a network outage.

Compare actual preparation, installation, follow-up effort, unresolved questions, and customer understanding with the original plan. Record what was learned and which changes are needed before broader use.

Separate measured observations from predictions. One successful installation does not prove a company-wide savings rate, failure reduction, or long-term financial return. Retain enough context to explain the conditions under which the result occurred.

Ask Mar-Hy about the specific equipment family, current manufacturer documentation, and relevant training. Confirm the application and support arrangements before turning a new product into a standard promise.