Start a project

INDUSTRIES / HOME SERVICES

AI, CRM and Workflow Automation for Home Service Businesses

A home-service business rarely loses work because it is short of inquiries. It loses work in the gaps between them — the call nobody returned, the quote nobody chased, the job nobody marked lost. This is the operating layer that closes those gaps: capture, ownership, routing, follow-up and a recorded outcome for every opportunity.

Aevrion works on what happens after an inquiry arrives. Marketing produces the inquiry; this is the process that decides whether it becomes a booked job — configured around the CRM or field-service platform you already run.

Request a lead-flow review See the published verticals

01 / THE OPERATING LAYER

Fourteen control points between an inquiry and a booked job.

Every home-service business already has these — the question is only whether each one is defined and owned, or left to whoever happens to remember. Where a control point is undefined, the outcome underneath it is whatever the busiest day produces.

  1. 01

    LEAD CAPTURE

    Every inquiry becomes a record, whichever channel it arrived on — phone, form, chat, marketplace or a referral someone took by text. A lead that exists only in a call log is not captured.

  2. 02

    WEBSITE-TO-CRM LEAD FLOW

    The path from a form submission to a CRM record with its source attached, verified end to end rather than assumed. A form that emails an inbox is a notification, not a pipeline.

  3. 03

    MISSED-CALL HANDLING

    What happens in the minutes after an unanswered call: acknowledgement where messaging is appropriate, an urgency decision, a record, an owner and a callback path with a stated expectation.

  4. 04

    CRM OWNERSHIP

    One named person holds each opportunity until it reaches an outcome. Ownership that rotates by whoever is free is not ownership; it is the reason a lead can be everyone's and nobody's at once.

  5. 05

    LEAD ROUTING

    The rule that decides who receives what, based on classification rather than availability — so an emergency and a replacement quote do not queue behind each other.

  6. 06

    PIPELINE STATES

    Stages that describe what is actually true of the opportunity, readable by someone who was not on the call. If a stage cannot be verified by looking at the record, it is a label, not a state.

  7. 07

    APPOINTMENT WORKFLOWS

    Booking, confirmation, reminder, rescheduling and no-show handling, each with an owner. The reminder is the visible part; what happens when nobody answers the door is the part that decides the outcome.

  8. 08

    ESTIMATE AND QUOTE FOLLOW-UP

    A quote carries a status the office can read without asking the technician who wrote it, and a follow-up sequence with a named owner rather than a reminder in somebody's phone.

  9. 09

    STOPPING CONDITIONS

    The conditions that change or end an automated sequence — a reply, an acceptance, a decline, a request for time, an opt-out. These are designed before any cadence is chosen, not bolted on after a complaint.

  10. 10

    HUMAN HANDOFF

    The defined point where the system stops and a person takes over, with the context already assembled. Pricing an awkward job, judging whether equipment is worth repairing and handling a complaint are human decisions.

  11. 11

    OUTCOME AND REASON

    Won, lost and deferred recorded with a reason specific enough to change something — and deferred work carrying a date it comes back with an owner on that date.

  12. 12

    REVIEW REQUESTS

    Asked at the point the work was actually completed and received well, by a route the customer recognises. A blanket request sent to every closed job includes the ones that went badly.

  13. 13

    REACTIVATION

    Past customers and dead estimates returned to, on a basis that is defensible: a service interval, a deferred decision with a date, or a recorded reason that has since changed.

  14. 14

    REPORTING

    The small number of figures that change a decision — where leads come from, which ones convert, where opportunities stall, what is sitting unowned right now — assembled from the record rather than from memory.

No business defines all fourteen at once, and none of them is a software feature. They are operating decisions — a tool can hold them once they exist, and cannot make them on the business’s behalf.

02 / WHERE LEAD FLOW BREAKS

Five gaps every trade in this category shares.

