LA NPDT — LA New Product Development Team

Our work / venthalpy

IoT Product Development: From Sensor to Dashboard

What a custom IoT build actually includes

  • Hardware Development
  • Software & Mobile App Creation
  • IoT Integration
Start a project
IoT Product Development: From Sensor to Dashboard
Ashok Chintagunta

Written by Ashok Chintagunta, MS Computer Science, Louisiana Tech University

CTO & Software Engineer, AI and Automation

Updated September 3, 2026

An IoT product is really three products that have to ship together: instrument hardware that measures accurately, firmware that gets the data off the device reliably, and an app that turns the readings into a decision someone will pay for.

Venthalpy hired us as a single partner for all three — Air and Fluid diagnostic probes, the firmware, and the mobile app that grades HVAC efficiency and produces customer-facing reports.

Project at a glance

Client
Venthalpy — smart HVAC diagnostics platform
Category
IoT instrumentation and mobile app
Hardware
Air probes for air-to-air heat exchange; fluid probes for chillers, cooling towers and hot water boilers
Measured
Temperature, pressure, relative humidity, air quality, airflow rate, duct leakage, insulation efficiency
What we delivered
Mechanical and electronics engineering, firmware, IoT integration and the iOS mobile application
Why it matters
HVAC accounts for close to 40% of energy use in commercial buildings
Custom IoT product development means one team designing the sensor hardware, the firmware, the connectivity and the app or dashboard that turns the data into a decision. We have built that full stack for HVAC diagnostics, connected consumer products and industrial monitoring — prototype through production.
  • Sensor hardware: probe or board selection, analog front end, and a custom enclosure that survives the field environment
  • Firmware: measurement loop, calibration, power management, and over-the-air update capability
  • Connectivity: BLE for technician tools, Wi-Fi or cellular for always-connected devices, with a provisioning flow a non-engineer can complete
  • App and dashboard: the screens that turn raw readings into a recommendation, a grade or an alert
  • Cloud pipeline: ingestion, storage and the API the app and dashboard share

Case study: Venthalpy — IoT HVAC diagnostic probes and iOS app

The client

The modern urban landscape presents a significant challenge: energy-intensive HVAC systems represent a substantial portion of our environmental footprint, especially when considering they account for almost 40% of total energy use in commercial buildings.
In this context, Venthalpy emerged as a revolutionary IoT platform, poised to redefine the HVAC service industry with its smart diagnostic instruments. Their vision was clear, but realizing it required the right technological partner: LA NPDT.

The challenge

HVAC efficiency is invisible on site. A technician can measure a supply temperature and still not know whether a system is undersized, leaking through the ducts, or fighting poor insulation. Venthalpy needed instruments accurate enough to stand behind a recommendation, an app that turned raw temperature, pressure and humidity streams into a grade a homeowner could understand, and a wireless workflow rugged enough for attics, crawl spaces and rooftops.
We took on the mantle to design and develop both the hardware and software components for Venthalpy, aligning with their ethos of efficiency and innovation.
Dustin Morris, a key figure at Venthalpy, describes the system's value to both HVAC contractors and homeowners.
Venthalpy probe connected to an HVAC unit during a field diagnostic
Venthalpy iOS app tutorial screens guiding a technician through a measurement
From empowering novice technicians to accurately diagnose entire spaces, to presenting clear before-and-after efficiency comparisons, the capabilities of Venthalpy are groundbreaking.
Dustin also touches on the system’s unique ability to detect duct leakages and evaluate a building’s insulation quality, ensuring homes and businesses operate at peak efficiency.

Our solution

