How this matrix is used: Each Signal Tier represents a LinkedIn audience segment built by tech stack (Tier 2/3) or industry (Tier 4). Copy is generalized to the tier — not the account. The tier targeting does the personalization work; the copy does the resonance work. Persona targeting (job title filtering in LinkedIn) selects which pain point variant each person sees within their tier.

Audience building: Tier 2 & 3 audiences are built by targeting company follower lists of Databricks, Snowflake, dbt, Airflow users. Tier 1 (OSS) audiences are uploaded from CRM. Tier 4 is served broadly within the ICP by industry.

Tier 1 — OSS Users (DataHub Core)

Tier 2 — AI Tooling Confirmed

Tier 3 — Modern Data Stack (no AI tooling confirmed)

Tier 4 — Industry Fallback

Tier 1 — OSS Users (DataHub Core)

Confirmed DataHub Core users. They have discovery and lineage. The message bridges to what Cloud adds: freshness monitoring, incident SLAs, compliance workflows, MCP Server, Context Graph for AI agents. This is an upgrade conversation, not a discovery conversation.

Example accounts: Abbott, Pfizer, Disney, CBRE, P&G, Ford, Walmart, Splunk, BlackRock, Parker Hannifin, CVS Health

CRM Account Stage = OSSOSS Telemetry Activity tag

Persona 1

Data Engineer

Pain Point Freshness and volume monitoring still means manual debugging — even with DataHub Core running. When a pipeline goes stale, there's no automated alert before downstream consumers hit bad data.

Problem

Core tells you what. Not when it breaks. Freshness monitoring, volume checks, and automated alerts on stale data — Core doesn't provide them. Your team builds them.

Solution

Automated assertions catch stale data before consumers do. DataHub Cloud monitors freshness, schema stability, and volume on a schedule — and alerts your team before anything breaks downstream.

Why DataHub

You're already running DataHub. Cloud adds observability. No migration. No retraining. Just the monitoring infrastructure your OSS deployment was never designed to provide. See what Cloud adds →

Persona 2

Data Platform Lead

Pain Point Incident management in Core means building dashboards from scratch. No SLA tracking, no cross-team visibility, no automated escalation — platform leads are flying blind when something breaks.

Problem

Your incident workflow is a Slack thread. Still. OSS DataHub doesn't come with SLA dashboards or cross-team incident visibility. You built the platform. You're still building the ops layer on top of it.

Solution

Incident SLA dashboards. Out of the box. DataHub Cloud gives platform leads real-time visibility into data health across every team — without the dashboard build your OSS deployment requires.

Why DataHub

Built on what your team already knows. Same DataHub. Cloud adds the operational layer — incident management, SLAs, compliance dashboards — that Core was never designed to include.

Persona 3

CDO / VP Data

Pain Point AI initiatives require metadata infrastructure that OSS DataHub can't provide. No MCP Server, no Context Graph — AI agents can't query trusted metadata at machine scale on Core.

Problem

Your AI agents can't talk to your data catalog. MCP Server and Context Graph are Cloud-only. AI initiatives built on DataHub Core hit the ceiling the moment they need metadata at machine scale.

Solution

Give AI agents trusted metadata. In real time. DataHub Cloud's MCP Server and Context Graph let AI agents query certified, live metadata — the infrastructure Core was never architected to provide.

Why DataHub

Your OSS foundation. Cloud's AI readiness layer. You've already solved discovery and lineage. Cloud is what turns that foundation into production-grade AI infrastructure. See DataHub Cloud vs Core →

Persona 4

AI / ML Team

Pain Point Training data freshness SLAs in production models are still caught manually or over Slack — Core doesn't provide the automated monitoring or agent-queryable metadata ML teams need.

Problem

Stale training data. Found after the model ran. When freshness SLA misses in production models are caught manually, you're always a step behind — and your models pay for it.

Solution

Automated freshness monitoring built for production AI. DataHub Cloud catches training data quality issues before your models consume them — automated assertions, real-time alerts, no manual checks.

Why DataHub

MCP Server. Context Graph. Cloud-only. Worth it. ML teams at scale need metadata infrastructure that works at machine speed. Cloud adds exactly that — built on the DataHub your org already runs.

