Question 1

What does done-for-you multi-location lifecycle marketing actually deliver?

Accepted Answer

Completions builds and operates a multi-location lifecycle marketing bundle on the email-publishing, sms-publishing, push-notification-publishing, and in-app-messaging agents for multi-location retailers, multi-unit restaurant operators, franchise systems, and regulated multi-location operators running 50-1,500 locations across multiple states and verticals. Location-aware cadences: welcome series, post-purchase, replenishment reminder, birthday, win-back, dormant, at-risk, lapsed, and reactivation cadences shape subject lines, body copy, offers, send-time, and tone to each subscriber's home location (DMA, vertical, region, hours, inventory mix) through the operator delivery layer (Klaviyo, Postscript, Attentive, Iterable, Braze, Customer.io, Cordial, Bloomreach, Sailthru, Adobe Journey Optimizer, Salesforce Marketing Cloud, Oracle Eloqua, HubSpot, Mailchimp, ActiveCampaign, Drip, ConvertKit, Twilio, MessageBird, OneSignal, Airship, Marigold). Brand-voice gating: every draft passes through a multi-model 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 with version-pin, tone, formality, empathy, and channel-format knobs. Per-vertical compliance overlay: where the vertical is regulated, HIPAA, FDA OPDP, DEA Schedule II-V, ATF, state- Metrc, DISCUS, FDA tobacco, state-licensing-board, and state-financial rules apply; FTC, Lanham Act, state-AG UDAP, ADA Title III, and COPPA apply universally; FTC Franchise Rule and FDD Items 19/20 apply where the operator is a franchisor and shares performance data with franchisees. Consent and channel-policy management: TCPA prior-express-written-consent (marketing) and prior-express-consent (transactional) registers live in the operator system of record; CAN-SPAM unsubscribe register honors opt-outs within the statutory window with accurate sender-line, accurate subject-line, working unsubscribe link, and physical mailing address; 10DLC SMS campaign and CTIA A2P registration is operator-counsel-maintained where the operator runs SMS through Twilio, Attentive, Postscript, or SimpleTexting; CASL applies where the operator markets into Canada; UK PECR and EU ePrivacy Directive apply where the operator markets into the UK and EU; GDPR Article 6 lawful-basis, Article 21 right-to-object, Article 22 right-not-to-be-subject-to-solely-automated-decision-making, and Article 33 breach-notification registers apply where GDPR applies; CCPA Section 1798.120 and CPRA Section 1798.121 opt-out cascades plus the 11 other state rights acts (Virginia VCDPA, Colorado CPA, Connecticut CTDPA, Utah UCPA, Iowa ICDPA, Indiana ICDPA, Tennessee TIPA, Texas TDPSA, Montana MCDPA, Oregon OCPA, Delaware DPDPA) and state SHIELD acts apply per state. Per-cohort causal-uplift attribution: the operator data-science team's causal-inference stack (EconML, CausalML, DoubleML, scikit-uplift, uplift, with T/S/X/DR-learner meta-learners, Bayesian treatment-effect models, counterfactual prediction, and causal-forest) runs against holdout-control architecture (portfolio-wide holdout, segment-stratified, matched-control, difference-in-difference, synthetic-control, pre-post, A/B test, and bandit control-arm), with cadence-trigger prediction supported by XGBoost, LightGBM, CatBoost, lifelines survival models, and PyMC Bayesian hierarchical models. Cross-channel coordination: the operator workflow engine (Temporal, Inngest, Trigger.dev, Vercel Queues) enforces frequency caps, cross-channel conflict resolution, cross-channel suppression, and quiet-hours respect. CDP integration: the operator CDP (Segment, mParticle, Rudderstack, ActionIQ, Treasure Data, Tealium, Lytics) feeds identity and trait state. Audit trail: every cadence decision and outcome persists to operator-controlled WORM storage (AWS S3 Object Lock, Google Cloud Storage retention, Azure Blob immutable, or Snowflake Time Travel) at per-statute retention windows reviewed by operator counsel. Operator owns the brand spec, the subscriber data, the TCPA consent register, the CAN-SPAM unsubscribe register, the GDPR Articles 6/21/22/33 registers, the CCPA + state rights-acts opt-out registers, the 10DLC and CTIA A2P registrations, every delivery and CDP credential under operator billing, the LLM prompt library, the orchestration code, the compliance overlay rule library, and the audit trail. Completions owns the orchestration knowledge.

Question 2

Why is multi-location lifecycle marketing typically operator-side rather than delivery-vendor- or CDP-vendor-shipped?

Accepted Answer

