Platform

Run the whole shop.One connected platform.

Thermal is one schema, not a bundle of separate apps: customer, service site, equipment, agreement, work order, and invoice, all wired together. Every page below is a view over that same spine.

Grouped by outcome

Win the work. Run the day. Get paid. Prove it.

Grouped the way a buying committee actually evaluates a platform — not a flat feature list, four jobs the software has to do.

Equipment is the spine

Every page above is a view over the same record, and that record starts with the equipment — not the calendar, and not a line item on a customer account. Age, warranty, refrigerant, and every past visit live on one serialized unit, so a callback connects to a cause instead of starting over.

See the equipment platform
The difference

Every decision is wired to a piece of equipment.

The unit is the spine of Thermal. Its age, run hours, refrigerant, warranty and every past visit live in one serialized record — so the system can connect a callback to a cause, and a tired RTU to a visit before it dies in July.

Tracking jobs tells you what happened. Tracking equipment tells you what to do next.

The tech sees what failed last time before they climb to the roof
Catch the failure before the tenant feels it — book on your terms
Prove the callback rate dropped because the right tech got the right job
Carrier 48TC · 7.5-ton RTU
78% RISK
4820G60418 · Northgate · installed 2019
Spring PM — agreement visit
Apr 2024 · healthy
No cooling — recharged
Jul 2025 · callback ×1
Low charge again — suspected leak
Oct 2025 · topped ×2
Book before peak — suggested
May 2026 · close the loop
A planned PM visit now beats a no-cool emergency across 40 units in July.

Illustrative interface mock — not customer data

What is "the platform"?

The full set of connected surfaces Thermal runs on one schema — customer, service site, equipment, agreement, work order, and invoice. Dispatch, agreements, equipment, and preventive maintenance are live today; the rest of this page tracks what's shipping next.

Why is equipment listed under "Run the day" instead of its own top-level thing?

Equipment isn't a side feature — it's the record every other page on this list reads from. It's grouped with the day-to-day operating surfaces because that's where a dispatcher and a technician actually touch it, even though it's structurally the center of the schema.

Some of these pages aren't built yet — why link to them?

Because the roadmap is real and we'd rather be honest about what's next than hide it. Pages marked "Early access" or "On the roadmap" say so plainly; pages not yet built route to their planned URL rather than a dead link, and we're finishing them.

Does Thermal replace my accounting system?

No. Thermal runs beside QuickBooks, Xero, and — on the roadmap — Sage Intacct and Microsoft Dynamics 365 Business Central. It never implements inside an ERP; it feeds the service and equipment layer those systems don't carry.

One platform. Every branch.

See how dispatch, agreements, and equipment run together on your own service area.