How the four layers of a heating growth stack connect

The four layers, briefly

Every heating growth stack has the same four layers, whatever the software brands.

• Capture is where a stranger becomes a contact: the website, the tracked phone numbers on it, click-to-text and email links, and the Google Business Profile.
• Record is where that contact is remembered: the CRM or field-service system, with one record per customer and every enquiry, quote and job attached.
• Demand is paid attention: Google Search campaigns, Local Services Ads where available, Performance Max, and Meta campaigns for retargeting and seasonal reminders.
• Proof is public trust: Google reviews, replies to them, and the places they are shown on the website and in ads.

Each layer can be good or bad on its own. What makes a stack is the information that moves between them. We call each of those movements a wire.

The five wires

Wires one and two do most of the work. Wires three and four create the loop that makes the stack cheaper to run over time. Wire five is what lets you report a figure like cost per sold job honestly.

Wire 1: source, from capture to record

When a homeowner calls from your website, the call-tracking number they dialled tells you which page or ad they came from. That information has to be written into the CRM record at the moment the record is created, automatically. If staff have to type it in, it will be missing on busy days, which in a heating company are exactly the days that matter.

For website clicks from Google Ads, the platform attaches a click identifier to the visit. Keeping that identifier with the lead is what later allows wire two to report back to the right campaign. For calls, the call-tracking tool keeps the equivalent record.

Test: open the last ten CRM records created from new enquiries. How many have a source filled in without anyone typing it?

Wire 2: outcome, from record to demand

This is the wire most heating stacks are missing. The ad platforms only know what you tell them. If you tell Google Ads that a "conversion" is any call longer than 60 seconds, it will find more 60-second calls, including existing customers, parts suppliers and people asking whether you service rental units.

When the CRM sends back events like "assessment booked", "sold" and "invoiced", with values, the platforms can learn which searches and audiences produce revenue. Google Ads supports importing offline conversions, and Meta has an equivalent; the exact method depends on your CRM. What matters is that the events are real stages in your pipeline and that they are sent consistently.

Test: in your ad account, look at what is counted as a conversion. If nothing downstream of the phone call is listed, wire two is cut.

Wire 3: completion, from record to proof

When a technician closes a job in the field app, or the office marks it as invoiced, that status change can trigger a review request by text, with an email backup. The request goes out the same day, names the technician and links straight to your Google review page.

This wire turns reviews from a habit into a process. It also catches complaints: a reply that signals a problem can create a task for the owner before the customer posts publicly.

Test: compare the number of jobs completed last month with the number of review requests sent. They should match.

Wire 4: display, from proof back to capture and demand

A review on your Google Business Profile helps on the map. The same review, shown on the matching service page of your website, helps the next visitor decide to call. Where Google's ad formats allow it, rating information can appear with your ads as well.

This wire is what closes the loop. More recent reviews raise conversion; higher conversion lowers cost per lead; lower cost per lead frees budget for more demand.

Test: look at your boiler or heat pump page. Is there a recent review about that kind of job on it?

Wire 5: cost, from demand back to record

Finally, the ad spend for each campaign has to meet the outcomes recorded in the CRM, in one report. That join is what lets you say, "Our furnace replacement campaign cost $4,200 last month and produced seven sold jobs, so $600 each." Without it, you have two sets of numbers that never meet.

Test: can you produce last month's ad cost per sold job, by service, in under ten minutes? If not, wire five isn't in place.

The life of one furnace lead

Here is the whole system working, as a sequence.

1. In early November, a homeowner in [City] searches for furnace replacement and clicks your ad.
2. They land on your furnace replacement page, read a recent review about a similar install, and tap to call the tracking number shown.
3. Call tracking logs the call with its campaign and keyword, and the CRM creates a record with the source filled in (wire 1).
4. The office books an in-home assessment. The CRM stage changes, and that event is sent to Google Ads (wire 2).
5. The quote goes out. Five days later, an automated reminder goes to the homeowner and a task goes to the salesperson.
6. The job is sold for $7,800. The "sold" event and its value go back to Google Ads (wire 2 again).
7. The install is completed and invoiced. A review request goes out that afternoon (wire 3).
8. The homeowner leaves a review, which appears on your profile and is added to the furnace page (wire 4).
9. At month end, the report joins campaign spend to the sold value (wire 5).

Every step happened without anyone remembering to do it. That is the difference between owning four tools and running a stack.

Build order

Build the wires in the order that data flows: capture, then record, then demand, then proof. Ads come third because they need wires one and two to learn properly. Proof can start at the same time as ads, once the CRM is marking jobs complete.

Our growth stack blueprint maps your current wires and the build order for your company. The stack math guide puts a dollar value on each broken wire, and finding the leak is a self-check you can run today. For the layers themselves, see CRM integration and paid ads.