Six engineering surfaces sit between operator data infrastructure and a working multi-location lifecycle marketing bundle, and they sit outside the design center of the delivery, CDP, causal-inference, ML, and LLM ecosystems that own the upstream and downstream primitives. Surface 1 — Location-aware cadence generation: Klaviyo, Postscript, Attentive, Iterable, Braze, Customer.io, Cordial, Bloomreach, Sailthru, Adobe Journey Optimizer, Salesforce Marketing Cloud, Oracle Eloqua, HubSpot, Mailchimp, ActiveCampaign, Drip, ConvertKit, Twilio, MessageBird, OneSignal, Airship, and Marigold ship strong send-time and flow-builder primitives but stop short of multi-location-aware cadence shaping across DMA, vertical, region, hours, and inventory mix. Surface 2 — Brand-voice gating: 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 calibration to the operator brand spec with version-pin, tone, formality, empathy, and channel-format knobs is operator-side. Surface 3 — Per-vertical compliance overlay: TCPA, CAN-SPAM, 10DLC, CTIA A2P, CASL, UK PECR, EU ePrivacy, GDPR Articles 6/21/22/33, CCPA, 11 state rights acts, state SHIELD, plus per-vertical regulators (HIPAA, FDA OPDP, DEA, state-licensing-board, state- Metrc, DISCUS, FDA tobacco, ATF, state-financial) and franchise-specific frameworks (FTC Franchise Rule, FDD Items 19/20) are operator-counsel-side. Surface 4 — Consent and unsubscribe register management: per-subscriber TCPA prior-express-written-consent register, CAN-SPAM unsubscribe register, GDPR and CCPA registers, and 10DLC + CTIA A2P registrations require operator-side production discipline. Surface 5 — Per-cohort causal-uplift attribution: EconML, CausalML, DoubleML, scikit-uplift, and uplift ship strong CATE estimation primitives, and XGBoost, LightGBM, CatBoost, lifelines, and PyMC ship strong ML primitives, but tying them into holdout-control architecture across portfolio-wide, segment-stratified, matched-control, DiD, synthetic-control, pre-post, A/B, and bandit-control-arm is operator data-science work. Surface 6 — Cross-channel coordination: CDP vendors (Segment, mParticle, Rudderstack, ActionIQ, Treasure Data, Tealium, Lytics) ship strong identity and trait primitives but stop short of cross-channel cadence orchestration with frequency caps and conflict resolution; workflow engines (Temporal, Inngest, Trigger.dev, Vercel Queues) ship strong primitives but the policy is operator-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 delivery vendors are wired today across email, SMS, push, and in-app channels, which CDP holds subscriber identity and traits, which causal-inference and ML libraries the operator data-science team uses, which LLM-as-judge models are accessible, where the TCPA / CAN-SPAM / 10DLC / CTIA A2P / CASL / GDPR / CCPA / state rights-acts registers live, and where the per-vertical compliance overlay needs counsel review. Tier 2 AI Swarm Setup Sprint (4-8 weeks): builds the multi-location lifecycle stack on the email-publishing, sms-publishing, push-notification-publishing, and in-app-messaging agents, with the brand-voice gate calibrated to the operator brand spec by the operator brand team, the per-vertical compliance overlay rule library reviewed by operator counsel per vertical, and the causal-uplift attribution stack tuned by the operator data-science team. 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, master-record-canonicalization, subscription-lifecycle, location-benchmarking, and customer-data-graph siblings.

Question 4

Who owns the brand spec, subscriber data, consent register, and compliance overlay during engagement?

Accepted Answer

