An HVAC franchise network got city pages that finally matched their ads

Representative examplesEvery case study in this library is an illustrative composite of the kind of engagement we deliver — written to show our method and standards, not to name clients.

Where they started

Fourteen territories across climate zones make up this HVAC franchise network, run by owner-operators who know their towns and pay corporate for national advertising. The paid team at headquarters buys search in every territory; franchisees answer the phones. The arrangement works when the ad matches the driveway it lands in, and it was failing quietly: every click nationwide arrived at one page with one phone number and one seasonal offer. Franchise agreements gave corporate wide but not unlimited latitude over franchisee-facing pages, and two people maintained everything corporate owned.

What it was costing

Paid ads for fourteen cities all landed on one national page quoting one phone number and one set of seasonal offers. Franchisees paid for leads that referenced another city's weather and another territory's pricing, and the network's cost per booked tune-up kept rising.

What they could see

• A southern territory's spring ad landed on a furnace-tune-up page the north was still running.
• Franchisees forwarded complaints about ads quoting offers their territory had never priced.
• The paid team could not split performance by territory because every click landed on the same URL.
• Call tracking, where it existed at all, pooled into one national number nobody trusted.
• Launching a territory-specific campaign required a web team ticket, so nobody launched territory-specific campaigns.

The constraints we worked inside

• Franchise agreement limited how much corporate could change franchisee-facing pages without approval.
• Each territory had its own seasonal calendar — cooling in the south started weeks earlier.
• The paid team needed to launch territory campaigns without waiting on a web team.

What had been tried before

Corporate had the web team add a city-name line to the national page.

One swapped line under identical offers and proof did not fool anyone; franchisees still fielded calls about phone numbers and prices that were not theirs.

Territories were permitted to run their own local ads to franchisee-built pages.

Fourteen owners produced fourteen designs, most off-brand and several without compliant claim language; corporate quietly ended the experiment within a season.

The paid team paused the worst-performing territories each season to control spend.

Pausing cut spend and lead flow together, and the complaints escalated to the franchisee council — the problem was page fit, not territory viability.

What we proposed

Build territory pages from one governed template: corporate locks the brand and compliance regions, while each territory controls its own fields — city, phone number, seasonal offer, and the proof that matters in its climate. Offer switching follows each territory's climate calendar, so cooling markets open weeks before northern ones without anyone asking permission to be warm. Launch on the hottest territory first as a control, with per-territory tracking kept separate, so the network can see the difference instead of being asked to believe it.

Just as important is what we ruled out, and why:

• Fourteen independently designed territory pages — The earlier free-for-all had already failed on brand and compliance; governance was the lesson, and a template with locked regions is how it gets kept.
• Building the territory logic into the corporate website — The web team's backlog would make every territory launch a ticket; the paid team needed to ship campaigns at the pace of weather, not of sprints.
• One national page with geolocation auto-detection — Auto-detected content breaks caches and previews, and it keeps every offer decision central — exactly the authority dispute the template was designed to settle.

How the work ran

Delivered by the growth pod — strategist over 6 weeks, with working increments reviewed with the client every week.

The stack, and the reasoning

Unbounce

A governed template lets corporate lock the brand and compliance regions while territories edit their own fields — the network needed controlled localness, and this is the tooling shape of that.

DTR

Search terms carry local intent — cooling here, heating there — and DTR matches the page's service language to the query without maintaining a separate page for every service in every city.

Smart Traffic

Within a territory, emergency and maintenance intent arrive mixed; Smart Traffic routes to the variant that fits, which matters when the page's job is to produce a phone call within the hour.

Call tracking

Territory numbers proved what franchisees had asserted for years — call volume and quality vary by page — and gave the network per-territory evidence instead of dueling anecdotes.

What went wrong

How we worked together

Cadence

A weekly 30-minute call with the paid lead and the franchise operations manager; the pilot territory's dashboard went to the franchisee council every Friday.

Client side

The paid lead owned the template and the campaigns; the operations manager owned franchisee approvals; the pilot territory's owner-operator reviewed her page's copy personally.

Decisions

Corporate decided structure and locked regions; territories decided their own fields — the split was written into the field dictionary so every argument had a home.

They provided

The franchise agreement's page clauses, each territory's seasonal calendar, phone-system access for tracking, two franchisee interviews, and the pilot owner's review time.

What changed

The headline: cost per booked tune-up across the network versus the prior season — −29%, read from Call tracking plus booking records. A second check: landing-page-to-call progression in the pilot territory at +44%.

The arguments moved from principle to spreadsheet. Franchisees see their own territory's calls and can trace a slow week to an offer, a season, or a headline — and they bring that evidence to council meetings instead of grievances. The paid team launches a territory campaign in an afternoon, in season, with the right phone number on the page. The pilot owner's page answers her town's weather, her prices, and her number, which is all she had been asking for — and the other thirteen now ask when theirs arrives.

The result was read from Call tracking plus booking records against the pre-engagement baseline over the stated window, with a guardrail check on landing-page-to-call progression in the pilot territory. Where platform-reported numbers and business outcomes differ, this record says which layer it is quoting.

What they own now

• The governed Unbounce template with locked regions and the territory field dictionary.
• The climate-calendar switch schedule covering all fourteen territories.
• Per-territory call tracking with numbers mapped and forwarding verified.
• A franchisee onboarding one-pager covering what they can edit and how.
• The pilot territory's dashboard, replicated for the remaining thirteen.