When the scope ran
2026 build and launch; paid-media performance period is not published
Published baseline
The public case does not publish a before/after paid-media baseline.
What needed to change
Turn local service demand into a clear estimate path with service-area context and reliable lead routing.
How this case is classified
Local service website and campaign-ready funnel. The case is not labeled paid-ad performance without a platform and lead-source export.
Exact Nexus Ads scope
- Local offer and service structure
- Estimate funnel
- Lead routing
- Campaign source and landing foundations
Estimate and contact actions were structured for source and lead review.
System implementation evidence — no published paid-performance claim
This case verifies a live implementation and the documented Nexus Ads scope. It does not claim advertising performance without an approved campaign export and lead-source record.
Evidence required before publishing a media-performance claim
- Approved advertising spend and an exact comparison date range
- Lead count plus the written definition of a qualified lead
- CPL or CPA formula with the included cost boundary
- Attribution source, model and conversion window
- Redacted screenshots or exports from the ad platform, GA4 and CRM
- Client approval for the figures, context and publication date
A live local-service acquisition system with a clear estimate route. Client-specific lead totals remain unpublished.
Source: Public live site and documented implementation scope.
Limitations: Seasonality, ad spend, attribution and lead totals are not public, so causal campaign claims are excluded.
Last verified: 2026-07-13
[ next step ]