From Lead to Paying Customer: Marketing Diligence for Home Services

Start with a question the records can answer

Choose an acquisition cohort: people whose first qualifying inquiry arrived between two stated dates. Then choose an observation end through which first bookings, first completed jobs and payments can be recognized. A July inquiry paid in September belongs to that July cohort under this convention. September cash divided by September advertising expense mixes populations unless the lag has been reconciled. Compare cohorts with similar follow-up windows and service mix.

Define a new customer at the business level. A second service address, a repeat maintenance visit or a new phone number for an existing household can create duplicates. Preserve anonymous customer and inquiry references in the analysis; keep names, telephone numbers and recordings in the private system of record. Document the treatment of prior customers, multi-property accounts, cancellations and requests outside the service area.

Use one first journey per customer

The companion tool requires inquiries ≥ qualified leads ≥ first bookings ≥ first completions ≥ new paying customers. This is a defined first-journey funnel. A general dispatch report with repeated appointments or multiple jobs cannot be inserted without transformation. The constraint tests internal consistency; it does not prove that a call was qualified or that a receipt was matched correctly.

Google describes qualified and converted leads as advertiser-defined stages and supports importing later offline events. Those product labels do not independently establish a new paying customer. Save the configured conversion-action definitions and attribution settings beside the CRM-to-work-order-to-cash reconciliation. An account access handoff and an economics review are separate tasks; use the existing digital asset handoff guide for ownership and access.

Match acquisition cost to the same population

List media charges net of actual credits, agency retainers, campaign production, call handling or sales effort, and other supported acquisition costs. State the allocation period and whether a shared retainer serves acquisition, existing customers or brand activity. A whole-company salary cannot be assigned in full to each channel. Document a reasoned allocation and retain the unallocated balance. An entered zero means zero included cost; it cannot stand for an unknown invoice.

Mark the cost scope partial when an expense category is unresolved. The tool still calculates the entered-cost ratio and carries that warning. Do not describe it as a fully loaded customer acquisition cost. Separate one-time setup from recurring operating costs and show both if relevant. This avoids presenting a temporary low invoice as a sustainable annual run rate.

A two-channel example with reconciled first-job cash

The cohort runs July 1–31, with observation through September 30, 2026. Receipts exclude pass-through tax. Direct job cost covers the stated cohort delivery, including unpaid completions. Channel B has a lower acquisition-cost ratio, while Channel A has more first-job contribution dollars after acquisition spending in this example. Neither result establishes which channel should receive the next dollar: service mix, available capacity, cost completeness and incremental response remain unknown.

If these are nonoverlapping customer populations and nonduplicated costs, combined acquisition cost is $6,100 for 22 new paying customers, or $277.27 each. Combined net receipts are $15,800; less $7,100 delivery cost and $6,100 acquisition cost leaves $2,600 before other common costs. The tool suppresses combined totals until the user declares that populations, receipts and costs do not overlap. A person who clicked two ads must not become two customers in the total.

Resolve exceptions before scaling the conclusion

Keep a queue for unmatched calls, bookings without source evidence, receipts without work orders, source changes and duplicated contacts. Reconcile the total count and dollar population, the tested portion and the unresolved remainder. For example, 80 matched records in a 100-record export are 80% count coverage, not proof that 80% of spend or cash was reviewed. Report each denominator separately. Do not silently allocate the remainder to the best-performing source.

Refunds can exceed the entered first-job receipts where timing or scope differs. The tool preserves that negative result and flags it for review rather than forcing a positive return. A zero-customer channel retains its acquisition spending and contribution loss; its cost-per-customer ratio is unavailable. Later maintenance revenue, repeat jobs and referrals require separately observed cohorts. First-job contribution is not lifetime value, verified EBITDA, return on ad spend or a causal estimate of advertising effectiveness.

Create a repeatable review file

1. Freeze the inquiry cohort, observation date and stage definitions.
2. Reconcile anonymous lead, customer, work-order and cash references.
3. Assign each cost once and document missing or shared costs.
4. Review exceptions and disclose unmatched population coverage.
5. Run the customer acquisition tool and retain its private export with evidence.
6. Connect capacity and job-cost questions to the pricing model; connect later cash to the collection review without counting it twice.

Sources and scope

Source links support the specific topics noted. Examples and analytical frameworks are illustrative; confirm current requirements and transaction facts with the responsible advisers.

1. Google Ads — Qualified and converted leads
   Platform lead stages depend on the conversion actions configured by the advertiser. A reported conversion is not independently verified new-customer cash. Our cohort definitions and examples are original; no account connection or tracking implementation is supplied.
2. Google Ads — Offline conversion imports
   Supports the distinction between an online interaction and later offline outcomes. Current product migration notices were reviewed; this guide does not give an API setup recipe or imply an existing account integration.