From “Who uses it?” to “Who ships with it?”

There’s a quiet but consequential shift happening in how software gets sold. For a decade, B2B go-to-market relied on what I’ll call logo heuristics. If a database said “Company X uses Tool Y,” we aimed, fired, and hoped something moved. That approach made a kind of sense when software buying was centralized and slow, and when “adoption” looked like a contract signed by a procurement lead after a series of demos.

But the center of gravity has migrated. In modern engineering orgs, adoption starts where code ships. The people who decide whether your tool becomes indispensable aren’t the ones signing the MSA. They’re the ones with commit rights.

This is the gap DX set out to close with LeadGenius Contact-Level Technographics (CLT)—a shift from “Which companies have it?” to “Which people actually use it, for what, and alongside what else?” It sounds like a nuance. It isn’t. It’s a different theory of go-to-market.

The epistemology problem in B2B data

Traditional vendors sell what amounts to company-level claims: “This logo uses that tool.” Sometimes that’s accurate. Often it’s out of date. Almost always, it’s too blunt to guide real orchestration—events, content, campaigns—because it can’t answer basic operational questions:

• Is the company actually using GenAI? Which GenAI tools?
• Who are the users—engineers, SREs, data scientists, platform teams?
• What else is in their toolchain—Backstage, Datadog, or something idiosyncratic?
• How do we convert that knowledge into pipeline rather than just activity?

CLT approaches the problem like a good reporter: start with receipts. Public-web artifacts—commits, issues, profiles, Q&A, docs, job posts—are resolved to work identity. That identity is slotted into a buying group map: builders, influencers, evaluators, decision makers. And then it’s refreshed, because these stacks live and breathe.

What DX actually wanted

DX sits at a crossroads inside the enterprise—part platform, part developer experience, part growth. Their mandate is pragmatic: drive adoption, events, and revenue by finding where the real users are. Not personas. People.

The short list:

• Real GenAI coverage at the user level. Who’s on Claude, GitHub Copilot, Tabnine, Cursor?
• Precise audiences tied to target technologies like Backstage (dev portals) and Datadog (observability).
• Fuel for event marketing and thought leadership—VIP lists, session design, regional clustering, and content that speaks to what teams actually run.
• A continuously updated account map that raises contact intimacy and accelerates deal cycles.

This is not a better list. It’s a better model.

What the dataset says, and why it matters

When we parse the working sample, three things jump out:

• 406 target accounts analyzed
• 222 with at least one GenAI coding/assist tool in live use at the contact level
• A 54.7% GenAI adoption rate across the target universe

Tool-specific footprints at the account level look like this:

• Claude: 86 accounts
• GitHub Copilot: 71
• Cursor: 137
• Tabnine: 17
• Backstage (non-GenAI): 104
• Datadog (non-GenAI): 314

And there’s a long, telling list of multi-GenAI accounts—Google, GitHub, Amazon, Apple, Atlassian, AMD, Fidelity Investments, EPAM Systems, Elastic, Expedia Group, Canva, CGI, ByteDance, Bosch, FIS—where the developer stack is both diverse and opinionated. That last part matters. Opinionated stacks predict purchase motion: standards emerge, and new tools must fit.

This is a different way of estimating readiness. It’s not, “Are they in our TAM?” It’s, “Is the team already behaving like our best customers behave?”

The three plays that turn usage into pipeline

A) Precision Event Marketing
Events are the most honest channel in go-to-market. Either the right people show up and talk about real work, or they don’t. With CLT, DX builds VIP shortlists by city and region, clustering GenAI users and Backstage/Datadog practitioners. Invites reference actual toolchains. On site, seating and staffing are guided by usage density—where Copilot + Backstage overlap, you put a solutions architect, not a swag table. Post-event, scans auto-enrich; follow-ups reference the session attended and the tools already in use.

B) Thought Leadership with receipts
Most B2B “thought leadership” is a survey dressed as a whitepaper. CLT lets DX publish something sharper: a quarterly State of GenAI in Engineering, grounded in observed practice—Claude vs. Copilot penetration by industry/region, overlap with Backstage and Datadog, usage-density tiers that correlate with velocity. Then package it into pragmatic playbooks: “How teams ship faster with GenAI + Backstage” and “Observability patterns in GenAI-augmented pipelines.” Panels feature real practitioners surfaced by the contact graph.

C) Sales coverage and contact intimacy
Coverage isn’t how many titles you hold in CRM. It’s whether you have the right conversations in the right order. CLT maps the universe—builders → influencers → evaluators → decision makers—so SDRs begin with users and champions, then multi-thread up with integration-specific talk tracks. That sequencing does two things: it shortens cycles and it de-risks the deal by anchoring it in working practice rather than promise.

What changes when you adopt this model

• Event ROI goes up. Referencing a prospect’s real tool usage lifts acceptance and show rates. On-site routing based on usage density drives live conversions.
• Cycles get faster. Champion-led, tool-specific threads reduce the number of “prove-it” loops.
• Attribution gets cleaner. Because cohorts are built on observed behavior, not form-fill fiction, lift is measurable and repeatable.
• Coverage improves. You stop mistaking “title coverage” for “user coverage.” The latter is what pulls deals over the line.

There’s a clean way to say this on a slide:
Title coverage ≠ user coverage. User coverage = pipeline.

The process (so you can imagine doing it)

DX didn’t need a moonshot; they needed a motion.

1. Signal backfill (2–3 weeks): Resolve receipts to identities; stand up GenAI + Backstage/Datadog flags.
2. Audience kits (weekly): Net-new users, job-changers, new regions; export straight to MAP/CRM.
3. Event pods (rolling): City clusters, VIP routing, session design, staffing plans.
4. Content ops (quarterly): Benchmarks, panels, briefs—repurposed into ads, emails, and SDR talk tracks.

This is how you replace busywork with signal-based selling.

A brief note for the skeptics

You might read this and hear nothing more than another data product promise. I’d argue it’s an operating philosophy. The Challenger part isn’t “our data is better”; it’s that the unit of analysis has changed. The interesting question is no longer, “Do they have the software?” It’s, “Who are the people who can’t get their work done without it?”

Answer that, and you don’t just improve campaigns—you reorder the sales conversation. You walk in with receipts, with a map, with the understanding that adoption isn’t achieved by persuasion alone. It’s achieved by meeting the builders at the boundary between tool and workflow, and then helping them win.

Why bespoke beats leased logos

The future of go-to-market isn’t guessing which logos might be a fit. It’s custom insight tied to who does the work, updated as their stack evolves. Databases tell you where to knock. CLT tells you who opens the door, why they care, and what you should bring.

If you’re DX—or anyone tasked with turning GenAI noise into adoption and revenue—that’s the difference between running plays and running plays that work.

‍