Question 1

What does done-for-you franchise Google Ads governance and per-location geo-targeting actually deliver?

Accepted Answer

Completions builds and operates a franchise paid-search and paid-social governance bundle on the local-sem agent for multi-unit franchisors and multi-brand franchise systems running 50-1,500 franchisees. Per-service-area geo-targeting: maps each franchisee territory out of the operator FDD Item 12 territorial-protection register into platform-native geo-targeting across Google Ads, Microsoft Ads, Meta Ads, TikTok Ads Manager, and LinkedIn Ads using zip, county, CBSA, DMA, Nielsen DMA, state, radius-circle, polygon, drive-time, walk-time, and transit-time dimensions, with polygon geometry from Esri Business Analyst, Tango Analytics, Buxton, Pitney Bowes, Mapbox, Google Maps Platform, or HERE. FDD territorial-protection gating: detects radius-overlap, drive-time-overlap, and polygon-overlap between franchisee territories before campaigns ship so the gating runs against the FDD territorial-protection register rather than after-the-fact reconciliation in a franchisee-council meeting. Per-franchisee budget allocation: the policy lives in the operator repo with attorney-approved per-cohort, per-vertical, per-LTV, and per-tenure rules and runs against the operator marketing-fund accounting (FDD Item 11 Franchisor Assistance and Item 6 Other Fees disclosed). Per-location keyword universe: keyword research per franchisee per territory with per-location-aware adaptation versioned in the operator repo. Per-location ad-copy generation: a multi-model LLM ensemble (OpenAI GPT-5, Anthropic Claude Opus 4.7, Google Gemini Ultra, Mistral Large, Cohere Command R+, Meta Llama-3.1-405B) drafts ad variants with brand-voice gating and per-vertical compliance overlay applied before each variant ships to the platform. Cross-platform bid orchestration: SA360, Marin, Skai, Adobe Advertising Cloud, Optmyzr, and Adalysis manage bids where the operator runs them; the orchestration emits bid adjustments back through those tools rather than bypassing them. Per-vertical compliance overlay: where the franchise vertical is regulated, HIPAA, FDA OPDP, DEA, state licensing boards, state- Metrc, DISCUS, FDA tobacco, ATF, and state-financial rules apply; FTC and state-AG UDAP rules apply universally. Per-franchisee performance benchmarking with FDD Item 19 financial performance representation overlay: per-cohort z-score, relative-rank, and percentile trends with below-floor alerting to the operator marketing team and franchisee council, with FDD Item 19 disclosure rules constraining what comparative-performance data can be shared with prospective franchisees. Per-event bid pause/resume: coordinates with the operator inventory state, license-lapse signal, and crisis-detection signal so bids pause and resume on real-world events. Call tracking coordination: CallRail, Invoca, DialogTech, and CallTrackingMetrics feed back attribution to the per-franchisee performance benchmark. Local-listing coordination: Yext, Uberall, BirdEye, and ReviewTrackers anchor the geo-targeting to canonical NAP and GBP. Operator owns every platform credential (Google Ads, Microsoft Ads, Meta Ads, TikTok Ads, LinkedIn Ads, SA360, Marin, Skai, Adobe Advertising Cloud, Optmyzr, Adalysis, Esri Business Analyst, Tango Analytics, Buxton, Pitney Bowes, Mapbox, Google Maps Platform, HERE, FranConnect, Naranga, IFX Online, CallRail, Invoca, DialogTech, CallTrackingMetrics, Yext, Uberall, BirdEye, ReviewTrackers) under operator billing, the FDD territorial-protection register in the operator repo, the per-franchisee budget allocation policy with attorney-approved rules, the per-location keyword universe, the brand spec, the compliance overlay rule library, the orchestration code, the LLM prompts, and the audit trail. Completions owns the orchestration knowledge.

Question 2

Why is franchise Google Ads governance typically operator-side rather than ad-platform- or bid-vendor- or franchise-management-vendor-shipped?

Accepted Answer

