Question 1

What does done-for-you multi-location Google Business Profile governance actually deliver?

Accepted Answer

Completions builds and operates a Google Business Profile governance bundle on the GBP agent for multi-location retailers, multi-unit restaurant operators, and franchise systems running 50-1,500 locations across multiple ownership-model variants (corporate, single-unit franchisee, multi-unit franchisee, area-developer, joint-venture, operator-employee). Attribute management: hours, services, categories, amenities, payment methods, parking, and accessibility attributes synchronized to the operator master record through the operator GBP-management vendor of record (Yext, Uberall, BirdEye, ReviewTrackers, Rio SEO, Reputation.com, Whitespark, Synup, BrightLocal, Vendasta, Moz Local, or Localworks) where one is in place, or directly through the GBP API where the operator runs the integration in-house. Posting: offers, events, and updates drafted against the operator brand voice and posted at the per-location cadence determined by the autonomy-profile policy. Photo management: photo uploads, rotation, brand-guideline compliance, ADA Title III alt-text presence, and a portfolio-level de-duplication audit using a layered photo-similarity stack (perceptual hashes — pHash, dHash, aHash, wHash, ColorHash, BlockHash, crop-resistant hash — plus deep-learning embeddings from CLIP, DINOv2, SigLIP, SAM, and ImageBind) with EXIF cross-reference. Face-recognition through AWS Rekognition, Azure Face, Google Cloud Vision, or Clarifai supports former-employee opt-out where the operator runs the integration under operator-counsel-approved policy that respects Illinois BIPA, Texas CUBI, Washington H.B. 1493, and any other applicable biometric-privacy state law. Q&A response drafting: an LLM-as-judge ensemble (OpenAI GPT-5, Anthropic Claude Opus 4.7, Google Gemini Ultra, Mistral Large, Cohere Command R+, Meta Llama-3.1-405B) drafts responses against the brand-voice gate and the per-vertical compliance overlay before they ship to the GBP. Autonomy-profile enforcement: the autonomy-profile policy lives in the operator repo with attorney-approved per-franchisee per-attribute access-control rules, aligned to the operating agreement and FDD relationship, and the gate splits corporate-controlled, operator-controlled, and franchisee-controlled attributes accordingly. Suspension detection and recovery: monitors GBP signals, assembles per-state per-vertical evidence packs for reinstatement appeals, and routes through operator counsel as needed. Per-franchisee performance benchmarking: per-cohort z-score, relative-rank, and percentile trends with below-floor alerting and FDD Item 19 financial performance representation overlay applied to anything shared with franchisees or prospective franchisees. Cross-agent coordination with the citation-link-build, schema-audit-remediation, master-record-canonicalization, compliance-overlay-manager, and brand-spec-authoring siblings. Per-vertical compliance overlay covers FTC, Lanham Act, state-AG UDAP, ADA Title III, WCAG 2.1/2.2, HIPAA, FDA OPDP, DEA, state-licensing-board, state-cannabis Metrc, DISCUS, FDA tobacco, ATF, and state-financial where applicable; franchise-specific overlay covers FTC Franchise Rule, FDD Items 11, 12, 19, and 20, per-state franchise-relationship statutes, International Franchise Association policy, and per-franchisee franchise agreement terms. Operator owns the brand spec, the master record, the autonomy-profile policy, the operating agreement, the GBP credentials (per-location Manager and Owner roles), the GBP-management vendor credentials under operator billing, the photo library and brand-guideline style guide, the LLM-as-judge prompt library, the photo-similarity model code, the orchestration code, the compliance overlay rule library, and the audit trail. Completions owns the orchestration knowledge.

Question 2

Why is multi-location Google Business Profile governance typically operator-side rather than GBP-management-vendor- or LLM-vendor-shipped?

Accepted Answer

