Question 1

What does done-for-you per-location link outreach across franchise locations actually deliver?

Accepted Answer

Completions builds and operates a per-location link outreach bundle on the citation-link-build agent for multi-unit franchisors and multi-location service brands running 50-1,500 franchise locations across multiple DMAs and verticals. Per-location prospect discovery: prospects are identified from local-context surfaces shaped to each franchisee territory — per-DMA local publications, chamber-of-commerce directories, per-vertical trade publications, local-school directories, per-municipal-government directories, local news outlets, and event-sponsorship surfaces fed by PredictHQ, Eventbrite, and Ticketmaster. Personalized outreach drafting: every outreach draft passes through the operator 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) calibrated to the operator brand spec and per-prospect context (prior content, recent news, local-context tie-ins, per-prospect brand-voice adaptation). Per-vendor volume-cap enforcement: outreach volume runs through the operator outreach-platform of record (Pitchbox, BuzzStream, NinjaOutreach, Hunter, Mailshake, Lemlist, Outreach, Reply.io, Respona, Postaga, Snov.io) with per-vendor caps that respect TCPA prior-express-written-consent on SMS routes, CAN-SPAM unsubscribe register on email routes, 10DLC campaign and CTIA A2P registration on SMS where the operator runs SMS through Twilio, Attentive, or Postscript, CASL where the operator markets into Canada, UK PECR and EU ePrivacy where the operator markets into the UK or EU, and state-AG UDAP plus state-SHIELD per state where the operator markets. Per-location sender-reputation management: per-domain dedicated IP allocation, per-domain warming schedule, DMARC/DKIM/SPF authoring through the operator DNS (Cloudflare, Route 53, Google Cloud DNS, Azure DNS), inbox-placement monitoring through SenderScore, Google Postmaster Tools, Microsoft SNDS, Talos Intelligence, Spamhaus, and Barracuda Central, and bounce-rate and complaint-rate tracking through the operator email-infrastructure layer (SendGrid, Postmark, Mailgun, Amazon SES, SparkPost, Resend). Response routing: outreach responses route to the right operator team — franchisee, corporate marketing, or operator counsel — through the operator workflow engine (Temporal, Inngest, Trigger.dev, or Vercel Queues). Link-acquisition tracking: acquired links are recorded against the operator master record with per-location attribution. Per-vertical compliance overlay: where the franchise vertical is regulated, HIPAA, FDA OPDP, DEA, state-licensing-board, state- Metrc, DISCUS, FDA tobacco, ATF, and state-financial rules apply; FTC, Lanham Act, ADA Title III, COPPA, and state-AG UDAP rules apply universally. FDD overlay: FTC Franchise Rule, FDD Item 11 Franchisor Assistance, Item 12 Territorial Protection, Item 19 Financial Performance Representation, Item 20 Outlet List, per-state franchise-relationship statutes, International Franchise Association policy, and per-franchisee franchise agreement terms gate what franchisor-assistance copy and comparative-performance data the outreach can reference. Operator owns the prospect list, the franchisee data, the brand spec, the compliance overlay rule library, every vendor credential under operator billing, the sender domains under operator DNS control, the DMARC/DKIM/SPF records, the per-domain dedicated IP allocation, the TCPA consent register and CAN-SPAM unsubscribe register, the outreach orchestration code, the LLM prompts, the per-location link-acquisition tracking infrastructure, and the audit trail. Completions owns the orchestration knowledge.

Question 2

Why is per-location link outreach typically operator-side rather than outreach-vendor- or email-infrastructure-vendor-shipped?

Accepted Answer