Six engineering surfaces sit between operator data infrastructure and a working franchise paid-search and paid-social governance bundle, and they sit outside the design center of the ad-platform, bid-management, geo-and-trade-area, franchise-management, call-tracking, local-listing, and LLM ecosystems that own the upstream primitives. Surface 1 — Per-service-area geo-targeting against FDD Item 12 territorial protection: Google Ads, Microsoft Ads, Meta Ads, TikTok Ads Manager, and LinkedIn Ads ship strong geo-targeting primitives but treat franchise territory geometry as a manual setup; Esri Business Analyst, Tango Analytics, Buxton, Pitney Bowes, Mapbox, Google Maps Platform, and HERE ship strong polygon and drive-time primitives but tying them to per-franchisee FDD Item 12 boundaries is operator-side modeling. Surface 2 — FDD territorial-protection gating with radius, drive-time, and polygon overlap detection before campaigns ship is operator-side modeling that has to be reconciled with operator counsel. Surface 3 — Per-franchisee budget allocation: the per-cohort, per-vertical, per-LTV, and per-tenure rules and the FDD Item 11 Franchisor Assistance and Item 6 Other Fees disclosure language are operator-counsel-side. Surface 4 — Cross-platform bid orchestration: SA360, Marin, Skai, Adobe Advertising Cloud, Optmyzr, and Adalysis ship strong bid primitives but multi-franchisee FDD-aware coordination is operator-side. Surface 5 — Per-location ad-copy with brand-voice gate and per-vertical compliance overlay: OpenAI GPT-5, Anthropic Claude Opus 4.7, Google Gemini Ultra, Mistral Large, Cohere Command R+, and Meta Llama-3.1-405B ship strong generation primitives but brand-voice and compliance calibration are operator-side. Surface 6 — Per-event coordination: call-tracking vendors (CallRail, Invoca, DialogTech, CallTrackingMetrics), local-listing vendors (Yext, Uberall, BirdEye, ReviewTrackers), and franchise-management vendors (FranConnect, Naranga, IFX Online) each ship strong primitives but stitching inventory state, license-lapse, crisis-detection, and call-attribution into a single bid pause/resume signal is operator-side event-driven architecture. FTC Franchise Rule, FDD Items 11/12/19/20, per-state franchise-relationship statutes, International Franchise Association policy, per-franchisee franchise agreement terms, and state-AG UDAP are operator-counsel-side. Completions runs orchestration across all six surfaces under one Tier 3 Fractional CMO with AI Swarm engagement; operator owns the artifacts and can in-house at any time.

Question 3

What does the engagement look like across Tier 1, Tier 2, and Tier 3?

Accepted Answer

Tier 1 AI Readiness Assessment (2-3 weeks, diagnostic): audits the six surfaces above against the operator stack — which ad platforms run today, which bid-management tool sits on top, which geo-and-trade-area vendor anchors territory geometry, which franchise-management platform holds the franchisee directory, which call-tracking and local-listing vendors close the loop, where the FDD Item 12 territorial-protection register lives today, and where the per-vertical compliance overlay needs counsel review against FDD Item 19 financial performance representation rules and state-AG UDAP. Tier 2 AI Swarm Setup Sprint (4-8 weeks): builds the governance bundle on the local-sem agent, with the per-franchisee budget allocation policy reviewed by operator counsel and the FDD Item 19 + Item 20 overlay reviewed per-state. Tier 3 Fractional CMO with AI Swarm (6-month minimum, 1-2 days/wk embedded): continues operating the bundle end-to-end and coordinating with the adjacent brand-spec-authoring, compliance-overlay-manager, location-benchmarking, master-record-canonicalization, and inventory-aware-marketing skills.

Question 4

Who owns the platform credentials, FDD register, and audit trail during engagement?

Accepted Answer

Operator owns 100% of every artifact. Platform credentials (Google Ads, Microsoft Ads, Meta Ads, TikTok Ads Manager, LinkedIn Ads) sit under operator billing. Bid-management credentials (SA360, Marin, Skai, Adobe Advertising Cloud, Optmyzr, Adalysis), geo-and-trade-area credentials (Esri Business Analyst, Tango Analytics, Buxton, Pitney Bowes, Mapbox, Google Maps Platform, HERE), franchise-management credentials (FranConnect, Naranga, IFX Online), call-tracking credentials (CallRail, Invoca, DialogTech, CallTrackingMetrics), and local-listing credentials (Yext, Uberall, BirdEye, ReviewTrackers) all sit under operator billing. The FDD territorial-protection register is operator-owned and operator-counsel-maintained with per-state per-franchisee territory geometry. The per-franchisee budget allocation policy is versioned in the operator repo with attorney-approved per-cohort per-vertical per-LTV per-tenure allocation rules. The brand spec is versioned in the operator repo. The compliance overlay rule library lives in the operator repo with attorney-approved updates and tracks FTC Franchise Rule, FDD Item 11 Franchisor Assistance, FDD Item 12 Territorial Protection, FDD Item 19 Financial Performance Representation, FDD Item 20 Outlet List, per-state franchise-relationship statutes, International Franchise Association policy, per-franchisee franchise agreement terms, state-AG UDAP, and the per-vertical regulator set where applicable (HIPAA, FDA OPDP, DEA, state-licensing-board, state- Metrc, DISCUS, FDA tobacco, ATF, state-financial). The per-location keyword universe lives in the operator repo with monthly refresh. The per-location ad-copy library lives in the operator repo with brand-spec-pinned knobs. The orchestration code lives in the operator repo with operator-controlled deploy pipeline. The LLM prompts live in the operator repo. LLM API credentials (OpenAI, Anthropic, Google, Mistral, Cohere, Meta) sit under operator billing. The audit trail persists to operator-controlled WORM storage where SEC, FINRA, SOX, state-AG, or state franchise-registrar retention rules require it. Completions owns the orchestration knowledge — how to design per-service-area geo-targeting, how to tune FDD territorial-protection gating, how to debug per-franchisee budget allocation cascades, and how to coordinate with the brand-spec-authoring, compliance-overlay-manager, location-benchmarking, master-record-canonicalization, and inventory-aware-marketing siblings. The operator can in-house at any time; Completions credentials revoke immediately on engagement-end.