Our joint efforts culminated in a suite of advanced diagnostic tools, including the standout Air and Fluid probes.
These instruments, finely-tuned for their respective applications, capture critical data, from temperature and pressure to relative humidity and air quality.
Yet, raw data needs interpretation. The Venthalpy mobile app, another brainchild of our collaboration, seamlessly integrates with the diagnostic instruments.
It translates intricate metrics into digestible insights, empowering technicians and customers alike.
With this platform, users can make informed financial and technical decisions, whether it’s about HVAC system modifications, essential repairs, or strategic upgrades.
The decisive capability is grading: Venthalpy evaluates the efficiency of any HVAC unit and returns a precise diagnosis, saving time and unnecessary parts on site.
The system can ascertain air flow rates, detect potential leakages, and even calculate the real-time insulation efficiency of buildings.

The result

Together, Venthalpy and LA NPDT are shaping a sustainable future, one HVAC system at a time, making strides in both operational efficiency and eco-consciousness.

Customer testimonial

“Partnering with LA NPDT was pivotal for Venthalpy. Their comprehensive product development expertise, encompassing mechanical and electronics engineering to firmware and mobile app creation, was instrumental in bringing our vision to life. Thanks to our collaboration, our system now has the potential to improve HVAC efficiency nationwide, paving the way for more sustainable buildings. Engaging with a singular, unified development company like LA NPDT streamlines the journey from concept to reality.”
DUSTIN MORRIS COO Venthalpy ProductsVenthalpy
Dustin Morris of Venthalpy, HVAC diagnostics partner

Services provided

LA NPDT proudly served as the key technology development partner for Venthalpy. Our multi-disciplinary approach and expertise allowed us to comprehensively address the diverse needs of the project. Here’s a breakdown of our involvement:

Hardware development

We meticulously designed and developed the HVACR Tools for Venthalpy, including the advanced Air and Fluid probes. The air probes were tailored for air-to-air heat exchange applications, encapsulating features such as temperature, pressure, relative humidity, and air quality monitoring. The fluid probes, on the other hand, were curated for liquid-to-air heat exchange applications, specifically for equipment like chillers, cooling towers, and hot water boilers.

Software and mobile app

Recognizing the importance of intuitive and user-friendly software, we crafted a mobile application for Venthalpy. This app seamlessly communicates with the tools, allowing for real-time data monitoring. It simplifies complex data, offering users visual and textual insights, and further allows for efficient report generation.

IoT integration

To ensure that Venthalpy stood at the forefront of HVAC service industry innovations, we integrated Internet of Things (IoT) capabilities. This not only enhanced the product’s diagnostic proficiency but also provided continuous monitoring capabilities, making Venthalpy a comprehensive IoT solution tailored for HVAC companies.
Throughout our collaboration, our primary objective was to ensure that Venthalpy’s vision was realized in a manner that embodied efficiency, sustainability, and user-centric design.
The HVAC efficiency system we developed, from sensor hardware to the mobile app.
Video page ↗

What an IoT product costs to develop

Electronics raise the floor: an IoT build starts where a mechanical product ends, because board spins, certification and app work all have real minimums. The prototype stage is where the architecture decisions get made cheaply.

How the build runs

  • Prove the physics first: a bench rig confirms the sensor and measurement approach before any enclosure design starts
  • Prototype the full chain: probe, firmware, app screen — so the data flow is real, not a mockup
  • Harden for the field: sealing, drop and thermal work, battery life, and a provisioning flow tested on non-technical users
  • Scale the back end last: cloud and dashboard features grow once the device is stable

Frequently asked questions

How long does it take to develop a custom IoT product?

A connected proof-of-concept typically takes 3 to 5 months. Getting to a pilot-ready device you can put in customers' hands usually runs 9 to 14 months including enclosure hardening and app polish. Timeline moves most with certification scope and app complexity.

Do you build both the hardware and the app?

Yes — that is the point of a single-team build. On Venthalpy the same project covered the diagnostic probes, the firmware and the iOS app, so the data path from sensor to screen was designed once instead of handed off between vendors.

Which connectivity should a field device use?

BLE fits tools a technician pairs with on site, like the Venthalpy probes. Wi-Fi suits devices in a building with known infrastructure. Cellular is the answer when the device sits where neither exists — but it adds module cost, carrier plans and certification scope, so we only spec it when the use case demands it.