Six engineering surfaces sit between operator data infrastructure and a working per-location link outreach bundle, and they sit outside the design center of the outreach-platform, email-infrastructure, DNS, SMS, deliverability, franchise-management, local-context, and LLM ecosystems that own the upstream primitives. Surface 1 — Per-location prospect discovery: Pitchbox, BuzzStream, NinjaOutreach, Hunter, Mailshake, Lemlist, Outreach, Reply.io, Respona, Postaga, and Snov.io ship strong outreach primitives but stop short of franchise-aware per-territory prospect shaping that ties chamber-of-commerce, trade-publication, local-school, municipal, news, and event-sponsorship sources to each franchisee territory. Surface 2 — Personalized 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-prospect personalization with operator-counsel-approved guardrails is operator-side. Surface 3 — Per-vendor volume-cap enforcement: TCPA, CAN-SPAM, 10DLC, CTIA A2P, CASL, UK PECR, EU ePrivacy, state-AG UDAP, and state-SHIELD compliance across multi-vendor outreach platforms is operator-counsel-side. Surface 4 — Per-location sender-reputation management: SendGrid, Postmark, Mailgun, Amazon SES, SparkPost, and Resend ship strong delivery primitives, and Cloudflare, Route 53, Google Cloud DNS, and Azure DNS ship strong DNS primitives, and SenderScore, Google Postmaster Tools, Microsoft SNDS, Talos Intelligence, Spamhaus, and Barracuda Central ship strong deliverability monitoring, but per-domain warming schedules, DMARC/DKIM/SPF authoring, and inbox-placement remediation is operator-side. Surface 5 — Response routing: Temporal, Inngest, Trigger.dev, and Vercel Queues ship strong durable-workflow primitives but the routing policy from response to franchisee, corporate marketing, or operator counsel is operator-side. Surface 6 — FDD overlay: FranConnect, Naranga, and IFX Online ship strong franchisee-communication primitives but treat link outreach as out-of-scope; FTC Franchise Rule, FDD Items 11/12/19/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 (2-3 weeks, diagnostic): audits the six surfaces above against the operator stack — which outreach-platform vendors are wired today, which email-infrastructure and SMS-infrastructure vendors deliver, which DNS vendor authors DMARC/DKIM/SPF, which deliverability monitoring is in place, which franchise-management platform holds the franchisee directory, which local-context vendors are accessible, which LLM-as-judge models are available, and where the per-vertical compliance overlay and FDD overlay need counsel review against Items 11, 12, 19, and 20. Tier 2 AI Swarm Setup Sprint (4-8 weeks): builds the per-location link outreach bundle on the citation-link-build agent, with the brand-voice gate calibrated by the operator brand team, the per-vendor volume-cap policy reviewed by operator counsel, the sender-reputation per-domain warming schedule reviewed by the operator deliverability team, and the FDD 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 master-record-canonicalization, brand-spec-authoring, compliance-overlay-manager, internal-link-orchestration, and local-pack-tracking siblings.

Question 4

Who owns the prospect list, outreach platform credentials, sender domains, and audit trail?

Accepted Answer