Tier 2 — AI Tooling Confirmed

Reodev has confirmed AI tooling in the stack (OpenAI, SageMaker, LangChain, Vertex AI, MLflow, etc.). May also have modern data stack tags (Databricks, Snowflake, dbt, Airflow). Message: they're building AI, and the metadata / data quality layer hasn't kept pace. The risk is undocumented, unvalidated training data reaching production.

Example accounts: Experian, MGM, NBCUniversal, Cardinal Health, Nationwide, TIAA, Elevance Health, KKR, AT&T, Disney, UPS, Wells Fargo, U.S. Bank, Halliburton, NRG, Charles Schwab

Tags contain "AI Tooling"Reodev AI signal confirmed

Persona 1

Data Engineer

Pain Point Debugging metric discrepancies in AI pipelines means Slacking across teams hoping someone finds the root cause. No lineage from training data to model output means no fast path to the answer.

Problem

AI pipeline broke. Nobody knows why. Yet. When lineage doesn't connect your training data to your model outputs, debugging means Slack threads and hours of manual digging.

Solution

Trace AI pipeline failures to the source. Fast. DataHub maps lineage from raw data through every transformation to your model inputs — so engineers find the root cause in minutes, not hours.

Why DataHub

Connects to your AI stack. Automatically. DataHub integrates with Databricks, Snowflake, dbt, Airflow, and your AI tooling — automated lineage, no manual metadata maintenance. See integrations →

Persona 2

Data Platform Lead

Pain Point Self-serve discovery is bottlenecked on the central platform team. Analysts burn 20–30% of their time hunting for datasets instead of using them — and AI initiatives move at the speed of the slowest data question.

Problem

Your analysts ask the platform team. Every time. When data discovery isn't self-serve, your central team becomes the bottleneck — and AI timelines move at the speed of that queue.

Solution

Self-serve discovery. No platform team required. DataHub's conversational search lets analysts find certified data in seconds — cutting the discovery requests that bottleneck your platform team daily.

Why DataHub

119% more AI models reach production. IDC, 2026. DataHub customers see 119% more AI/ML models successfully reaching production after eliminating the data discovery bottleneck. See the research →

Persona 3

CDO / VP Data

Pain Point AI initiatives stall on the question of which data is actually safe to train on. Without a certification layer, every AI project carries undocumented risk — and that's the kind of exposure that surfaces at the worst time.

Problem

Which data is safe to train your AI on? Every AI initiative your team is running carries the same undocumented risk — nobody has certified which training data is actually validated and trustworthy.

Solution

Operationalize AI readiness. Not just aspirations. DataHub certifies which data is safe to train on — automated quality assertions, lineage from source to model, and governance your board can see.

Why DataHub

3,000+ organizations. 119% more models in production. DataHub is how enterprise data leaders make AI initiatives actually ship — not pilots. See how leading organizations operationalize AI readiness →

Persona 4

AI / ML Team

Pain Point Freshness SLA misses in revenue-impacting models are still caught manually or over Slack. There's no automated layer between when training data goes stale and when the model consumes it.

Problem

Your model consumed stale data. You found out later. Without automated freshness monitoring between your data pipelines and your models, every training run is a manual quality check you probably skipped.

Solution

Catch data quality issues before models consume them. DataHub's automated assertions validate freshness, volume, and schema stability on every dataset — flagging issues before they reach training pipelines.

Why DataHub

Built for AI teams at companies like yours. DataHub customers report 119% more AI/ML models reaching production after eliminating training data quality issues at the pipeline level. See results →

Tier 3 — Modern Data Stack (No AI Tooling Confirmed)

Confirmed modern data stack (Databricks, dbt, Airflow, Snowflake) but no AI tooling confirmed yet. Message connects the specific tool to the problem it creates in production — lineage for dbt/Airflow, governance for Snowflake, lakehouse readiness for Databricks. Industry context makes the pain specific.

Example accounts: Brooks Running, Apollo, Cruise, Omnicom, Barings, Mylan, Swedish Match, Coca-Cola Consolidated, Jazwares, Whirlpool, Ameriprise

Tags: Databricks, dbt, Airflow, or SnowflakeNo AI Tooling tag

