Score your CRM on what people build today.

CRM data is slow and reactive. GitHub is fast: see what your technical targets are working on right now, where they live and what they are about to build.

Engineers at target accounts building agents

  • Evan Mattson
    @moonbox3
    May
    Jun
    Jul
    Aug
    Sep
    Oct
    Nov

    Principal engineer driving agent orchestration and AI tooling at Microsoft

    Drives AI agent learning resources and orchestration protocol work at Microsoft. Lands changes in a2aproject/A2A, a protocol for communication between agentic applications.

  • Mackenzie Zastrow
    @zastrowm
    May
    Jun
    Jul
    Aug
    Sep
    Oct
    Nov

    Sr. engineer at AWS building production agent SDKs

    Delivers agent SDKs at Amazon Web Services. Contributes to strands-agents/harness-sdk, a software development kit for building AI agents, and strands-agents/tools, a set of tools for agents.

  • Scott Mansfield
    @ScottMansfield
    May
    Jun
    Jul
    Aug
    Sep
    Oct
    Nov

    Go and TypeScript Staff engineer bridging infrastructure and AI agents at Google

    Ships AI agent tooling in TypeScript at Google, after software engineering at Meta. Contributes to Netflix/rend, a memcached proxy for managing data caches.

Use cases

For your customers

  • Which of my accounts have engineers building agents?
  • Which startups’ engineers are testing pgvector?
  • Who at my accounts started using MCP this month?
  • Which contacts on this list build what I sell?

For your product

  • Which of our contact records match a GitHub profile?
  • What does each engineer at this account build?
  • Which records belong to people who just changed jobs?
  • When did each person on this account last ship code?

For founders, product, data and partnerships teams.

Fresh signals your customers can act on this week.

Today
Firmographics and titles that update after the fact.
With Vamo
What every contact is building right now, on every record.

How it works

  1. Step 1

    Send your records

    Pass contacts or accounts over the API: a name and company, a LinkedIn or a GitHub.

  2. Step 2

    Get the builder signal back

    Each person matched across GitHub and LinkedIn, with what they build, their languages and a ranked score.

  3. Step 3

    Ship it as a column

    Show it on every record, let customers filter by what people build, and keep it fresh as they ship and move.

Run it in Claude, or build on the API. See how Vamo compares with people data APIs.

See the column on your own accounts.