For revenue leaders

A pipeline sales leaders can check field by field

A forecast is only as good as the fields under it. Here every field names its source, run and author, so a number can be checked.

try
Start freeRead the docs

Every sales leader has the same Monday problem: the review runs on stale, hand-typed fields. 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, stakeholder roles, an activity timeline and provenance on every field. A signal search collects account changes into a table your team reviews.

Who this is for
A VP of sales or chief revenue officer who runs the GTM (go-to-market) team at a company selling to businesses. It has two or more sellers and often no ops or data team.
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. Pipeline figures count those same deals, and the Pipeline dashboard links to the deal board.

Example searches

Ask for it the way you'd say it

Each example is a request in plain words, with what it returns underneath.

  • Deals without a champion

    which open deals have no champion identified and nothing logged in the last two weeks

    Each stakeholder's role is stored on the deal's link to that person, so whether a deal has a champion is recorded data you can check.

  • Accounts that just changed

    tell me which of my open opportunities posted a job or changed leadership this month

    The search fills a table. Bind it as a feed and it refills on a schedule with only new events. It stops after 5 cycles in a row with nothing new, until you resume it. No workflow trigger fires on those rows yet.

  • 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, so no deal rests on a single contact.

    1. Records
    2. Tables
    3. Messages
    1. 1Choose which of the 5 built-in roles each deal needs, from champion to end user. Then attach people to the deal in those roles.
    2. 2Enrich the missing seats from the account, and log every touch on the timeline.
    oxygen crm relationships upsert

  • Account changes that reach a human

    A hiring or leadership change at an open account lands on a list your team reviews.

    1. Signals
    2. Tables
    3. Sequences
    1. 1Run a hiring or leadership search across your open accounts on a cadence, filling a table you read.
    2. 2Pick the accounts where the change matters. Enroll the person it involves, such as the new leader, in a short cadence you review, not a blast.
    oxygen signals search run

  • A forecast that opens

    Stage counts, deal value and win rate, read from the same deals your team moves on the board.

    1. Records
    2. Dashboards
    3. Observability
    1. 1Set the pipeline stages your team argues about, then read the summary.
    2. 2Open the deal board from the Pipeline dashboard. Open any deal to read its fields, its stakeholders and its activity timeline.
    oxygen crm pipeline

Capabilities

What you get

  • Provenance on every field

    Each value names the run, provider or person that wrote it, and when, so a review checks the value instead of debating it.

  • The buying committee as structure

    Deals carry stakeholders with roles: champion, economic buyer, decision maker, influencer, end user. Each company record counts how many of the 5 roles its deals have filled, so a single-threaded account shows early.

  • Outreach and the record together

    Sends and replies write themselves onto each person's and company's timeline, in the same database as the deal and its stage.

  • Reporting you can hand upward

    Curated dashboards count from the tables the motion writes, so the board and the deals behind it read the same data.

Instead of

The stack this replaces

Native, on one contract and one credit balance, not another tab wired to the last one.

Data sources

Data sources and CRM connections

  • People Data Labs

    Company and person records you can run by name to fill an account before a review.

  • PredictLeads

    Hiring, technology and leadership news 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 for contacts with a LinkedIn URL.

  • LeadMagic

    Mobile lookups for rows outside the United States, and a later lane for contacts the earlier lanes missed.

  • Crustdata

    On your own Crustdata key, headcount and posting trends, so growth or contraction at a customer shows up early.

Use managed credits where available, or connect a supported provider key on an eligible paid plan. Your provider bills its calls; OXYGEN adds a per-call platform fee. Signed-in CRM connections such as HubSpot have no per-call fee. Connected sending accounts reserve monthly credits. See pricing and supported integrations.

Limits

Where this stops

  • The shipped pipeline of Lead, In Progress, Won and Lost fits most sales teams. If your motion is unusual, agree your own stages before you trust the numbers.
  • Account events tell you something changed, not that 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?
Both, deliberately. Records is the canonical layer for companies, people and deals. Tables are where sourcing and enrichment happen, and a row only becomes canon when you promote it.
How do I know a field is current?
Every attribute stores the run, provider or person that wrote it, with a timestamp. Open the value to see its source instead of asking whoever touched the account. Its change history is short: plan on 7 days.
Can we keep the CRM the team already uses?
Yes, if OXYGEN connects to it. Sync runs both ways or one way depending on the CRM, and each run keeps its status, errors and retries. There is no Salesforce sync, so a Salesforce team brings its records in from a file.
What does a deal record actually hold?
Stage, value, the company, the stakeholders and their roles, the activity timeline, provider IDs and provenance per field. The buying committee is stored as linked people with roles, so you can read it at a glance.
Will my reps have to log activity by hand?
Not for outreach: sends and replies land on each person's and company's timeline on their own. A deal's own timeline, and the Pipeline dashboard's cold-deal count, read only what is logged on the deal itself, so log outcomes there.
How is spend controlled if the team enriches freely?
Each paid run carries a credit ceiling, and a daily or monthly budget can cap the workspace's spend. Every cost is recorded per run.

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.

Start freeSee pricing