For revenue leaders
Pipeline you can audit down to the cell
A forecast is only as good as the fields under it. Here every attribute names its source, its run and its author, so a number can be checked.
Every sales leader at this size has the same Monday problem. The review runs on fields somebody typed, and half are stale. You cannot tell whether a deal slipped because the buyer went quiet or because nobody updated the record.
Records hold companies, people and deals with a stage model, per-deal stakeholder roles, an activity timeline and provenance on every field. Signals hold what changed at the account. Sequences and Messages hold what the team actually sent and what came back from it.
- Who this is for
- A VP of sales, head of revenue or CRO at a four to fifty person B2B SaaS company, running two to eight sellers with no ops function and no data team behind the numbers.
- What it looks like today
- The pipeline review runs on fields somebody typed last week. Deals are single-threaded, activity is logged when a rep remembers, and nobody can tell a stalled deal from a stale record.
- What changes
- The record layer carries provenance, stakeholders and an activity timeline written by the motion itself. A forecast figure opens into the deals and the runs that produced it.
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.
Deals without a champion
which open deals have no champion identified and nothing logged in the last two weeks
Stakeholder roles are edges on the deal, so a missing champion is a filter rather than a hunch.
Accounts that just changed
tell me which of my open opportunities posted a job or changed leadership this month
The search fills a table you re-run when you want it fresh. Nothing subscribes to these events yet, so the list gets rebuilt rather than remembered.
Where a value came from
show me every field on this account and which run or which person wrote it
Provenance is stored per field, so a value carries an author, a source and a timestamp.
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.
A buying committee on every deal
Each deal carries named stakeholders and their roles, not one contact and a hope.
- 1Define the stakeholder roles you sell to, then attach people to the deal.
- 2Enrich the missing seats from the account, and log every touch on the timeline.
oxygen crm relationships upsertAccount changes that reach a human
A hiring or leadership change at an open account lands on a list your team reviews, not in a newsletter.
- 1Run a hiring or leadership search across your open accounts on a cadence, and let it fill a table you actually read.
- 2Pick the accounts where the change matters, then enroll those owners in a short human cadence rather than a blast.
oxygen signals search runA forecast that opens
Stage counts, deal value and slippage that click through to the record behind them.
- 1Set the pipeline stages your team argues about, then read the summary.
- 2Open any figure into the deals, the fields and the activity that produced it.
oxygen crm pipeline
Capabilities
What you get
Provenance on every field
An attribute names the run, provider or person that wrote it, and when. A review can check a value instead of debating whether anyone touched it lately.
The buying committee as structure
Deals carry stakeholders with roles: champion, economic buyer, decision maker, influencer, end user. A single-threaded deal shows as a gap, not a surprise in week ten.
Outreach and the record together
What the team sent, what came back and the stage that resulted live in one database, so the timeline stops being a logging chore nobody keeps up.
Reporting you can hand upward
Curated dashboards read the tables the motion writes, so a board figure and the deals behind it are one query, not two exports reconciled by hand.
Instead of
The stack this replaces
Native, on one contract and one credit balance — not another tab wired to the last one.
- HubSpot
- Attio
- Salesforce
- Clay
- Apollo
- Looker
Data sources
What the data actually comes from
Every value lands with its provider and cost recorded on the cell.
People Data Labs
Backfills company and person attributes so an account is complete before a review.
PredictLeads
Hiring, technology and connection events per company, so a review can see what changed at an account.
Blitz API
Resolves the stakeholder you are missing on a deal and heads the work-email chain.
LeadMagic
Adds mobiles and the contacts the first lane missed, including outside the United States.
Crustdata
Headcount and posting trends, so growth or contraction at a customer shows up early.
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
- A stage model is a decision, not a default you can skip. The shipped pipeline fits most early-stage B2B SaaS, but an unusual motion needs a working session before the reporting is trustworthy.
- Account events tell you something changed. They do not tell you a deal is in trouble. What a leadership change means for one opportunity is still your team's judgment.
FAQ
Questions people ask first
Is this a CRM or a prospecting tool?
How do I know a field is current?
Can we keep the CRM the team already uses?
What does a deal record actually hold?
Will my reps have to log activity by hand?
How is spend controlled if the team enriches freely?
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.