Five failures that recur across every trade in this category, whatever software sits underneath them. Each has the same shape: a moment where responsibility is handed over and nobody catches it.

  1. 01

    THE AFTER-HOURS GAP

    An inquiry arrives outside working hours, is captured by an answering service or a voicemail, and is owned by nobody until morning — by which time the customer has usually booked whoever answered.

  2. 02

    THE CHANNEL GAP

    Phone, form, chat and marketplace leads land in different places, and only some of them reach the system of record. The channels that do not reach it are invisible in every report that follows.

  3. 03

    THE FIELD-TO-OFFICE GAP

    A technician on site sees work worth quoting. Where there is no route from the visit back into the pipeline, the observation stays in a van and never becomes an opportunity.

  4. 04

    THE SILENCE GAP

    A quote is sent and nothing happens. Without a state and an owner, silence is indistinguishable from a decision, so the follow-up that would have resolved it is never triggered.

  5. 05

    THE OUTCOME GAP

    Lost work is never marked lost and deferred work is never marked deferred, so the pipeline fills with opportunities nobody can act on and the reporting underneath it describes a business that does not exist.

03 / PUBLISHED VERTICALS

Two trades have pages. They are not equally developed, and it is worth saying which.

Each vertical below applies the operating layer to the commercial motions of one trade. The depth of each is exactly the list of routes underneath it — no more is implied.

GARAGE DOOR

Garage door CRM and lead-flow systems

The operating layer between a garage door inquiry and a booked job: capture, ownership, CRM structure, missed-call recovery, estimate follow-up and recorded outcome.

What is different here: Two commercial motions run through one phone line. An urgent repair is a same-day dispatch decision; a replacement door is a considered purchase that has to survive a gap of days or weeks. A pipeline that treats them identically is serving one of them with a process built for the other.

HVAC

HVAC CRM and lead-flow systems

The operating layer between an HVAC inquiry and a booked job: classification, ownership, estimate and financing state, follow-up, outcome and maintenance renewal.

What is different here: Three motions rather than two. Emergencies have a clock, financed replacements have a lender in the middle of the pipeline, and maintenance agreements are a recurring relationship with a renewal date. Weather moves all three at once.

04 / WHAT IS NOT BUILT

The trades below have no page, and no engagement behind them.

They share the lead-flow shape described above, which is why Aevrion is willing to work in them. That willingness is not experience, and this page will not present it as any.

  • Plumbing
  • Electrical
  • Roofing
  • Pest control
  • Landscaping and lawn care
  • Cleaning services
  • Appliance repair
  • Pool service

No client results, conversion rates or engagement counts are published for any trade on this site, including the two that do have pages. A specialist page will exist for a trade when there is something specific to say about it — not before.

05 / EXISTING SYSTEMS FIRST

You probably already own the software. The question is what is authoritative.

Home-service businesses commonly already run a CRM or a field-service platform with customer and pipeline functionality. Where one is in place, adding a second system introduces a synchronisation problem that has to be worth the operating one it removes.

The software is rarely the thing that is broken

Start by asking what the current system is being asked to do that it genuinely cannot. In most of these businesses the honest answer is nothing: the platform can already hold states, owners and follow-up rules, and nobody has decided what those should be. Buying a different one relocates that decision without making it, and the second implementation tends to arrive about a year later.

What a real constraint looks like

It is specific, and it survives being written down. There is no way to represent an opportunity that has not yet become a job. The lead sources that matter cannot be connected. The licensing model prices out the people who do the work, so the record is always second-hand. Where one of those holds, changing system is justified — and it gets named before it gets recommended.

Aevrion does not resell software and 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.

06 / WHERE AUTOMATION STOPS

Automation carries the sequence. It does not carry the judgment.

The test is whether somebody could defend the message out loud. A sequence still running after a customer has replied fails it immediately: they started a conversation and the business answered with a schedule.

So every sequence gets the conditions that end it before it gets any content — a reply, an acceptance, a decline, a request for time, an opt-out. Writing those first is what keeps a follow-up design from becoming a broadcast with a delay on it.

