Sheppard

Operating

Local Service Ads at the portfolio level: how PE-backed home services platforms should run LSAs

Local Service Ads have become the highest-intent paid channel in home services. At portfolio scale, the question isn't 'should we use them' — it's how to budget, verify, and bid across multiple entities, and how to defend cost-per-booked-job as the channel matures. Here's the framework.

By Chris SheppardMay 5, 202610 min read

Local Service Ads — Google's pay-per-lead service-business format — have become the highest-intent paid channel in home services. Searchers see verified providers, badge-marked Google Guaranteed icons, and instant call buttons. Conversion rates dwarf traditional search ads.

At portfolio scale, the question isn't whether to use them. It's how to budget, verify, and bid across multiple entities — and how to defend cost-per-booked-job as the channel matures and competition intensifies.

Why LSAs deserve a dedicated line in your marketing P&L

Most platforms still report LSA spend inside generic 'paid search' or 'Google.' That hides three things sponsors care about: the unit economics of the channel (which differ from search), the verification overhead (which scales with entity count), and the cannibalization with organic and paid search. Break LSA out as its own line, with cost-per-booked-job — not cost-per-lead — as the primary unit metric.

Per-brand vs. pooled budgeting

LSA budgets are managed at the location/profile level by default. At platform scale, the question is whether to set per-brand budget caps or pool budget across the portfolio. Per-brand caps preserve brand-level accountability and prevent one over-spending profile from draining the platform. Pooled budgets capture demand spikes more efficiently but require centralized monitoring. Most platforms above five portcos benefit from a hybrid: per-brand soft caps with platform-level reallocation authority during weather events or seasonal demand spikes.

Google Guaranteed at the entity level

Google Guaranteed verification — licensing, insurance, background checks — runs at the entity (LLC) level, not the brand level. For a multi-brand platform with separate operating entities per brand, each entity verifies separately. This is administratively meaningful: licensing renewals, insurance certificate updates, and background check expirations all need a calendar at HoldCo. A lapsed verification suspends the badge, which materially drops conversion rate.

LSA + paid search + organic: modeling overlap

When LSAs run alongside paid search and organic local pack listings, the platform can occupy three of the top result positions simultaneously. That's high visibility — and meaningful overlap. Sophisticated platforms model the cannibalization explicitly: what share of LSA-booked jobs would have come through organic or paid search anyway, and what's incremental? The answer determines whether to scale LSA aggressively or use it as a peak-demand pressure relief valve.

Dispute, recording, and the CSR feedback loop

Google charges for LSA leads on a per-call basis. Calls that aren't qualifying (wrong service, out of area, spam) can be disputed for credit. At low volume, disputes are an afterthought. At platform scale — hundreds of calls per week — disputes become a real EBITDA line. Build the workflow: CSR scores every call against dispute criteria, the operations lead disputes weekly, and the credits show up on the next month's invoice. Platforms running this discipline typically recover 8-15% of monthly LSA spend.

Benchmarks: cost-per-lead vs. cost-per-booked-job

LSA cost-per-lead has risen materially in 2025-2026 across HVAC, plumbing, and electrical — driven by increased competition and Google's bid-tier model. Cost-per-booked-job is the metric that matters: the ratio between leads and booked jobs varies meaningfully by trade, by CSR quality, and by service mix. Track and report cost-per-booked-job by brand and by trade against platform benchmarks; cost-per-lead alone is misleading.

When to scale LSAs and when to throttle

Scale when cost-per-booked-job is below the marginal job profitability threshold and capacity exists to dispatch incremental work. Throttle when capacity is constrained (over-booked techs lower customer satisfaction, which hits reviews, which hits LSA conversion in a feedback loop). The platforms that run LSAs best treat them as a capacity-aware demand channel — not as an always-on growth lever.

LSAs are the channel where operational discipline shows up directly in marketing efficiency. The platforms that win are the ones whose dispatch and CSR teams understand the channel, not just whose marketing teams do.

Frequently Asked

More on operating.

How does Google Guaranteed verification work for a multi-entity platform?

+
Verification runs at the entity (LLC) level. Each operating entity in a multi-brand platform verifies separately — licensing, insurance, background checks. Renewals, insurance certificate updates, and background check expirations need a centralized calendar at HoldCo. A lapsed verification suspends the Google Guaranteed badge and materially drops LSA conversion rate.

Should LSA budget be set per-brand or pooled at the platform?

+
Hybrid: per-brand soft caps with platform-level reallocation authority. The caps preserve brand accountability and prevent runaway spend on a single profile; the centralized authority lets the platform capture demand spikes (heat domes, cold snaps, weather events) by reallocating budget where it matters most that week.

What's a healthy LSA cost-per-booked-job benchmark?

+
Varies meaningfully by trade. HVAC tends to run 1.5-3x cost-per-lead, plumbing 1.2-2x, electrical 2-4x — driven by lead-to-job conversion rates and service-mix economics. Cost-per-lead alone is misleading; cost-per-booked-job is the metric that ties to platform unit economics.

How do LSAs cannibalize organic and paid search?

+
Materially, when all three appear in the same SERP. Sophisticated platforms model overlap explicitly: what share of LSA-booked jobs would have come through organic or paid search regardless. The answer determines whether LSA is incremental demand or shifted demand — and that determines bid strategy.

How do you dispute LSA charges at scale?

+
Build a CSR-driven workflow: every call is scored against dispute criteria (wrong service, out of area, spam, duplicate), the operations lead disputes weekly through Google's interface, credits appear on the next monthly invoice. Platforms running disciplined dispute workflows typically recover 8-15% of monthly LSA spend.

Engage Sheppard

Have a deal that needs this work?

Pre-LOI, post-close, mid-hold, or pre-exit — the conversation starts with five questions and fifteen minutes on the calendar.