For edtech

The agentic GTM platform for edtech sales teams

Education buys on a calendar, not a quarter. AI agents find the right person, and a daily workflow you build reaches them when the budget opens.

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 thousands of sites. Turning it into rows is a research build. Source institutions, read their pages for size and structure, then find the named role at each one before anybody writes.

Who this is for
The GTM (go-to-market) team at an education software company with a proven offer. It sells to schools, districts, universities, or training providers. Two or more sellers work long cycles account by account.
What it looks like today
Institutions publish their staff directories and hide almost nothing, yet a general sales database holds only part 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

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

  • 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. 2Promote the institutions inside your pricing band to Records, then tag each record with its segment.
    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. 2Keep the sequence's enrollment manual, then build a daily workflow that enrolls each account's contacts when its budget date comes up.
    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 workspace funnel summary for how replies turn into meetings and deals.
    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 on the account. A scheduled workflow you build reads them each day and enrolls that account's contacts in the sequence when its window opens.

  • 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 tables, metered sourcing

    Tables, sequence drafts, and building a workflow cost nothing. Sourcing institutions, reading their sites, and contact lookups draw credits, and each of those runs carries a credit ceiling.

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

  • Serper

    Google Maps 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, run when you pick it by name.

  • Blitz API

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

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

  • 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. Keep them 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. The account then 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. Where a phone number resolved, the same cadence can add a call step. A rep dials from the web softphone, a beta an admin turns on in Settings, on a number bought on a paid plan.
What about seasonality?
Build it into the account. Store each decision date on the record, and have a daily workflow enroll the contacts of accounts whose window is opening. A district that decides in March is then not contacted with one that decides in August. A sequence can schedule its own start, but that is one date for the whole campaign, at most 30 days ahead.
Can two people work the same list without colliding?
Yes, if each institution has one owner. Accounts carry that owner, and activity is logged on the record. Two campaigns can still enroll the same person. Skipping leads already in another active sequence is off by default. It matches LinkedIn identities only, so an email-only lead is never checked. An email opt out blocks only that address, in every campaign.
Does the free workspace cover a first build?
Enough for a small first slice, not a whole state. Sourcing bills per page of results and reading a site bills per row. Managed finders bill on a hit. Email checks bill even on a miss. A row with a name and a domain but no LinkedIn URL first checks up to 8 guessed addresses. Every run you start carries a credit ceiling, so size one institution type in one region before going wider.

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