Operator owns 100% of every artifact. The brand spec is versioned in the operator repo with version-pin, tone, formality, empathy, and channel-format knobs. The subscriber data sits in operator data infrastructure (Snowflake, BigQuery, Databricks, Redshift, or Postgres) with operator CDP credentials (Segment, mParticle, Rudderstack, ActionIQ, Treasure Data, Tealium, Lytics) under operator billing. The TCPA prior-express-written-consent register, CAN-SPAM unsubscribe register, GDPR Articles 6/21/22/33 registers, CCPA + CPRA + 11-state-rights-acts opt-out cascade, CASL register, UK PECR + EU ePrivacy registers, and state SHIELD register live in the operator system of record with operator-counsel-policy retention. The 10DLC campaign and CTIA A2P registration sit under the operator TCR and carrier credentials. Delivery vendor credentials (Klaviyo, Postscript, Attentive, Iterable, Braze, Customer.io, Cordial, Bloomreach, Sailthru, Adobe Journey Optimizer, Salesforce Marketing Cloud, Oracle Eloqua, HubSpot, Mailchimp, ActiveCampaign, Drip, ConvertKit, Twilio, MessageBird, OneSignal, Airship, Marigold) sit under operator billing. LLM API credentials (OpenAI, Anthropic, Google, Mistral, Cohere, Meta) sit under operator billing. The orchestration code, the LLM prompt library, the causal-uplift attribution code, and the cadence-trigger ML code 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 Act, 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, and FDD Items 19/20 where applicable. 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. 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 location-aware cadence shapes, how to tune the brand-voice gate, how to debug per-vertical compliance gating cascades, how to integrate causal-uplift attribution with cadence-trigger prediction, how to coordinate cross-channel frequency caps and suppression, and how to coordinate with the brand-spec-authoring, compliance-overlay-manager, master-record-canonicalization, subscription-lifecycle, location-benchmarking, and customer-data-graph 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 email-publishing, sms-publishing, push-notification-publishing, and in-app-messaging agents: (1) Location-Aware Cadence workstream — pre-engagement baseline of which lifecycle cadences ship location-aware copy today vs which inherit a generic template, then weekly reporting on per-cadence per-channel location-awareness coverage. (2) Brand-Voice Gate workstream — pre-engagement baseline of brand-voice fit across cadence drafts today, then weekly reporting on LLM-as-judge ensemble pass distribution and operator-brand-team disagreement signals. (3) Consent and Channel-Policy workstream — pre-engagement baseline of TCPA consent register state, CAN-SPAM unsubscribe register state, 10DLC + CTIA A2P registration state, CASL register state, GDPR Articles 6/21/22/33 register state, CCPA + state rights-acts opt-out register state, and state SHIELD register state, then weekly reporting on register completeness, unsubscribe SLA adherence within the statutory window, 10DLC campaign health, and per-jurisdiction opt-out cascade outcomes. (4) Per-Vertical Compliance Overlay workstream — pre-engagement baseline of which frameworks are attorney-approved today across HIPAA, FDA OPDP, DEA, state-licensing-board, state- Metrc, DISCUS, FDA tobacco, ATF, state-financial, FTC, Lanham Act, state-AG UDAP, ADA Title III, COPPA, FTC Franchise Rule, and FDD Items 19/20, then weekly reporting on overlay completeness and counsel re-review state. (5) Per-Cohort Causal-Uplift Attribution workstream — pre-engagement baseline of which holdout-control architectures the operator runs today, then weekly reporting on per-cohort lift estimates with confidence interval, CATE estimator stability, and operator-data-science-team-aligned validation. (6) Cross-Channel + CDP Coordination workstream — pre-engagement baseline of how email, SMS, push, and in-app channels coordinate today, then weekly reporting on frequency-cap enforcement, cross-channel conflict resolution outcomes, quiet-hours respect, and CDP identity/trait sync with the delivery layer. Caveats: delivery-vendor API rate limits, deprecations, schema changes, and pricing changes are vendor decisions outside Completions control; SMS carrier filtering, 10DLC campaign approvals, and CTIA A2P trust scores are carrier decisions outside Completions control; TCPA, CAN-SPAM, 10DLC, CTIA A2P, CASL, UK PECR, EU ePrivacy, GDPR, CCPA, state rights acts, and state SHIELD policy can change and require operator-counsel re-review; per-vertical regulator policy can change without notice; FDD Items 19/20 thresholds are FTC and state franchise-administrator policy and can change; LLM-vendor API rate limits, model deprecation, and pricing changes are outside Completions control; causal-uplift attribution confidence depends on operator holdout-control architecture and traffic volume; cross-channel coordination latency depends on CDP and delivery-vendor API behavior; per-statute retention windows are operator-counsel-policy; the audit trail persists to operator-controlled WORM storage on the operator cloud account; per-cadence performance shared with franchisees or prospective franchisees is operator-counsel-policy.

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 location-aware cadence generation, brand-voice gating, per-vertical compliance overlay management, TCPA + CAN-SPAM + 10DLC + CTIA A2P + CASL + GDPR + CCPA + state rights-acts + state SHIELD register management, per-cohort causal-uplift attribution, cross-channel coordination, and CDP integration + delivery vendor credentials hand-off + CDP credentials hand-off + LLM API credentials hand-off + orchestration code hand-off + LLM prompt library hand-off + causal-uplift attribution code hand-off + cadence-trigger ML code hand-off + compliance overlay rule library hand-off + audit-trail hand-off with WORM-storage operator-account-ownership confirmation + 10DLC + CTIA A2P registration remains operator-owned; Completions credentials revoke immediately on engagement-end and the attorney relationship continues unbroken.

Frequently asked