Six engineering surfaces sit between operator data infrastructure and a working GBP governance bundle, and they sit outside the design center of the GBP-management, photo-similarity, face-recognition, franchise-management, and LLM ecosystems that own the upstream and downstream primitives. Surface 1 — Attribute management with autonomy-profile enforcement: Yext, Uberall, BirdEye, ReviewTrackers, Rio SEO, Reputation.com, Whitespark, Synup, BrightLocal, Vendasta, Moz Local, and Localworks ship strong listing-sync and posting primitives but stop short of per-franchisee per-attribute access-control split across corporate, single-unit, multi-unit, area-developer, joint-venture, and operator-employee ownership-model variants aligned to the operating agreement and FDD relationship. Surface 2 — Portfolio-level photo de-duplication audit: pHash, dHash, aHash, wHash, ColorHash, BlockHash, crop-resistant hash, CLIP, DINOv2, SigLIP, SAM, and ImageBind ship strong similarity primitives but tying them into one audit pipeline calibrated to operator brand-guideline state is operator-side modeling. Surface 3 — Former-employee opt-out: AWS Rekognition, Azure Face, Google Cloud Vision, and Clarifai ship strong face-recognition primitives but governance around former-employee opt-out is operator-counsel-side because biometric-privacy state laws (Illinois BIPA, Texas CUBI, Washington H.B. 1493) constrain what biometric data can be collected, retained, and used. Surface 4 — Brand-voice-gated Q&A drafting: OpenAI GPT-5, Anthropic Claude Opus 4.7, Google Gemini Ultra, Mistral Large, Cohere Command R+, and Meta Llama-3.1-405B ship strong drafting primitives but brand-voice gating and per-vertical compliance overlay calibration are operator-side modeling. Surface 5 — Suspension detection and recovery: per-state per-vertical evidence-pack assembly and reinstatement appeal drafting under Google Business Profile Terms of Service is operator-counsel-side process work. Surface 6 — Cross-franchisee coordination and FDD overlay: FranConnect, Naranga, and IFX Online ship strong franchisee-communication primitives but treat GBP governance as out-of-scope; FTC Franchise Rule, FDD Items 11, 12, 19, and 20, per-state franchise-relationship statutes, International Franchise Association policy, and per-franchisee franchise agreement terms 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 ($10k, 2-3 weeks, diagnostic): audits the six surfaces above against the operator stack — which GBP-management vendor sits in front of GBP today, which photo-similarity stack and face-recognition vendor (if any) handle photo governance, which franchise-management platform holds the franchisee directory and operating agreement, which LLM-as-judge models are accessible, where the per-vertical compliance overlay needs counsel review, and where the FDD overlay needs per-state review against Items 11, 12, 19, and 20. Tier 2 AI Swarm Setup Sprint ($25-50k, 4-8 weeks): builds the GBP governance bundle on the GBP agent, with the autonomy-profile policy reviewed by operator counsel against the operating agreement and FDD relationship, and the per-vertical compliance overlay rule library reviewed by operator counsel per vertical. Tier 3 Fractional CMO with AI Swarm ($15-25k/month, 6-month minimum, 1-2 days/wk embedded): continues operating the bundle end-to-end and coordinating with the adjacent citation-link-build, schema-audit-remediation, master-record-canonicalization, compliance-overlay-manager, and brand-spec-authoring skills.

Question 4

Who owns the brand spec, autonomy-profile policy, operating agreement, and GBP credentials during engagement?

Accepted Answer