AI earns a place at the points where a person still reads the output: sorting an inbound message, pulling the detail out of a voicemail, drafting a reply somebody sends. It has none where a wrong answer reaches a customer with nobody in between.

07 / HOW AEVRION IMPLEMENTS

Six steps, and nothing is configured until the fourth.

  1. 01

    READ THE LAST HUNDRED INQUIRIES

    Not a workshop and not a process diagram — the records themselves, including the dead ones. A business describes the path it intends; the records show the path that happened, and the distance between the two is the work.

  2. 02

    WRITE THE RULES DOWN OUTSIDE THE SOFTWARE

    Classification, ownership, response expectations, stopping conditions. Kept in a document rather than in a settings screen, because this is the part that survives a change of platform and the part a new hire has to be taught.

  3. 03

    FIND THE CONSTRAINT BEFORE FINDING A TOOL

    If the rules can be expressed in what the business already runs, that is the answer. A replacement earns its cost only against a constraint somebody can state in one sentence.

  4. 04

    BUILD THE PATH, THEN THE EXCEPTIONS

    The ordinary case first, then everything that does not fit it — the duplicate, the reopened job, the customer who returns eleven months later. A build that handles only the happy path fails in its first busy week.

  5. 05

    REHEARSE ON WORK THAT ALREADY WENT WRONG

    Put the inquiries the business lost through the new process. If it would not have caught them, it is not finished — and that is cheaper to discover now than in production.

  6. 06

    LEAVE SOMEONE ABLE TO CHANGE IT

    A named person inside the business who holds the rules and knows what altering one affects. Without that, the configuration and the company drift apart until somebody proposes replacing the system again.

08 / DECISION SUPPORT

Questions home-service owners ask before anything else.

01Which trades has Aevrion actually built for?

Two have published pages: garage door and HVAC. Garage door is the deeper of the two — a hub, four service routes and an ungated checklist — and HVAC has a hub with two supporting articles. Other home-service trades share the same lead-flow shape and Aevrion is willing to work in them, but no page, engagement or result is claimed for any of them, and this page does not pretend otherwise.

02Is this lead generation or marketing?

No. Marketing produces the inquiry. Aevrion works on what happens operationally after one arrives — capture, classification, ownership, follow-up and recorded outcome. A shortage of inquiries and a shortage of booked jobs are different problems with different fixes, and automating the second will not solve the first.

03We already have a CRM or a field-service platform. Do we need another one?

Usually not. Before answering, write down the rules you would configure in a new system — the states, the owners, the stopping conditions. If they could be configured in the one you have, the one you have is not the problem, and buying another relocates the decision without making it. A second system is recommended only where a specific constraint blocks the work, stated in a sentence. Aevrion resells no software and takes no platform commission.

04Do you have to specialise in my trade to be useful?

The operating layer is largely the same across home services — capture, ownership, routing, estimate state, stopping conditions, outcome. What differs is the shape of the commercial motions underneath it, and that is established during the review from your own inquiry history rather than assumed from a template.

05Can you promise more booked jobs?

No, and a page that did should be read carefully. Aevrion publishes no client results in these trades because none exist to publish. What this work delivers is narrower and checkable: every handoff carries a name, every opportunity carries a state somebody else can read, and nothing sits without a next action. That is what makes conversion measurable — it is not itself a conversion claim.

06Where does automation stop?

At the first sign the customer is participating: a reply, an acceptance, a decline, a request for time, an opt-out. After that they are in a conversation and a scheduled message is an interruption. The judgement calls stay with people too — what an unusual job should cost, whether ageing equipment is worth repairing, how to answer somebody who is unhappy. The system's job is to get a person to those moments sooner, and better briefed, than they would have arrived on their own.

NEXT

Where this connects.

Bring one real inquiry that did not become a job — ideally a quote that went quiet. Aevrion works outward from that single case rather than from a template for your trade.

Request a lead-flow review