Question 1

What does the done-for-you LTV math primitives bundle actually deliver?

Accepted Answer

Completions builds and operates a 4-skill bundle on the customer-graph agent: (1) LTV-Computation runs per-customer per-cohort LTV across 10 methods (historical, cohort, BG/NBD-predictive, Pareto/NBD-predictive, Markov-chain, survival-analysis, regression, neural-net, Bayesian, hybrid-stack) across 6 horizons (30-day, 90-day, 180-day, 365-day, 720-day, lifetime). (2) LTV-Decay-Modeling fits decay curves across 7 families (exponential, Weibull, Gamma, log-normal, Cox proportional-hazards, accelerated-failure-time, competing-risks) with decay-parameter attribution. (3) LTV-Counterfactual computes intervention scenarios across 6 intervention types (offer, journey, retention, upsell, cross-sell, win-back) with baseline-LTV, intervention-LTV, incremental-LTV, intervention-confidence, and an intervention-attestation record. (4) LTV-Emission emits LTV-record and LTV-change-event to 8 downstream subscribers (offer-optimizer, journey-orchestrator, communication-broadcast, marketing-mix-modeling, measurement-attribution-engine, audience-segmentation, competitive-intelligence, governance-oversight). The 4-skill bundle sits above the operator commerce + ESP + CDP + reverse-ETL stack (Shopify, BigCommerce, Salesforce Commerce Cloud, Adobe Commerce, Klaviyo, Braze, Iterable, Listrak, Cordial, Bloomreach, mParticle, Segment, Tealium, RudderStack, Snowplow, Hightouch, Census). Compliance overlay covers HIPAA PHI, GLBA, PCI DSS payment-data, FCRA consumer-report-data, GDPR Article 17 right-to-erasure, CCPA right-to-delete, per-vertical retention, and per-jurisdiction data-residency / cross-border-transfer. Operator owns 100% of the artifacts: 4 registries inside operator data infrastructure, 4-skill model code aligned with operator data-engineering and data-science teams, per-source credentials (CRM, POS, ESP, SMS, loyalty, per-vertical specialty sources) under operator billing and credentials, per-vertical compliance overlay rule library in operator repo with attorney-approved updates, prompts, and the audit trail. Completions owns the orchestration knowledge. Operator can in-house at any time.

Question 2

Why is LTV math typically operator-side rather than CDP- or ESP-vendor-shipped?

Accepted Answer

Klaviyo, Braze, Iterable, Listrak, Cordial, and Bloomreach ship strong ESP + CRM messaging primitives. mParticle, Segment, Tealium, RudderStack, and Snowplow ship strong CDP + event-streaming primitives. Hightouch and Census ship strong reverse-ETL primitives. The 4 engineering surfaces of an LTV math primitives layer typically sit operator-side rather than vendor-shipped: (1) LTV-Computation across 10 methods and 6 horizons binds to the operator-specific identity-resolution graph, the operator-specific order + subscription + return histories, and the operator-specific revenue-recognition rules — the methods and horizons that fit the operator depend on operator-specific repurchase cycles and category economics; (2) LTV-Decay-Modeling across 7 survival-analysis families requires the operator to choose curves and priors consistent with the operator-specific category and channel mix; (3) LTV-Counterfactual across 6 intervention types requires binding to the operator-specific experimentation surface, control-group definitions, and attestation rules; (4) LTV-Emission to 8 downstream subscribers requires operator-specific routing, retry, and idempotency rules consistent with the operator-specific MMM, audience, and offer-optimization stack. The compliance overlay (HIPAA, GLBA, PCI DSS, FCRA, GDPR Article 17, CCPA) requires attorney-approved per-vertical rules. Completions builds and operates this layer above the operator vendor stack.

Question 3

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

Accepted Answer

Tier 1 AI Readiness Assessment ($10k, 2-3 weeks, diagnostic): audits six axes. Tier 2 AI Swarm Setup Sprint ($25-50k, 4-8 weeks): builds LTV-computation + LTV-decay-modeling + LTV-counterfactual + LTV-emission on customer-graph agent — completing the 12th 4-skill bundle + Identity-resolution data-fabric extends 3-to-4 WITHIN single agent + 4-stage data-pipeline mirrors catalog-canonicalization architecture. Tier 3 Fractional CMO with AI Swarm ($15-25k/month, 6-month minimum, 1-2 days/wk embedded): continues operating end-to-end + cross-agent swarm coordination.

Question 4

Who owns the LTV-computation, LTV-decay-modeling, LTV-counterfactual, and LTV-emission registries?

Accepted Answer

Operator owns 100% of every artifact: 4 registries (in operator data infrastructure), 4-skill bundle model code (operator-owned + operator-data-engineering-team + operator-data-science-team-aligned), per-source credentials (CRM + POS + ESP + SMS + loyalty + per-vertical specialty sources under operator billing + operator credentials), per-vertical compliance overlay (rule library in operator repo with attorney-approved updates), HIPAA + GLBA + PCI + FCRA + GDPR + CCPA + per-vertical retention + per-jurisdiction disclosure register (operator-owned + operator-counsel-maintained), brand spec, LLM prompts, audit trail. Completions owns the orchestration knowledge.

Question 5

What does Completions commit to on a Tier 3 engagement?

Accepted Answer

Completions commits to a 4-workstream pre-engagement-baseline reporting cycle on the customer-graph agent: (1) LTV-Computation workstream — pre-engagement baseline of which LTV methods and horizons are computed today and at what frequency, then weekly reporting on computation coverage and observed prediction calibration against actuals as cohorts mature. (2) LTV-Decay-Modeling workstream — pre-engagement baseline of which decay families are fit today and how decay parameters are attributed, then weekly reporting on decay-model fit quality and posterior credibility on operator-supplied evaluation cohorts. (3) LTV-Counterfactual workstream — pre-engagement baseline of which intervention types currently have counterfactual coverage and what experimental-design discipline exists, then weekly reporting on counterfactual coverage and intervention-attestation persistence. (4) LTV-Emission workstream — pre-engagement baseline of which downstream subscribers consume LTV today and at what latency, then weekly reporting on emission coverage, observed latency, and routing-policy compliance. Caveats: LTV prediction calibration depends on the operator-specific repurchase cycle, category economics, and the maturity of cohorts available; decay-model posterior confidence depends on the operator-side experimental-design discipline and sample sizes; intervention-LTV counterfactual fidelity depends on the operator-side experimentation surface and control-group definitions outside Completions control; emission latency depends on operator-side warehouse load, reverse-ETL vendor SLAs, and downstream subscriber ingestion windows; right-to-erasure and right-to-delete execution timelines are governed by statute, operator-counsel guidance, and downstream vendor capabilities.

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 + 4 registries hand-off + 4-skill bundle model code hand-off + per-source credentials hand-off + per-vertical compliance overlay rule library hand-off + LLM prompts hand-off + audit trail hand-off; Completions credentials revoke immediately.

Done-for-you LTV math primitives for DTC ecommerce, subscription- commerce, multi-location retail, and PE-sponsored portfolio operators — a 4-skill LTV-Computation + LTV-Decay-Modeling + LTV-Counterfactual + LTV-Emission bundle on the customer-graph agent.

Frequently asked