Operator owns 100% of every artifact. The brand spec is versioned in the operator repo with brand-spec-version-pin tone, formality, empathy, and channel-format knobs. The autonomy-profile policy is versioned in the operator repo with attorney-approved per-franchisee per-attribute access-control rules and is FDD-relationship-aligned. The operating agreement is operator-owned and operator-counsel-maintained. GBP credentials (per-location Manager and Owner roles) are owned by the operator with per-franchisee role assignment under the autonomy-profile policy; Completions accesses via operator-granted permissions that the operator can revoke at any time. GBP-management vendor credentials (Yext, Uberall, BirdEye, ReviewTrackers, Rio SEO, Reputation.com, Whitespark, Synup, BrightLocal, Vendasta, Moz Local, Localworks) sit under operator billing. Franchise-management vendor credentials (FranConnect, Naranga, IFX Online) sit under operator billing. The master record sits in operator data infrastructure (Snowflake, BigQuery, Databricks, Redshift, or Postgres). The compliance overlay rule library lives in the operator repo with attorney-approved updates and tracks Google Business Profile Terms of Service, FTC, Lanham Act, state-AG UDAP, ADA Title III, WCAG 2.1/2.2, HIPAA, FDA OPDP, DEA, state-licensing-board, state-cannabis Metrc, DISCUS, FDA tobacco, ATF, state-financial, FTC Franchise Rule, FDD Items 11/12/19/20, per-state franchise-relationship statutes, International Franchise Association policy, per-franchisee franchise agreement terms, Illinois BIPA, Texas CUBI, and Washington H.B. 1493 where applicable. The photo library and brand-guideline style guide sit in operator storage. The photo-similarity model code, the orchestration code, and the LLM-as-judge prompt library live in the operator repo with operator-controlled deploy pipeline. LLM API credentials (OpenAI, Anthropic, Google, Mistral, Cohere, Meta) and face-recognition API credentials (AWS Rekognition, Azure Face, Google Cloud Vision, Clarifai) sit under operator billing. The audit trail persists to operator-controlled WORM storage (AWS S3 Object Lock, Google Cloud Storage retention, Azure Blob immutable, or Snowflake Time Travel) where SEC, FINRA, SOX, state-AG, or state franchise-registrar retention rules require it. Completions owns the orchestration knowledge — how to design the autonomy-profile policy, how to tune brand-voice-gated Q&A drafting, how to debug suspension cascades, and how to coordinate with the citation-link-build, schema-audit-remediation, master-record-canonicalization, compliance-overlay-manager, and brand-spec-authoring 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 GBP agent: (1) Attribute + Posting workstream — pre-engagement baseline of which attributes drift today, which posts ship at which cadence per location, and how the autonomy-profile policy is enforced across franchisee ownership-model variants, then weekly reporting on attribute coverage against the master record, post cadence per autonomy profile, and autonomy-profile policy violations caught before they ship. (2) Photo-Governance workstream — pre-engagement baseline of which photos sit in the portfolio today, what brand-guideline compliance looks like, and which photos may need former-employee opt-out review under operator-counsel policy, then weekly reporting on de-duplication audit outcomes, brand-guideline compliance, ADA Title III alt-text presence, and former-employee opt-out events processed where the operator runs the face-recognition integration. (3) Q&A + Brand-Voice workstream — pre-engagement baseline of Q&A response cadence and brand-voice fit today, then weekly reporting on draft volume, brand-voice gate pass rates, editorial-routing volume, and operator-brand-team disagreement signals. (4) Suspension Detection + Recovery workstream — pre-engagement baseline of GBP signal monitoring and reinstatement-appeal capacity today, then weekly reporting on suspension events detected, evidence packs assembled, counsel-routing latency, and reinstatement outcomes. (5) Per-Vertical Compliance + FDD Overlay workstream — pre-engagement baseline of which frameworks are attorney-approved today across GBP Terms of Service, FTC, Lanham Act, state-AG UDAP, ADA Title III, WCAG 2.1/2.2, HIPAA, FDA OPDP, DEA, state-licensing-board, state-cannabis Metrc, DISCUS, FDA tobacco, ATF, state-financial, FTC Franchise Rule, FDD Items 11/12/19/20, per-state franchise-relationship statutes, IFA policy, per-franchisee franchise agreement, Illinois BIPA, Texas CUBI, and Washington H.B. 1493, then weekly reporting on overlay completeness, rule-update lag, and counsel re-review state. (6) Per-Franchisee Performance + Cross-Agent Coordination workstream — pre-engagement baseline of per-franchisee performance reporting today, then weekly reporting on per-cohort z-score, relative-rank, and percentile trends with FDD Item 19 overlay applied to anything shared with franchisees, and coordination state with the citation-link-build, schema-audit-remediation, master-record-canonicalization, compliance-overlay-manager, and brand-spec-authoring siblings. Caveats: Google Business Profile policy and Terms of Service change without notice and require Completions to update orchestration and prompt libraries on detection; GBP API rate limits, deprecations, and pricing changes are Google decisions outside Completions control; GBP-management vendor API and pricing changes are outside Completions control; LLM-vendor API rate limits, model deprecation, and pricing changes are outside Completions control; face-recognition vendor API changes and biometric-privacy state-law changes (Illinois BIPA, Texas CUBI, Washington H.B. 1493) require operator-counsel re-review; per-vertical regulator policy 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; suspension recovery outcomes depend on Google policy decisions outside Completions control; 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 attribute management, posting, photo governance with de-duplication and former-employee opt-out, Q&A response drafting with brand-voice gate, autonomy-profile enforcement, suspension detection and recovery, per-vertical compliance overlay management, FDD overlay management, and per-franchisee performance benchmarking + brand spec hand-off + autonomy-profile policy hand-off + GBP credentials remain operator-owned (Completions permissions revoke immediately) + GBP-management vendor credentials hand-off + franchise-management vendor credentials hand-off + LLM API credentials hand-off + face-recognition API credentials hand-off + photo-similarity model code hand-off + orchestration code hand-off + LLM-as-judge prompt library hand-off + compliance overlay rule library hand-off + audit-trail hand-off with WORM-storage operator-account-ownership confirmation; Completions credentials revoke immediately on engagement-end and the attorney relationship continues unbroken.

Frequently asked