Why AI matters here • Function deep dives • Tool landscape • Execution Prompt Cards
For HVAC teams with 20+ technicians. Most shops are not struggling with demand — they are struggling with operations. Reduce office workload, tighten schedules, and close more jobs.
Most HVAC companies are not struggling with demand — they are struggling with operations. AI creates leverage in the office, on the road, and in the field when tied to ServiceTitan-class workflows and clear governance.
Built for: HVAC teams with 20+ technicians and multi-location dispatch.
Eight operating areas where AI pays back fastest in HVAC — mirror your dispatch, office, and field workflows.
Prioritize tools that integrate with your FSM stack — adoption beats novelty.
Compatible with ChatGPT, Claude, and Gemini via the prompt cards in this playbook. Optional derivative: 100+ HVAC prompt library (workflow kit).
Use these execution prompt cards to move from ideas to action. Start with the card that matches your immediate objective, add your context, then run it. Follow Step A to Step C for best results. This set is expanded by function and industry to reflect what this playbook specifically needs.
Start here: begin with Step A cards to build context, then move to Step B and Step C.
Execution path: Step A - Build Context
When to use this card: When starting a new workflow and you need clean context before solution design.
Next recommended card: Step A - Build Context: COMBO Chain Sequencer Prompt
This works because stronger context up front reduces hallucinations and improves relevance.
Expected outcomes: clearer inputs, fewer re-prompts, and better downstream output quality.
Execution path: Step A - Build Context
When to use this card: When you need prompts that build context and progress step-by-step.
Next recommended card: Step B - Diagnose and Prioritize: Risk and Control Prompt
This works because it creates explicit prompt chaining instead of isolated one-off prompts.
Expected outcomes: better continuity between outputs and faster execution from insight to action.
Execution path: Step B - Diagnose and Prioritize
When to use this card: When rolling out a new workflow or tool and you need risk visibility before scale.
Next recommended card: Step B - Diagnose and Prioritize: Callback Root-Cause Prompt
This works because it ties recommendations directly to risk severity and control design.
Expected outcomes: improved governance quality, fewer unmitigated risks, and better compliance readiness.
Execution path: Step B - Diagnose and Prioritize
When to use this card: When callback rate is eroding margin and customer trust.
Next recommended card: Step C - Design and Execute: Operational Decision Prompt
This works because it ties repeat visits to repeatable root causes.
Expected outcomes: fewer callbacks and stronger first-time fix rate.
Execution path: Step C - Design and Execute
When to use this card: When priorities are unclear and you need a fast, owner-ready action plan.
Next recommended card: Step C - Design and Execute: KPI and ROI Prompt
This works because it translates broad operational questions into accountable execution steps.
Expected outcomes: clearer priorities, faster decision cycles, and stronger operational follow-through.
Execution path: Step C - Design and Execute
When to use this card: When you need to justify investment decisions and track measurable business value.
Next recommended card: Step C - Design and Execute: Field Notes to Estimate Prompt
This works because it connects initiative planning to measurable business outcomes.
Expected outcomes: stronger measurement discipline, better investment decisions, and clearer value communication.
Execution path: Step C - Design and Execute
When to use this card: When office staff spend too long turning field notes into quotes.
Next recommended card: Step C - Design and Execute: Route and Schedule Optimization Prompt
This works because it standardizes estimate structure from unstructured inputs.
Expected outcomes: faster quote turnaround and fewer back-and-forth calls.
Execution path: Step C - Design and Execute
When to use this card: When dispatch struggles to fit more jobs per day during peak season.
Next recommended card: Step C - Design and Execute: A2L and Code Compliance Check Prompt
This works because it forces explicit tradeoffs between urgency, geography, and skill match.
Expected outcomes: tighter routes, better utilization, and fewer late arrivals.
Execution path: Step C - Design and Execute
When to use this card: When regulatory change increases install and documentation risk.
Next recommended card: Implementation handoff: convert output into owner-ready plan and operating cadence.
This works because it makes compliance checks explicit before work starts.
Expected outcomes: fewer compliance surprises and safer field execution.
Individual experiments, no standard process.
Some team usage, limited controls and repeatability.
Documented workflows, governance, and KPI tracking.
Cross-team adoption with continuous improvement loops.
Define scope, owners, controls, and baseline metrics.
Pilot one workflow and validate quality, speed, and risk outcomes.
Scale successful workflow patterns and formalize operating cadence.
Reference path: pilot field-notes-to-estimate in the office for two weeks, then add route optimization for peak season with weekly callback review.
Related playbooks: Construction, Customer Service.