Note for creative team: Tier 3 has 3 sub-variants based on which stack tools are confirmed. Use the variant that matches the dominant tool in the audience's targeting. dbt/Airflow → lineage angle. Snowflake-only → governance angle. Databricks → lakehouse readiness angle. If multiple tools are confirmed, default to the dbt/Airflow variant.

Persona 1 · dbt / Airflow variant

Data Engineer

Pain Point When dbt models change and Airflow pipelines break, finding the root cause means tracing manually through layers of transformations. There's no fast path from "this dashboard is wrong" to "this is why."

Problem

dbt changed. Airflow broke. Now what? Tracing a pipeline failure through transformation layers without lineage means hours of manual debugging your team can't afford to spend.

Solution

Column-level lineage. From dbt to every downstream report. DataHub maps every dbt transformation to what depends on it — so when something breaks in Airflow, your team knows exactly what changed and where.

Why DataHub

Connects to dbt, Airflow, and Snowflake. Out of the box. Automated lineage across your stack — no custom build, no manual maintenance. 100+ integrations, all kept current as your pipelines change. See integrations →

Persona 2 · dbt / Airflow variant

Data Platform Lead

Pain Point Self-serve discovery doesn't exist without a catalog — and without lineage, even a catalog doesn't tell analysts whether the data they found is safe to use. The central team stays the gatekeeper.

Problem

Analysts find data. Then ask if they can trust it. Without lineage connecting your dbt models to downstream reports, discovery is only half the problem. Analysts still need a human to confirm the data is current.

Solution

Discovery and trust. At the same time. DataHub's conversational search surfaces certified datasets with lineage context built in — so analysts know what they found is current without asking the platform team.

Why DataHub

91% faster data searches. Real IDC data. 2026. DataHub customers cut data search time from 50 minutes to 5 — without rebuilding their dbt and Airflow workflows. See the numbers →

Persona 3 · Snowflake / Databricks variant

CDO / VP Data

Pain Point At scale in Snowflake or Databricks, governance means knowing who owns what, what's certified, and what's PII — and maintaining that manually across hundreds of tables is the work that falls through the cracks.

Problem

Snowflake at scale. Governance still mostly manual. Ownership, PII classification, and data certification across hundreds of tables don't maintain themselves — and the gap compounds every time a new dataset gets added.

Solution

Governance that scales with your data. Automatically. DataHub automates PII classification, ownership assignment, and compliance tracking across your Snowflake environment — so governance keeps pace without manual effort.

Why DataHub

3,000+ organizations. 48% fewer data outages. DataHub customers report 48% fewer data-related outages after deploying automated governance and observability across their data stack. Get a demo →

Persona 4 · All stack variants

AI / ML Team

Pain Point Finding reliable training data across a fragmented, undocumented Snowflake/Databricks environment means hours of hunting before a model can even be built. Feature reuse is rare because nobody knows what's already been built.

Problem

Your ML team rebuilds features that already exist. Without discovery across your Snowflake and Databricks environment, ML engineers spend hours finding data before building — and miss the pipelines someone else already shipped.

Solution

Find certified training data in seconds, not days. DataHub's conversational search surfaces existing features, training datasets, and pipelines across your entire stack — so your ML team builds on what already works.

Why DataHub

119% more AI models ship. With the same team. DataHub customers get 119% more AI/ML models to production by eliminating the discovery and data quality work that delays every experiment. See results →

Tier 4 — Industry Fallback

No confirmed tech stack or AI tooling. Signal comes from industry and company profile. Message is broader — a specific industry-relevant data problem that resonates without requiring stack knowledge. These audiences are served broadly within the ICP by industry vertical on LinkedIn.

Example accounts: Hulu, Coca-Cola, Bank of America (Merrill Lynch), Merrill Lynch, Omnicom Group, Whirlpool, Swedish Match, CEVA Logistics, National Indemnity, NetJets

No tech stack confirmed in TagsICP industry match

Note for creative team: Tier 4 runs 4 industry sub-variants (Financial Services, Healthcare, Media/Tech, General Enterprise). LinkedIn audience targeting by industry handles delivery — copy below covers each sub-variant. Use the industry-matched sub-variant for each audience.

Sub-variant A — Financial Services

Data / Risk / Compliance Leaders

