Bring your signup data, account research and engineering contacts together. Give sellers the context to start a useful conversation with the team.
B2B GTM Teams that love us
Why OXYGEN
Give technical interest a commercial next step.
❌❌❌❌❌❌❌❌···❌
→
OXYGEN
One view of the account
Bring account research, your imported signup data and sales conversations together. Sellers can see the engineering context before asking the team for time.
14122864
16184299
1392456
18214899
15163672
An opening engineers recognise
Reach out around the environment and problem your product supports. Use the evidence you hold to ask a relevant question about the team’s actual work.
Tables
Sequences
Workflows
CRM
Room for your sales motion
Qualify accounts before enriching every contact, then choose the people and outreach steps. Keep technical fit and the commercial conversation connected.
A better evaluation handoff
Save the use case, technical questions and next action when interest moves beyond a single developer. Give sales and technical teammates the same account context.
Build your developer-tools sales motion.
Build your marketAgentExample
Research software companies hiring platform engineers with Kubernetes and GitHub Actions. Match the account list to our imported business signups and find the platform lead.
OXYGEN Agent
I’ll search your data sources, combine the results, and keep one record per company.
ApolloCompany & people search
Searching
BlitzAPIFind the buying team
Searching
Sales NavigatorSearch your saved audience
Searching
Ocean.ioDiscover lookalike companies
Searching
↳
Technical account fit and matched business signupsCompany · Domain · Buying team · Source
Deduplicated
Build your marketAgentExample
Research software companies hiring platform engineers with Kubernetes and GitHub Actions. Match the account list to our imported business signups and find the platform lead.
OXYGEN Agent
I’ll search your data sources, combine the results, and keep one record per company.
ApolloCompany & people search
Searching
BlitzAPIFind the buying team
Searching
Sales NavigatorSearch your saved audience
Searching
Ocean.ioDiscover lookalike companies
Searching
↳
Technical account fit and matched business signupsCompany · Domain · Buying team · Source
Deduplicated
Inbound leadsTablesExample
All leads 4Enriched
Email waterfallTry the next provider when no email is found
Start with signups and product data you import from a source you control. Check which company each person belongs to before sales follows up. The examples below are made up to show the method. A signup alone does not prove that a team wants to buy.
Find the accounts your product belongs in.
Build a list around the tools and problems your product supports. Keep the source beside each finding so a seller knows what to ask about.
Put company research, relevant hiring and tech data in a Table with the source and date.
A tool named in a job ad may be a clue. Check whether the team uses it before you pitch around its setup.
Make the first conversation technically relevant.
Give the seller enough context to ask about the team's work. Find the people close to that problem and prepare email and LinkedIn outreach.
Find the right engineering contacts, add their work details and check their email addresses.
Use your offer and sourced account facts to draft the opening. Review the copy and sending settings before you start the campaign.
Give product interest a commercial next step.
Help sales choose which imported signups deserve a team review. Use the company match, account history and what the person tells you.
Import the signup or product data you control. Check the company match against your existing Records.
Save the use case, people involved and agreed next step. Ask about budget and who decides rather than infer them from a signup.
Illustrative account decisions
What you know
A person signs up with a work email at a target company. A job ad mentions Kubernetes. The team has not told you what it uses.
What it means
The company fits and there is a useful question to ask. The job ad does not prove what the team has installed or plans to buy.
What happens next
Save the signup source and date. Ask which release task the person wants to improve before you pitch a change across the team.
What you know
The signup uses a personal email. You cannot yet match it to a company. A star on a code repo is the only other activity.
What it means
Hold the sales handoff. A guessed employer and a star do not tell you what a team needs or give you consent to contact its staff.
What happens next
Keep the company blank. In the next allowed chat, ask about the person's project and team. Do not look up contacts at a guessed employer.
What you know
The developer describes a release problem and asks the platform lead to join a review of one team workflow.
What it means
You now have a team problem and a person to work with. Ask who owns the budget and what a useful test must show.
What happens next
Save the use case, people involved, test question and agreed next step. Give that brief to the seller so the team does not have to start again.
Use seven fields in the brief: source event, date, company match, confirmed use case, question to test, next owner and agreed next step. Leave unknowns open. Keep the next chat on the same account record.
Sending, infrastructure & usageSee every account, inbox and workflow cost.+
What you need
Price
Billing unit
What’s included
Connected accountsEach connected account reserves its credits every month.
Your own mailbox
$1 (100 credits)
mailbox / month
Connect a mailbox you already own. Warm-up included. Managed inboxes pay this fee too.
+Managed inboxes and deliverabilityOXYGEN buys the domains and inboxes and keeps them warm.
Google Workspace inbox
$4 (400 credits)
inbox / month
300 for the mailbox plus the 100 connected-inbox fee, billed separately. Warm-up included. Up to 5 per domain.
Microsoft 365 inbox
$4 (400 credits)
inbox / month
300 for the mailbox plus the 100 connected-inbox fee, billed separately. Warm-up included. Up to 5 per domain.
Azure tenant
$40 (4,000 credits)
tenant / month
One Microsoft tenant for one domain, up to 100 inboxes. Each inbox adds 25 credits ($0.25) a month for its connection, warm-up included.
Sending domain
$12.50 (1,250 credits)
domain / year
A .com at the registrar's price, renewed yearly. Other endings are priced when you pick them.
Inbox deliverability
$1 (100 credits)
inbox / month
Optional monitoring with 2 placement tests a month. Extra tests 66 credits ($0.66) each.
Dedicated IP
$25 (2,500 credits)
IP / month
Optional. Every mailbox connection leaves from one IP you can allowlist.
Your own Entra mailbox
$0.25 (25 credits)
mailbox / month
Sequencer and warm-up included. Entra sending limits apply; managed tenant hosting is separate.
LinkedIn account
$34 (3,400 credits)
account / month
Connections, messages and InMail included.
WhatsApp number
$34 (3,400 credits)
number / month
Messages included.
Phone number
$10 (1,000 credits)
number / month
Calls use 5 credits ($0.05) a connected minute.
X account
$10 (1,000 credits)
account / month
Posting and engagement included.
Credits and usageCredits pay for enrichment, AI and workflow steps.
Workflow step
$0.0005 (0.05 credits)
per tool step
Charged for each step that calls a tool, plus that tool's own price. Triggers, filters, branches, loops, merges, waits, approvals, code and row writes are free.
Email address found
$0.085 average (8.5 credits)
per email found
Charged only when one is found. Cheaper providers are tried first.
Mobile phone found
$0.99 average (99 credits)
per phone found
Charged only when one is found. Cheaper providers are tried first.
A simple email setup:Three Google Workspace inboxes on one domain use 1,200 credits ($12) a month, plus 1,250 credits ($12.50) a year for the domain. Warm-up and sending are included.
Can sales use our signup data alongside account research?
Yes. Import the business signup or product evidence your team controls, then match it to company Records and research the account. That gives the seller context for a useful follow-up. OXYGEN does not automatically receive private product events or identify anonymous developers from this page. A signup establishes interest in trying the product; sales still needs to confirm the team’s use case and the next commercial step.
Can we find accounts using the technologies our product supports?
Use supported technology data and public engineering evidence to research the environments your product fits. Keep detected technology separate from a tool mentioned in a job description, with the source available to the seller. The evidence helps prioritise accounts and prepare a technically relevant opening. It does not establish a production deployment, an active replacement project or a purchase decision on its own.
How do we get beyond a single developer champion?
Research the engineering team around the same company and find the people relevant to using, implementing and buying your product. OXYGEN keeps those contacts with the account context and helps prepare email and LinkedIn outreach. Begin with the champion’s actual use case, then bring in a platform or engineering lead when there is a reason for a team evaluation. Do not assume that an individual signup carries budget authority.
What happens when an account agrees to an evaluation?
Keep the technical questions, confirmed requirements, people involved and next action with the company and contact Records. Supported replies remain available in Messages, so the next seller or technical teammate can continue the conversation. Workflows can connect reply handling with CRM updates. The product scenes are examples; they do not represent a completed customer evaluation or a measured increase in qualified pipeline.
Will this work with the CRM and agents we already use?
You can work in OXYGEN’s web app, connect a coding agent through the CLI or MCP, and use the same workspace data. HubSpot supports bidirectional sync; Attio receives updates and Pipedrive can be imported. Salesforce sync is not available. Keep your current mailboxes connected for outreach or choose managed infrastructure. Account, contact, conversation and next-step context stays available to the team in OXYGEN.
Where should a developer-tools team start?
Pick one engineering use case and the account characteristics that make it relevant. Bring a small set of business signups or other first-party evidence you control, then inspect the account match and research before enriching contacts. Tim’s lead-source framework treats that first-party context as a useful starting point. Prepare a focused approach and review the campaign before launch; the free tier lets you inspect the workflow, while managed usage consumes credits.