Projects  /  Execution Partner

Knowing which advertising actually made the phone ring.

An operating platform for home-services businesses — the phone, the follow-up and the numbers in one system. Our recent work has been the reporting layer: matching every inbound call and click to a customer record so paid spend can be judged against outcomes.

Sector
Home services
Improvement area
Marketing spend and attribution
Built on
Atlas HQ, the platform we develop and operate
Status
In active development, in production

Context

Home-services businesses — roofing, restoration, HVAC and the like — live and die on the phone. The work arrives as a call or a form fill, gets followed up or does not, and turns into a job or does not. Most of the money is spent buying those calls.

Execution Partner runs that loop: inbound calls, the follow-up, the pipeline and the reporting, in one place rather than across a phone system, a CRM and an ad account that never agree with each other.


The bottleneck

Paid search reports leads. Leads are not customers. A large share of the calls attributed to brand campaigns are existing customers who searched the company name because that is how they find the number — and counting them as acquisition makes the cheapest-looking campaign the one that mostly bought traffic the business already had.

Without a link from the click or the call back to the customer record, there is no way to separate the two, so the spend question never resolves. Owners were making budget decisions on a number that quietly included their own repeat business.


What we built

  • Match on arrival. Every inbound click and call is matched to a customer record the day it lands, rather than reconciled later from exports.
  • New versus returning, separated. The report distinguishes a first-time caller from a customer the business already had, so acquisition and repeat demand are never summed into one figure.
  • Outcome, not volume. Sources are reported against what happened — matched, new, booked — instead of against raw lead counts.
  • One system. The call, the follow-up thread and the job sit on the same record, so the reporting is built from operations rather than from a separate analytics pipeline.

Where it stands

Measured

  • No quantified outcome has been supplied for this engagement. We are not putting a percentage on it.

Delivered and in use

  • Attribution from ad click or inbound call through to the matched customer record
  • New and returning customers reported separately
  • Spend reported against booked work rather than lead volume

Human responsibility

Execution Partner is a product with its own customers, built on Atlas HQ — the multi-tenant platform we develop and operate. It is a different thing from the consulting engagements described elsewhere on this site: there, we work inside your business and you own what we build. Here, we run the platform.

We include it because the engineering is ours and the problem is a good example of the kind we take on.


Something in your operation that works like this?

Tell us how it runs today, and we’ll look at what an improvement could be worth.