Pain Point BCBS 239 and regulatory reporting requirements demand data lineage accuracy that quarterly audit processes can't reliably maintain as pipelines change daily.

Problem

Regulatory data lineage. Still a quarterly scramble. BCBS 239 requires continuous lineage accuracy — but pipelines change daily, and point-in-time audits can't keep pace with what actually runs in production.

Solution

Continuous compliance. Not point-in-time documentation. DataHub tracks lineage automatically across your data platform — flagging compliance gaps in real time so your team fixes them before regulators find them.

Why DataHub

Visa runs this for compliance at global scale. Visa and leading financial institutions use DataHub to turn BCBS 239 compliance from a periodic audit into an always-on operational standard. Get a demo →

Sub-variant B — Healthcare / Pharma

Data / Compliance / AI Leaders

Pain Point Clinical and patient data governance is non-negotiable — but managing access controls, PII classification, and audit trails manually across a complex data environment doesn't scale and creates compliance gaps.

Problem

Clinical data governance. Still mostly manual overhead. Manually classifying PII, assigning data ownership, and tracking compliance across clinical pipelines doesn't scale — and every new dataset adds more risk.

Solution

Automated PII classification. Continuous compliance monitoring. DataHub automatically detects sensitive data, enforces governance policies, and maintains the audit trails your compliance and regulatory teams require — at scale.

Why DataHub

Built for sensitive data at enterprise healthcare scale. DataHub is used by healthcare organizations managing clinical data governance at scale — including access control, PII workflows, and regulatory audit trails. See how →

Sub-variant C — Media / Streaming / Tech

Data / Platform / Analytics Leaders

Pain Point Content, ad, and user behavior teams work from different data sources — metric inconsistencies between teams slow decisions and erode trust in the analytics that drive product and revenue.

Problem

Three data teams. Three versions of the same number. When product, content, and ad teams can't agree on metrics, the real problem isn't the numbers — it's that nobody can trace where the difference came from.

Solution

Shared truth. Traceable lineage. No more Slack debates. DataHub connects your teams to a single source of certified, documented data — with lineage that shows exactly where every metric came from.

Why DataHub

Netflix runs this. So does DoorDash, Twilio, and Miro. Leading tech and media companies trust DataHub to unify their data platform. See how it works for organizations like yours →

Sub-variant D — General Enterprise (CPG / Retail / Industrial)

Data / Analytics / Platform Leaders

Pain Point Data fragmentation across divisions, markets, and business units means analysts spend 20–30% of their time hunting for reliable data instead of using it — and nobody can agree on which number is right.

Problem

Your data exists. Your team can't find the right version. When every division manages its own data, analytics teams spend more time verifying datasets than using them — and the decisions downstream reflect that.

Solution

Find trusted data in seconds. Across every division. DataHub's conversational search makes certified, documented data discoverable to every team — cutting the discovery time that bottlenecks analytics across your organization.

Why DataHub

91% faster. 48% fewer outages. Real customer results. DataHub customers find data 91% faster and see 48% fewer data-related outages — at Walmart, P&G, and 3,000+ other organizations. Get a demo →

Matrix Summary — Audience × Message Map

Tier	Primary Signal	Data Engineer Hook	Platform Lead Hook	CDO / VP Hook	AI / ML Hook
T1 — OSS	DataHub Core user	Freshness monitoring	Incident SLA dashboards	MCP Server / AI agents	Training data freshness
T2 — AI Tooling	AI tooling confirmed	Pipeline debugging	Self-serve discovery	AI readiness certification	Training data quality
T3 — Tech Stack	dbt / Airflow / Snowflake / Databricks	Lineage / root cause	Certified discovery	Governance at scale	Feature reuse / ML discovery
T4 — Industry	Industry vertical match	Industry-specific pain (FinServ: BCBS / Healthcare: governance / Media: metrics / Enterprise: discoverability)

Generated for internal ABM use · FY27 Q1 · Wacarra Yeomans · Acryl Data

ABM Tier Messaging Matrix

Tier 1 — OSS Users (DataHub Core)

Tier 2 — AI Tooling Confirmed

Tier 3 — Modern Data Stack (No AI Tooling Confirmed)

Tier 4 — Industry Fallback

Matrix Summary — Audience × Message Map