Operator owns 100% of every artifact. The prospect list is versioned in the operator repo and operator data infrastructure. Franchisee data sits in operator data infrastructure (Snowflake, BigQuery, Databricks, Redshift, or Postgres). The brand spec is versioned in the operator repo. Outreach-platform vendor credentials (Pitchbox, BuzzStream, NinjaOutreach, Hunter, Mailshake, Lemlist, Outreach, Reply.io, Respona, Postaga, Snov.io) sit under operator billing. Email-infrastructure vendor credentials (SendGrid, Postmark, Mailgun, Amazon SES, SparkPost, Resend) sit under operator billing with operator-owned per-domain dedicated IP allocation. SMS-infrastructure vendor credentials (Twilio, Attentive, Postscript) sit under operator billing with operator-owned 10DLC campaign and CTIA A2P registration. DNS credentials (Cloudflare, Route 53, Google Cloud DNS, Azure DNS) sit under operator DNS control with operator-owned DMARC, DKIM, and SPF records. Deliverability-monitoring credentials (SenderScore, Google Postmaster Tools, Microsoft SNDS, Talos Intelligence, Spamhaus, Barracuda Central) sit under operator billing where the operator runs them. Franchise-management vendor credentials (FranConnect, Naranga, IFX Online) sit under operator billing. Local-context vendor credentials (PredictHQ, Eventbrite, Ticketmaster) sit under operator billing. LLM API credentials (OpenAI, Anthropic, Google, Mistral, Cohere, Meta) sit under operator billing. The TCPA consent register, CAN-SPAM unsubscribe register, and CASL register live in the operator system of record with operator-counsel-policy retention. The outreach orchestration code, the LLM prompt library, the per-location link-acquisition tracking code, and the response-routing policy live in the operator repo with operator-controlled deploy pipeline. The compliance overlay rule library lives in the operator repo with attorney-approved updates and tracks TCPA, CAN-SPAM, 10DLC, CTIA A2P, CASL, UK PECR, EU ePrivacy, GDPR, CCPA, 11 state rights acts, state SHIELD, FTC, Lanham, state-AG UDAP, ADA Title III, COPPA, FTC Franchise Rule, FDD Items 11/12/19/20, per-state franchise-relationship statutes, International Franchise Association policy, and per-franchisee franchise agreement terms. The audit trail persists to operator-controlled WORM storage where SEC, FINRA, SOX, state-AG, or state franchise-registrar retention rules require it. The attorney relationship is operator-owned and operator-counsel-maintained; Completions accesses attorney work-product under operator-controlled attorney-client privilege. Completions owns the orchestration knowledge — how to design per-location prospect discovery, how to tune per-location personalization with brand-voice gating, how to debug per-domain sender-reputation cascades, how to manage TCPA + CAN-SPAM + 10DLC + CTIA A2P + CASL register discipline, and how to coordinate with the master-record-canonicalization, brand-spec-authoring, compliance-overlay-manager, internal-link-orchestration, and local-pack-tracking siblings. The operator can in-house at any time; Completions credentials revoke immediately on engagement-end and the attorney relationship continues unbroken.

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 citation-link-build agent: (1) Prospect-Discovery workstream — pre-engagement baseline of which local-context sources are wired today across chamber-of-commerce, trade-publication, local-school, municipal, news, and event-sponsorship surfaces, then weekly reporting on per-franchisee prospect-list coverage and source freshness. (2) Personalized-Drafting workstream — pre-engagement baseline of how drafts are produced today, then weekly reporting on LLM-as-judge ensemble pass distribution and operator-brand-team disagreement signals. (3) Per-Vendor Volume-Cap workstream — pre-engagement baseline of outreach volume per vendor today and which compliance frameworks are wired, then weekly reporting on per-vendor cap adherence and TCPA + CAN-SPAM + 10DLC + CTIA A2P + CASL + UK PECR + EU ePrivacy + state-AG UDAP + state-SHIELD overlay completeness. (4) Sender-Reputation workstream — pre-engagement baseline of per-domain dedicated IP allocation, DMARC/DKIM/SPF state, and inbox-placement metrics today, then weekly reporting on per-domain reputation, bounce rate, complaint rate, and deliverability-monitoring signals from SenderScore, Google Postmaster Tools, Microsoft SNDS, Talos Intelligence, Spamhaus, and Barracuda Central. (5) Response-Routing + Link-Acquisition workstream — pre-engagement baseline of how responses route today and how acquired links are tracked, then weekly reporting on response volume by routing destination (franchisee, corporate marketing, counsel) and link-acquisition events recorded against the master record. (6) Per-Vertical Compliance + FDD-Overlay workstream — pre-engagement baseline of which frameworks are attorney-approved today (FTC, Lanham, state-AG UDAP, ADA Title III, COPPA, HIPAA, FDA OPDP, DEA, state-licensing-board, state- 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), then weekly reporting on overlay completeness and counsel re-review state. Caveats: outreach-platform vendor API rate limits, deprecations, and pricing changes are vendor decisions outside Completions control; email-infrastructure deliverability outcomes depend on mailbox-provider policy (Gmail, Outlook, Yahoo, Apple Mail Privacy Protection) outside Completions control; SMS carrier filtering, 10DLC campaign approvals, and CTIA A2P trust scores are carrier decisions outside Completions control; DNS vendor and deliverability-monitoring vendor API and pricing changes are outside Completions control; TCPA, CAN-SPAM, 10DLC, CTIA A2P, CASL, UK PECR, EU ePrivacy, state-AG UDAP, and state-SHIELD policy can change and require operator-counsel re-review; per-vertical regulator policy can change without notice; FDD Items 11/12/19/20 thresholds + disclosure rules are FTC + state franchise-administrator policy + can change; per-state franchise-relationship statutes, IFA policy can change; LLM-vendor API rate limits + model deprecation + pricing changes outside Completions control; per-franchisee outreach response capacity is operator-team capacity decision; per-statute retention windows are operator-counsel-policy; the audit trail persists to operator-controlled WORM storage on the operator cloud account; comparative-performance data shared with franchisees is operator-counsel-policy under FDD Item 19.

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 prospect discovery, personalized drafting, per-vendor volume-cap enforcement, per-location sender-reputation management, TCPA + CAN-SPAM + 10DLC + CTIA A2P + CASL register discipline, response routing, link-acquisition tracking, and FDD overlay management + outreach-platform vendor credentials hand-off + email-infrastructure vendor credentials hand-off + SMS-infrastructure vendor credentials hand-off + DNS credentials hand-off (operator retains DMARC/DKIM/SPF records) + deliverability-monitoring vendor credentials hand-off + franchise-management vendor credentials hand-off + local-context vendor credentials hand-off + LLM API credentials hand-off + outreach orchestration code hand-off + LLM prompt library hand-off + per-location link-acquisition tracking code hand-off + response-routing policy hand-off + compliance overlay rule library hand-off + TCPA + CAN-SPAM + CASL register 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