A mid-market HVAC company went from whiteboard sketches to a working CRM + dispatch + field app in three weeks. Here’s the prototype you can try right now.
What the HVAC Team Actually Needed
Sales lived in one system, job scheduling in a shared spreadsheet, and technicians ran on WhatsApp and printed work orders. Nothing talked to anything else. Every missed service window meant an angry facilities manager. Every lost job-photo meant revenue stuck in “to invoice” for weeks.
The brief in one sentence: “Give us a single place to see every asset we maintain, every open job, and every technician in the field — and make it impossible to forget a follow-up.”
One Spec, Three Surfaces: CRM, Dispatch, Field
We wrote the spec first. Three pillars: a CRM for customers and sites, a dispatch board for jobs and crews, and a mobile-friendly field app for technicians to see today’s work, capture data sheets, and close jobs with photos and signatures.
On the office side, the CRM view covered companies, sites, and equipment with clear relationships: rooftop chiller units, AHUs, compressors, and annual maintenance contracts. The dispatch view gave planners a day and week board: drag a job onto a technician, see travel time, capacity, and SLAs in one place.
On the field side, technicians saw a simple list of today’s jobs, tap-through work order details, access instructions, and a structured data sheet for each asset: readings, replaced parts, photos, and customer sign-off.
The test wasn’t “does it look good?” It was: can a technician in a boiler room, on 4G, complete a job without calling the office once?
The bar we set for the first pilotBecause the spec drives the build, updating the workflow — adding a checklist step, changing a data point, tweaking a permission — becomes an edit to the document, not an endless chain of tickets. The same spec that gave us this three-week prototype will power the production build.
The spec is the product. The code is what follows.