Can you start from an existing prototype or proof of concept?

Yes. A working bench prototype is valuable evidence — we audit what it proves, identify the gap to a manufacturable device, and quote the remaining work as stages: production electronics redesign, enclosure, firmware hardening and app completion.

Related resources

Capabilities used on this project

How a connected diagnostic instrument gets built

HVAC systems account for close to 40% of energy use in commercial buildings. Turning that into a business means measuring it credibly, which is an engineering problem across four disciplines at once.

  1. 1. Start from the measurement, not the app

    Everything downstream inherits the sensor's accuracy. The Venthalpy air probes measure temperature, pressure, relative humidity and air quality for air-to-air heat exchange; the fluid probes are built for liquid-to-air equipment such as chillers, cooling towers and hot water boilers.

  2. 2. Design the probe as a field tool

    These instruments live in trucks and mechanical rooms. Housing, sealing, connector choice and probe geometry are set by the working environment and by how a technician actually holds and inserts the tool, not by the PCB outline.

  3. 3. Build firmware around what the app must guarantee

    Sampling, filtering and the connection protocol determine whether a reading is trustworthy and whether it appears when the technician expects it. The firmware contract is agreed before the app UI, because the UI cannot fix an unreliable stream.

  4. 4. Turn raw data into a verdict

    The Venthalpy app translates the metrics into digestible insight — airflow rates, duct leakage detection, insulation efficiency and an efficiency grade for the unit. A number a homeowner can act on is the product; the reading is only the input.

  5. 5. Give the technician something to hand over

    Report generation and before-and-after efficiency comparisons let a novice technician diagnose a whole space and justify the recommendation. That output is what converts a service call into an approved repair or upgrade.

  6. 6. Keep hardware, firmware and app on one schedule

    Split these across three vendors and every defect becomes a negotiation. Running mechanical, electronics, firmware and app development under one team is what let Venthalpy move from concept to a working platform without integration stalls.

The four layers of an IoT product
LayerWhat it decidesTypical failure if rushed
Sensing and mechanicalAccuracy, durability, how the tool is heldReadings that drift or a probe that breaks in the field
ElectronicsPower, sampling, connectivityBattery life and dropouts discovered after tooling
FirmwareReliability of the data streamData that arrives late, out of order, or not at all
Mobile app and cloudWhether the data becomes a decisionA beautiful dashboard nobody acts on
IoT product developmentElectronics and firmware engineering

Questions about this project

Straight answers from the engineers who ran the build. Have a different question? Ask us directly.

Talk to an engineer
Should hardware and the app be developed by the same company?

For a connected instrument, yes. Most IoT programs fail at the seams — a firmware timing issue looks like an app bug, an accuracy problem looks like a sensor defect. One team holding mechanical, electronics, firmware and app removes the finger-pointing and the schedule risk that comes with it.

What does IoT development actually cost to get to a working system?

It is driven by how many sensing modalities you need and how regulated the environment is. A single-sensor device with a simple app is a fraction of a multi-probe platform like Venthalpy, which needed two distinct instrument families plus reporting. We scope it against the measurements you truly need on day one.

How do you keep an app from just being a data dashboard?

By deciding early what verdict the user needs. Venthalpy grades a unit's efficiency and shows before-and-after comparisons, so a technician can justify work to a customer. Raw metrics belong underneath that answer, not in place of it.

Can you support the product after launch?

Yes — connected products change after they ship, because firmware, app platforms and sensor supply all move. We stay engaged for revisions, added probe types and platform updates rather than handing over files and disappearing.

Industries this project belongs to

See how we approach development in each of these categories, and the other products we have taken from sketch to production there.

More of our work

Get in touch

Tell us what this is about

Share a few details about your question, partnership, or idea — a member of the LA NPDT team will reply within one business day.

Optional context

What are you looking to accomplish? (optional)

What do you already have? (optional — tick any)

Your information stays confidential and is never shared.