For devtools startups
GTM infrastructure for devtools startups
Developer tools sell to people who spot a broker list instantly. The fix is better targeting, not better prose.
A devtools ICP is defined by what a team runs, not by which industry box it sits in. Two companies with identical headcount and funding are different accounts if one is on Kubernetes and the other is not.
The whole motion lives in one workspace. Tables hold the working list with typed columns and run history. Signals hold hiring and stack events on the account. Sequences own the cadence and the senders.
- Who this is for
- Seed to Series A developer tool companies where a founder still owns revenue. An API, an observability tool, a CI or platform product. Four to fifty people, no GTM engineer.
- What it looks like today
- Your buyers are engineers, so the usual playbook lands badly. A list bought by industry and headcount is mostly companies that will never run your stack.
- What changes
- Targeting starts from the stack and the roadmap. You build the list from technographics and hiring, enrich it where the list lives, and write from something the account actually did.
Example searches
Ask for it the way you'd say it
Every search below runs on the same hosted Tables, with the cost previewed before anything is spent.
Teams already on your stack
find series A companies running kubernetes who posted a platform engineer role this quarter
Detected technology and posting-derived technology arrive as separate columns.
The person who signs off
for each company here find the vp of engineering or head of platform with a work email
The work email lands on the same row as the detected stack and the open roles, so the opening line and the address come out of one lookup.
Migration moments
tell me when a company in my list posts a role naming a database I can replace
The posting lands as a durable signal on the account, not a one-off alert.
Plays
Three motions you can run this week
Each one is a chain of Oxygen primitives — the same hosted objects your workspace already has, composed.
Stack-matched account build
A list where every account already runs something you attach to.
- 1Write the ICP into the workspace wiki so every run reads it.
- 2Source by technology and hiring, enrich in place, promote what fits.
oxygen lead-sourcing planEngineer-safe first touch
A short first message naming a real detail, not a merge field.
- 1Add an AI column drafting one line from stack and open roles.
- 2Review a sample, then enroll the approved rows.
oxygen sequences startDocs traffic to pipeline
Companies reading your docs become accounts, not an analytics chart.
- 1Send website visitor events in and attach them to accounts.
- 2Rank by pages viewed and stack match, then enroll the top slice.
oxygen signals leads-today
Capabilities
What you get
Targeting from the stack
Build lists from technology detected on a domain and technology named in job postings, then filter by headcount.
One workspace instead of five tools
Sourcing, enrichment, the CRM, sequences, the inbox, and reporting share one tenant database. Nothing syncs between vendors.
A terminal-first surface
The CLI and MCP server expose the same actions as the web app over the same API, so a founder or an assistant can script a build.
Start without a card
A new workspace lands with 10,000 credits, no card and no clock. Tables, the CRM, workflows, and drafts are unmetered; agent runs, enrichment, and AI columns draw credits.
Instead of
The stack this replaces
Native, on one contract and one credit balance — not another tab wired to the last one.
- Clay
- Apollo
- Instantly
- HubSpot
- n8n
- Zapier
Data sources
What the data actually comes from
Every value lands with its provider and cost recorded on the cell.
TheirStack
Job postings and the technologies named inside them, which catches a stack decision early.
BuiltWith
Technology detected on a company domain: the frameworks, clouds, and tools visible from outside.
PredictLeads
Company events including hiring, so a platform team staffing up becomes a reason to write.
Blitz API
Public LinkedIn company and profile data, which is how the platform owner at an account becomes a named person instead of a job title.
Run these on Oxygen's managed credits, or connect your own provider keys and pay the vendor directly — the same columns, the same runs, the same provenance either way. See every integration.
Limits
Where this stops
- Detection sees what is public. A company running your category behind a private network may not show it, so treat a negative match as unknown.
FAQ
Questions people ask first
Why not just buy a technographic list?
Does this work if my buyer is not the CTO?
Can I keep using my own provider keys?
How does an AI assistant fit in?
What does it cost to start?
Do I need a GTM engineer to run it?
Put your GTM motion on one stack
Sign up, get a working workspace with a one-time credit grant, and run the first play end to end without wiring five tools together.