Question 5

What does Completions commit to on a Tier 3 engagement?

Accepted Answer

Completions commits to a 6-workstream pre-engagement-baseline reporting cycle on the local-sem agent: (1) Geo-Targeting + FDD-Protection workstream — pre-engagement baseline of how franchisee territories map into platform geo-targeting today and where overlaps surface, then weekly reporting on per-service-area coverage and overlap-detection events caught before campaigns ship. (2) Budget-Allocation workstream — pre-engagement baseline of how corporate-fund and franchisee-fund spend is allocated today, then weekly reporting on per-cohort, per-vertical, per-LTV, and per-tenure adherence with FDD Item 11 and Item 6 disclosure overlay. (3) Ad-Copy + Brand-Voice workstream — pre-engagement baseline of brand-voice fit across ad copy today, then weekly reporting on brand-voice gate pass rates and operator-brand-team disagreement signals. (4) Cross-Platform Bid Orchestration workstream — pre-engagement baseline of which bid-management tool the operator runs and how it coordinates with platform-native automation today, then weekly reporting on bid adjustments shipped, platform-policy events caught, and operator-finance-team-aligned ROAS reporting. (5) Per-Vertical Compliance + Per-Event Pause/Resume workstream — pre-engagement baseline of which frameworks are attorney-approved today (FTC + state-AG UDAP universally; HIPAA + FDA OPDP + DEA + state-licensing-board + state- Metrc + DISCUS + FDA tobacco + ATF + state-financial where applicable), then weekly reporting on overlay completeness and bid pause/resume events from inventory, license-lapse, and crisis-detection signals. (6) Per-Franchisee Performance + FDD Item 19 workstream — pre-engagement baseline of how per-franchisee performance is reported today, then weekly reporting on per-cohort z-score, relative-rank, and percentile trends with FDD Item 19 disclosure overlay applied to anything shared with prospective franchisees. Caveats: ad-platform policy (Google Ads, Microsoft Ads, Meta Ads, TikTok Ads Manager, LinkedIn Ads) changes without notice and is outside Completions control; bid-management vendor API and pricing changes are outside Completions control; FDD Item 11, Item 12, Item 19, and Item 20 thresholds and disclosure rules are FTC and state franchise-administrator policy and can change; per-state franchise-relationship statutes, International Franchise Association policy, and state-AG UDAP can change and require operator-counsel re-review; per-vertical regulator policy (HIPAA, FDA OPDP, DEA, state-licensing-board, state- Metrc, DISCUS, FDA tobacco, ATF, state-financial) can change without notice; LLM-vendor API rate limits, model deprecation, and pricing changes are outside Completions control; franchisee territory geometry depends on operator FDD updates and counsel-approved registry changes; per-franchisee performance benchmarking shared with franchisees or prospective franchisees is operator-counsel-policy; the audit trail persists to operator-controlled storage on the operator cloud account.

Question 6

How does engagement end and what is the operator transition path?

Accepted Answer

Tier 3 engagements are 6-month minimum with 90-day notice. At engagement end, Completions transitions back to operator in-house in 30-60 days: operating-playbook hand-off + in-house staff training across 3-5 operator team members covering per-service-area geo-targeting, FDD territorial-protection gating, per-franchisee budget allocation, ad-copy generation, cross-platform bid orchestration, per-vertical compliance overlay management, per-event pause/resume coordination, per-franchisee performance benchmarking with FDD Item 19 overlay, and attorney-relationship continuity + platform credentials hand-off + bid-management credentials hand-off + geo-and-trade-area credentials hand-off + franchise-management credentials hand-off + call-tracking credentials hand-off + local-listing credentials hand-off + LLM API credentials hand-off + FDD territorial-protection register hand-off + per-franchisee budget allocation policy hand-off + per-location keyword universe hand-off + per-location ad-copy library hand-off + orchestration code hand-off + LLM prompts hand-off + compliance overlay rule library hand-off + audit-trail hand-off with operator-account-ownership confirmation; Completions credentials revoke immediately on engagement-end and the attorney relationship continues unbroken.

Frequently asked