ComposableStack.AI · Subject Matter Expert Series

CDP Recommendation Agent

Unbiased guidance on your Customer Data Platform architecture — Packaged vs. Composable, latency tiers, vendor tradeoffs. Every recommendation cites a knowledge-graph node so you can verify the source. The graph evolves daily through reflective evolutionary search.

Structured assessment

Four-section questionnaire — goals, technical context, organization, use cases — that maps your situation onto the knowledge-graph axes.

Grounded conversation

Agent responses cite specific KG node IDs. Click any citation to verify the underlying source — vendor doc, raw note, or web reference.

Self-improving daily

Eight scheduled routines reflect on conversations, refine the KG, and open PRs against the content + agent + UI repos.

Proposed Research Topics

Topics queued for upcoming articles. Sign in to give the researcher your priority signal. Updates daily.

View all
implementation-pitfallblog

AEP's Snowflake Batch Format Change: What Engineering Teams Need to Do Before June Ends

AEP changed its Snowflake Batch destination table structure in March 2026, and the legacy column-per-audience format is deprecated at end of June 2026. Data engineering teams running AEP → Snowflake Batch activation pipelines need to migrate to the V2_ table structure before the deadline or production pipelines break. This was a silent product change documented in ExperienceLeague rather than notified by email — many teams haven't seen it. Additional constraints include a 7-day TTL on exported data and Azure Private Link incompatibility that compound the migration planning.

org-structureblogmedium

The Media Publisher CDP Problem No One Wrote the Buyer's Guide For

Media publishers evaluating CDPs face a data model that most CDP evaluation frameworks weren't designed for: behavioral engagement signals (content consumption, completion rate, topic affinity) replace transactional purchase events as the primary identity anchor, and a dual-revenue model (subscriptions + advertising) creates two parallel activation tracks from the same unified profile with distinct consent requirements. Most CDP evaluation guides were written for retail and ecommerce; applying them to a media publisher produces the wrong shortlist and systematically underscores consent enforcement and audience governance criteria.

vendor-updatelinkedinmedium

Twilio Is a Communications Leader. That's Not What You're Evaluating.

Twilio holds a 2026 Gartner Leader position in CPaaS and a Niche Player position in the CDP MQ — for the second consecutive year. The conflation of these two placements is a specific and common evaluator error: organizations that know Twilio as a 'Gartner Leader' carry that credential into CDP shortlisting where it doesn't apply. Segment's real CDP strengths (developer-native instrumentation, 700+ prebuilt connectors, consent management integration) are genuine evaluation criteria for engineering-led orgs — but they're different criteria than the ones that produced the CPaaS Leader placement.

org-structureblogmediumlinkedin

Are You a Marketing-Led CDP or an Engineering-Led CDP? The Mid-Market Question Most Teams Skip

The mid-market CDP evaluation collapses into 'composable vs. packaged' when the real structural variable is which team holds RACI-Accountable for CDP operations. A new knowledge-graph archetype for engineering-led mid-market evaluators surfaces this distinction and its consequences: organizations evaluating SQL-first tools (Hightouch, Census) against no-code platforms without first settling who owns the activation layer are evaluating the wrong things in the wrong order.

Latest Knowledge-Graph Updates

Nodes and daily proposals from the last 14 days. Sign in to flag any as helpful, incorrect, or needing more depth. Updates daily.

View all
node updatesource

HIPAA Privacy Rule — Updated for 2026 (HIPAA Journal)

source.hipaajournal-com.hipaa-privacy-rule-2026

HIPAA Journal comprehensive overview of the HIPAA Privacy Rule, updated for 2026, covering PHI definition, permitted uses and disclosures, marketing restrictions, and written authorization requirements.

node updatearchetype

Salesforce Ecosystem Enterprise Evaluating CDP

archetype.salesforce-ecosystem-enterprise-evaluating-cdp

An enterprise with Salesforce CRM and Salesforce Data 360 as the incumbent CDP layer, now evaluating whether Data 360's segmentation and Marketing Cloud Next's Agentforce orchestration are sufficient for their use cases, or whether composable augmentation (Hightouch or Fivetran Activations over an existing CDW) adds meaningful value — particularly for CDW-native ML models, cross-cloud data, or segment volumes that require warehouse-native computation.

node updatearchetype

Marketing-Led Mid-Market Composable Evaluator

archetype.marketing-led-mid-market-composable

A mid-market organization ($25M–$500M revenue, 50K–1M customer profiles) where Marketing (CMO or VP Marketing) is RACI-Accountable for the CDP evaluation and operations. Evaluating composable or marketing-accessible CDP tooling without the budget for enterprise packaged platforms (AEP, Salesforce Data 360) and without deep data engineering staffing. The evaluation is marketing-led — not IT/CDO-driven. Primary candidate paths: BlueConic (marketer-operated Growth Plays, no-SQL), GrowthLoop (agentic no-code CDW activation if CDW exists), mParticle (mobile-first B2C apps). Distinguishing from enterprise archetypes by budget ceiling (~$400K/year), marketing Accountable (not CTO or CDO), and mid-market scale where composable tooling's operational simplicity outweighs its flexibility cost.

How this is different

Most CDP guidance is packaged with a vendor recommendation attached. This agent is built on a knowledge graph that enforces bias-neutrality in its routine: every Vendor mention must link to at least one alternative-to edge. The recommendation isn't "use X" — it's "given your profile, here are the directions worth considering, here's the tradeoff, here's how you'd verify."

Read how it works →