06-reference/research

agent deployer buyer mapping

2026-05-31·research-brief·source: deep-research
leadsbuyer-mappingicpagent-deployerdata-teams

Mapping the Buyer-Side of "Agent-Deployer for Data Teams": ICP, Sourcing Method, and the Honest Limit on Names

The question

Verbatim: "Map the buyer-side of 'agent-deployer for data teams' by name: ~10 director/VP-Data folks who could realistically be given budget to retain RDCO. LinkedIn + Sanity Check audience + phData pipeline sources."

This is the named follow-up the OpenExO brief explicitly queued: "Map the buyer-side of 'agent-deployer for data teams' by name. Who specifically at director/VP Data level is being given budget to hire one? 10-name list from LinkedIn + Sanity Check audience + phData pipeline." ([[~/rdco-vault/06-reference/research/2026-05-28-openexo-rewrite-vs-rdco-agent-deployer.md]])

Scope honesty up front (load-bearing). The two richest name sources named in the question — the Sanity Check subscriber list and phData's internal pipeline — are founder-side data I (the sub-agent) cannot access. They are not on disk, not in the vault, and not on the public web. A list of ten plausible-sounding names invented to satisfy the "by name" framing would be the single worst possible output of this brief: it would look like leads and be fiction. So this brief deliberately delivers three things instead: (a) a sharp buyer ICP so the founder knows exactly who qualifies; (b) a repeatable sourcing method the founder runs against his OWN lists (where the real names actually live); and (c) only genuinely public, verifiable role-archetype anchors, clearly labeled. The names are founder-side; the targeting system is the deliverable.

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

The precise buyer ICP (use this as the qualification checklist):

The sourcing method the founder runs against his OWN lists (this is where the real names are):

  1. Sanity Check subscriber list (highest-warmth source). Export subscribers; filter by job title for the title cluster above; cross-filter by company size (enrich via Clearbit/Apollo or manual LinkedIn lookup) to the 100-500 band. A subscriber who already reads RDCO's data content AND holds a budget-bearing data title is the warmest possible lead. Rank by engagement (opens/clicks) as a proxy for receptiveness. Realistically the top 3-5 RDCO names come from here.
  2. phData pipeline / phData-adjacent network (highest-fit source). The founder's day-job exposure puts him in front of exactly this buyer at exactly the moment of a stuck data project. Note the no-conflict guardrail: phData plays the $150K-$500K specialist-consultancy tier; RDCO plays the sub-$30K/month band below phData's floor. The clean, non-conflicting plays are (a) accounts phData declined/de-scoped as too small, and (b) past contacts at companies now in the 100-500 band who have a build-shaped need phData wouldn't take. Treat this as a relationship-mapping exercise, not a poach.
  3. LinkedIn Sales Navigator (cold but enumerable). Save a search with the Boolean title string + Director/VP/CXO seniority + 51-500 headcount + Engineering/IT function + (the high-signal kicker) "Changed Jobs in last 90 days." New data leaders in "prove myself" mode are the highest-converting cold segment. Then narrow to 1st/2nd-degree connections first — warm intros beat cold outreach for a $20K/month sale.
  4. Community mining (medium-warmth, builds the create-the-category flywheel). Data Council attendees, dbt Coalesce speaker/attendee lists, Locally Optimistic and dbt-community Slack participants who post about stalled data/AI projects or tooling gaps. These double as Sanity Check distribution and lead sourcing.

Cross-reference the four sources to find the gold: anyone who appears in 2+ of (Sanity Check engaged subscriber) × (phData-adjacent contact) × (1st-degree LinkedIn) × (active in a data community) is a TIER-1 lead. Run the intersection, not the union.

On named, verifiable individuals (the anti-fabrication discipline): I am returning ZERO invented names. The only buyer-side individual the vault records by name is Aaron Levie (CEO, Box), via his publicly-circulated "agent deployer and manager on every team" job description (primary source https://x.com/levie/status/2043883641366032638, read in full this session). But Levie is a CEO-altitude advocate that the role should exist — he is NOT a director/VP-Data who would retain RDCO. He belongs in the brief as category-legitimacy proof, NOT on a leads list. Every actual lead name must come from the founder running the method above against his own lists. 2 honest anchors (the ICP definition + the Levie role-legitimacy reference) beat 10 fabricated names.

Open follow-ups

Sources

Vault:

Web (accessed 2026-05-31):

Not accessed / honest gaps: Sanity Check subscriber list and phData internal pipeline are founder-side, not reachable by the sub-agent — they are where the real named list lives. No named individual leads are fabricated in this brief.