INDUSTRY / HVAC
Aevrion does CRM implementation for HVAC companies and builds the lead-flow automation around it. The question is rarely which CRM to buy: it is who holds the lead between the call and the booked job, what state the replacement estimate is in, and when follow-up is supposed to stop — and those are answerable on the system a company already runs.
Aevrion configures the operating process around the field-service platform you already run. Where that platform genuinely cannot carry the work, the constraint is named before anything is replaced.
01 / THE LIFECYCLE
An HVAC opportunity travels these positions whether or not anyone designed them. Where a position is undefined, the outcome underneath is what tends to fill the gap.
Where the inquiry came from — a search result, a map listing, a referral, a maintenance customer calling back, or a technician's recommendation on a service visit. Recorded on the record itself, not inferred later from a report.
Undefined: Spend and referral relationships are evaluated on impression, because nothing links a booked job back to what produced it.
The moment a person asks for something: a call, a form, a chat, a message on a map listing, or a reply to a maintenance reminder.
Undefined: Channels nobody watches accumulate requests that are answered days later or not at all.
The inquiry becomes a record with the customer's actual request attached — the equipment, the symptom, the property, and whether anything is currently running.
Undefined: The second conversation restarts the first one, and the customer repeats themselves to a company that already had the answer.
No heat, no cooling, a repair that can wait, a replacement enquiry, or a maintenance matter. This single decision selects which process applies and how fast it has to move.
Undefined: A no-heat call in February sits in the same queue as a request for a quote in April, and one of them is being served by a process built for the other.
One named person holds the record until it reaches an outcome. Ownership survives shift changes, weekends, holidays and the seasonal peak when everybody is busy.
Undefined: Everybody assumes somebody has it. During a heat wave, that assumption is made about far more records than usual.
One place that is authoritative for this customer and this opportunity. Where a company already runs a field-service platform, that is the first candidate — see the systems question below rather than assuming a second tool is needed.
Undefined: The truth is distributed across a dispatch board, an inbox, a spreadsheet and a technician's phone, and no two agree.
The visit is scheduled against real capacity, with an arrival expectation the customer was actually told and the office can actually see.
Undefined: Arrival windows are promised by whoever answered the phone and discovered by whoever has to drive there.
The visit produces either completed work or a priced proposal. A replacement proposal usually carries options — capacity, efficiency tier, sometimes a phased approach — and the option the customer was actually recommended is part of the record.
Undefined: The proposal exists as a number in a technician's memory and a photograph of a written page, and the office cannot follow up on something it cannot see.
Where a replacement is financed, approval is its own state with its own owner and its own clock. The customer may be committed while the application is not, and those are different situations requiring different next actions.
Undefined: A ready buyer is chased for a decision they already made, while the actual blocker — an incomplete application — goes unattended.
A defined owner, a defined next action and a defined stopping condition. The sequence changes or halts the moment the customer replies, accepts, declines, asks for time or opts out.
Undefined: Either nothing happens, or the same household is contacted four times by three people, which reads as disorganised rather than attentive.
Won, lost or deferred — recorded, with a reason specific enough to act on. “Price” is not a reason; “quoted two-stage, bought single-stage elsewhere” is.
Undefined: The pipeline shows opportunity that was decided months ago, and nothing about the loss can be learned.
Deferred replacements return with the season. Maintenance agreements come up for renewal on a date somebody must own. Both are scheduled work, not a marketing afterthought.
Undefined: A summer estimate marked “no” disappears, and the same household buys in November from whoever called first.
No company designs all twelve at once. The useful question is which of them currently depend on one person remembering — and what happens to those positions in the first week of a heat wave.
02 / THREE DIFFERENT BUSINESSES
Each has a different clock, a different decision-maker and a different failure mode. A pipeline that treats them identically is serving at least two of them with a process built for the third.
NO HEAT / NO COOLING
Minutes to hours
A house with no heat in winter or no cooling in a heat wave is a habitability problem, not a purchase decision. The customer is comparing who can come, not what it costs, and will keep calling down the results until somebody answers.
Failure mode: The call is lost during the ring-out, and nobody in the business ever knows it existed.
SYSTEM REPLACEMENT
Days to months
A replacement is a considered, usually financed purchase with more than one person in the decision. It may involve comparison quotes, a financing application, and a gap far longer than the customer's stated urgency suggests.
Failure mode: The estimate is sent, the household goes quiet for three weeks, and by the time anyone looks the system has been installed by somebody else.
MAINTENANCE AGREEMENT
Recurring, annual
The recurring relationship: scheduled visits, priority response, and the renewal that keeps it alive. It also creates a recurring customer relationship that can surface future repair and replacement opportunities, because a technician sees the equipment on a schedule rather than after it fails.
Failure mode: Agreements lapse silently because renewal belongs to nobody, and the replacement the technician flagged in spring is never followed up.
The maintenance column is the one most easily left out of a lead-flow conversation, and it is the one where an existing customer relationship can produce work without a new acquisition cost.
03 / WHAT STOPS BEING A MATTER OF MEMORY
No heat, no cooling, deferrable repair, replacement enquiry and maintenance are separated at the record — because each one deserves a different speed and a different owner.
One named person holds each opportunity until it reaches an outcome, and that survives the week when everyone is on a roof.
A replacement proposal carries a status the office can read without asking the technician who wrote it.
An application in progress is distinguishable from a customer still deciding, because those require different next actions from different people.
Follow-up has defined conditions that change or end it. They are designed before any cadence is chosen.
Won, lost and deferred are recorded with a reason specific enough to change something — and deferred work carries a date it comes back.
04 / WHERE HVAC LEAD FLOW BREAKS
These are the points where an opportunity stops being anybody's responsibility. None of them is a software problem first, and all five get worse exactly when volume is highest.
In the first heat wave, call volume doubles and the process that worked in April stops working. The handoffs that depend on somebody remembering are the first to fail, and they fail on the busiest revenue days of the year.
Demand falls, and the deferred estimates from the peak are the obvious place to look. They are also the least likely to have been recorded with a reason or a return date.
A technician recommends replacement during a maintenance visit. The recommendation comes from someone who has just examined the equipment, and where no route exists from the visit back into the pipeline it never becomes a record at all.
Maintenance agreements lapse silently, because renewal has a date but not an owner. The revenue is missed twice: the agreement, and the replacement lead the visit would have produced.
A no-heat call arrives at 21:10. It is captured by an answering service and owned by nobody until morning, by which time the household has booked whoever picked up.
The first of those gaps has a workflow rather than a setting behind it. What has to exist around an automatic reply — the owner, the repeat-call rule, the callback and the stopping condition — is set out in the HVAC missed-call text-back workflow.
05 / EXISTING SYSTEMS FIRST
HVAC is unusual here: a field-service platform including customer and pipeline functionality is commonly already in place. Where it is, adding a separate CRM alongside it introduces a synchronisation problem that has to be worth the operating one it solves.
Where Aevrion finds a capable field-service platform being used as a dispatch board — no classification that changes behaviour, no ownership field anyone trusts, estimate status held in a technician’s phone — that is a configuration and operating-rules problem. Replacing the software does not solve it, and usually postpones it by a year.
A second system is justified when a specific constraint blocks the work: no way to represent an opportunity that has not become a job, no usable integration for the lead sources that matter, or a licensing model that keeps the people doing the work out of the record. The constraint is named before the recommendation.
Aevrion does not resell software and takes no platform commission. Most of the results competing for this search are software vendors, which is worth knowing when reading any recommendation about which system you need — including this one.
The full version of this decision — what owns the lead, what owns the job, where ownership changes and when integration is actually necessary — is set out in HVAC CRM versus field service software. Where a business has already settled on a specific platform, the configuration work is described at GoHighLevel implementation.
06 / WHERE AUTOMATION STOPS
A customer who replies is talking to the business, and the business should answer — not continue a sequence. Automation stops or changes the moment someone responds, accepts, declines, asks for time or opts out.
Deciding whether a fifteen-year-old system is worth repairing, pricing an awkward installation, explaining why the cheaper quote is cheaper, or handling a household without heat in February are human decisions. Automation should reach those points faster and with better information — not make them.
Anything that would be embarrassing if the customer saw the mechanism behind it should not be automated.
07 / HOW AEVRION IMPLEMENTS
Trace real recent inquiries end to end — including the ones that went nowhere and the ones that arrived during the busiest week. The map is built from actual cases, not from how the process is described in a meeting.
Decide classification, ownership, response expectations and stopping conditions. These are business decisions; software cannot make them and should not obscure them.
Shape the existing field-service platform around those rules. Where a capable platform is already in place, configuring it is the first option Aevrion tests — see the systems section below.
Connect the steps that are now explicit, routing exceptions to a named person rather than dropping them.
Run the workflow against real historical inquiries — including a no-heat call, a financed replacement and a lapsed renewal — before it carries live work.
Document what runs, who owns it and how to change it, so the business is not dependent on whoever configured it.
08 / THE REVIEW
A structured read of how one real inquiry moves through the business, from first contact to recorded outcome.
How a call, form or map message arrives, what is captured with it, and what happens to the ones that arrive after hours or during a seasonal peak.
Whether no-heat, no-cooling, repair, replacement and maintenance are separated at the record, and whether that separation changes what happens next.
Whether one named person holds each opportunity, and how that survives a week when everybody is on the roof.
What the existing field-service platform can already represent, and where the business is working around it rather than in it.
Whether a replacement proposal has a status the office can read without asking the technician who wrote it.
Whether an application in progress is distinguishable from a customer still deciding.
Who owns the next action, what changes it, and what stops it.
Whether lost and deferred are recorded specifically enough to change anything, and whether deferred work returns with the season.
A written map of the current flow, identifying:
The review does not calculate lost revenue. Any such figure would require conversion data the business has not yet been able to record — which the review exists to establish rather than assume.
09 / DECISION SUPPORT
Often not. Those platforms include customer and pipeline functionality, and adding a second system introduces a synchronisation problem that has to be worth the operational one it removes. The question worth answering first is which system is authoritative for an opportunity that has not yet become a job — that handoff is one place where lead flow can break down. The systems article works through when a second tool is genuinely justified and when it is not.
No. Marketing produces the inquiry. Aevrion works on what happens operationally after one arrives — capture, classification, ownership, estimate state, follow-up and outcome. A shortage of inquiries and a shortage of booked jobs are different problems with different fixes.
Three things change the design. Replacement is a financed purchase, so finance approval is its own pipeline state. Demand is weather-driven, so deferred work returns seasonally and needs a route back. And maintenance agreements are a recurring relationship with a renewal date, which is both recurring revenue and a relationship that can surface future repair and replacement work.
No, and Aevrion takes no platform commission. A recommendation to change tools is a real cost to the business, so it needs a reason that survives being written down.
No. Aevrion publishes no HVAC client results, because none exist to publish. What the work produces is a process where every handoff has an owner, a visible state and a defined next action — which is a precondition for measuring conversion, not a substitute for it.
The moment a customer replies, accepts, declines, asks for time or opts out. Pricing an unusual installation, judging whether a system is worth repairing, and handling a complaint are human decisions. Automation should reach those points faster and with better information, not make them.
NEXT
Bring one real inquiry from the last season — ideally a replacement estimate that never closed. Aevrion works outward from that single case.
Request an HVAC lead-flow review