OXYGENOXYGEN

For edtech startups

GTM infrastructure for edtech startups

Education buys on a calendar, not on a quarter. Reaching the right person in the wrong month is the most common way an edtech pipeline dies quietly.

try
Start freeRead the docs

Education is the rare market where your buyer's org chart is published. Districts list their technology directors, universities list department heads, and most institutions state their enrollment somewhere on their own website.

The problem is that it sits across ten thousand sites. Turning it into rows is a research build: source institutions, read their pages for size and structure, then find the named role on each one before anybody writes a first email.

Who this is for
Seed to Series A education software companies selling to schools, districts, universities, or training providers. Four to fifty people, founder led sales with long cycles.
What it looks like today
Institutions publish their staff directories and hide almost nothing, yet the standard sales database knows none of it. Meanwhile a deal that misses the budget window waits a full year for the next one to open.
What changes
The institution list is built from public sources and enriched with the roles that matter, then worked on the calendar. Every conversation, pilot, and renewal date stays on the record between cycles.

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.

  • Districts above a size floor

    list public school districts in these three states with more than five thousand students

    Enrollment lands as a numeric column, so you can set the floor exactly where your pricing starts to work.

  • The role, per institution

    find the technology director or head of digital learning at each of these districts

    The title varies by state and size, so the table records the exact role it resolved for each institution.

  • Who already runs a competitor

    check each institution site for mentions of the platform we replace

    The mention and its source page sit on the row, turning a guess about the incumbent into something checkable.

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.

  • Institution map

    A row per district or campus, with size, structure, and a named role.

    1. Tables
    2. Records
    3. Tags
    1. 1Source institutions by state and type, then read each site for size and structure.
    2. 2Tag by segment and promote the ones inside your pricing band.
    oxygen companies search plan

  • Time the calendar

    Sequences that land in budget season rather than in the middle of exams.

    1. Workflows
    2. Sequences
    3. Records
    1. 1Record each account's budget and renewal timing as fields on the record.
    2. 2Schedule sending from those dates instead of from the day the list was built.
    oxygen sequences create

  • Pilots that do not get lost

    Pilots and champions on the institution record, stage movement in the funnel summary.

    1. Records
    2. Messages
    3. Dashboards
    1. 1Log pilot state, named champions, and the next follow up date as activity on the institution record.
    2. 2Read the account's own timeline for detail and the funnel summary for stage movement across the segment.
    oxygen crm activity timeline

Capabilities

What you get

  • Public structure, turned into rows

    Institution size, type, and staff roles are published but scattered. A sourcing run plus a read column collects them into a table you can actually filter.

  • Timing stored on the record

    Budget windows, renewal dates, and term boundaries live as fields, so a sequence is scheduled from the account rather than from the campaign calendar.

  • Long cycles that survive a rep change

    Champions, pilots, notes, and replies attach to the institution, so a deal picked up next year opens with its own history intact.

  • Free to build the map

    Tables, workflows, and drafts cost nothing. Sourcing institutions, reading their sites, and contact lookups draw credits, and every run previews its scope and ceiling before it starts.

Instead of

The stack this replaces

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

  • Clay
  • Apollo
  • Smartlead
  • HubSpot
  • Google Sheets
  • Zapier

Data sources

What the data actually comes from

Every value lands with its provider and cost recorded on the cell.

  • Op

    Open Web Ninja

    Listings for schools, campuses, and training providers by city, which is how the map gets started.

  • Exa

    Web search for institution pages, staff directories, and the documents that state enrollment.

  • People Data Labs

    Records for larger institutions and private providers that behave like ordinary companies.

  • Blitz API

    Finds the named technology or academic role behind an institution instead of a general office address.

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

  • Public institutions move slowly and publish inconsistently. A directory page can be a year out of date, so verify a named contact before a campaign rather than trusting the crawl.

FAQ

Questions people ask first

Can we source districts and schools separately?
Yes, and you should. A district is the buyer for some products and an individual campus for others, so they belong in different tables with different qualifying columns and owners.
How do we handle procurement requirements?
By recording them. Whatever an institution requires goes on the record as a field, so the account shows what is needed before anyone promises a timeline the team cannot meet.
Is email the right channel here?
It is the practical one. Institutional addresses are public and durable, and the same cadence can include a call step for the accounts where a phone number resolved.
What about seasonality?
Build it into the account rather than the campaign. Sending is scheduled from the dates on each record, so a district that decides in March is not contacted in the same wave as one that decides in August.
Can two people work the same list without colliding?
Yes. Accounts carry an owner, activity is logged against the record, and suppression is workspace wide, so two people working one market do not double contact an institution.
Does the free workspace cover a first build?
For a first state or two, comfortably. Sourcing and reading sites are metered per row, contact lookups bill on a hit, and each run states its ceiling before it begins.

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