The 6 crypto catalysts BD teams track on Compass

The 6 crypto catalysts that make BD outreach timely: raises, mainnets, listings, key hires, grants, and events. Plus the 3-check noise filter.

Which crypto catalysts matter most for BD?

6 crypto catalysts change BD timing: funding rounds, mainnet launches, listings, key hires, grants, and events. Each one hands a specific person a reason to reply this week. Nothing else in the feed does that.

The raise is the clearest of the 6. Open Sentient, an AI project, and the backers sit right on the profile: Hack VC, Delphi, and Foresight. New budget plus named backers gives you a route and a reason in one screen.

A key hire is the most person-shaped catalyst. Sentient lists Yura as Head of BD, and a BD lead answers partner notes for a living. The hire hands you a named owner.

Launches and listings are dated and public. An upgrade on a chain like Injective or Aptos creates integration work within weeks. A listing on a venue like OKX does the same for market makers and token teams.

Grants and events close the list. Ecosystem grant programs, with TON the obvious example, turn funded teams into buyers. A conference or a wallet integration, say with Phantom, concentrates attention for about a week.

Bar chartCatalysts by outreach usefulnessWork your queue from the top of this chart down. Values are relative BD priority, not market data; every bar links to a live page.
Funding roundNew budget, and the backer list names your route.
Key hireA new owner, like a Head of BD, with an empty pipeline.
Mainnet launch or upgradeIntegration work follows chains like Injective.
Grant programEcosystem money, TON-style, turns teams into buyers.
Exchange listingA dated reason for market makers and venues like OKX.
Conference or integrationReal hook, short shelf life; think wallet distribution via Phantom.

How do you separate catalyst timing from noise?

Run the 3-check filter: the event has a date, your contact owns it, and it rewrites your first line. A real catalyst passes all 3. Noise fails at least 2.

The 3 noise types are easy to name: a token price move, a viral post with no follow-through, and a headline from 2 quarters back. Each one explains why you noticed the account. None survives the filter.

The date check does most of the work. Price moves and viral posts carry no date a BD conversation can use. A raise, a listing, an upgrade: each arrives with one.

The table stretches the 3 checks into 5 team-ready rows. Work top to bottom and stop at the first fail.

TableCatalyst quality checkRun all 5 rows before a send. One fail moves the account to monitor; 2 fails park it.
CheckPass conditionWhere to check
SourceA primary announcement with a date and an actor.Catalysts
Account fitThe account matches a priority you already hold.Companies
Person fit1 named person has a reason to care.People
RouteYou know if the path is warm, cold, or held.Investors
Next stepThe event rewrites your first line.Your draft

What should you verify before using a catalyst?

Verify 4 fields before a catalyst touches outreach: source, date, actor, and relevance. The check takes about 2 minutes with the Catalysts feed open. Skip it and you inherit someone else's error.

Source means primary. The project's own announcement beats a repost, and a dated feed entry beats a screenshot. Secondhand claims get written down as secondhand, not laundered into fact.

Actor and relevance are the human half. Name who did the thing, then say why your contact's role cares. Two blanks you cannot fill means the catalyst is context, not timing.

  • Source: the project said it itself, not a repost.
  • Date: the event sits inside your 2-to-4-week window.
  • Actor: a named team or person did it.
  • Relevance: the event maps to your contact's role.

How should catalysts change BD work?

A catalyst should reorder your queue, not grow it. It moves 1 account up, changes the person you contact, or sharpens your first line. If it does none of those 3, file it as context.

Keep monitoring and sending as separate states. Monitoring means the account earns attention. Sending means you have a person, a reason, and a next step. Good BD teams park most catalysts in monitoring.

Ownership moves with the catalyst type. A raise belongs with whoever covers investors. A listing belongs with whoever covers venues. Assign the owner the day the event lands.

What should you do after you find a catalyst?

Run one pass: capture, map, owner, route, decide. The 5 steps take about 15 minutes per account after your second try. The output is a decision, not a research pile.

Send, hold, and monitor are the only 3 exits. Send needs the person, the reason, and the route all named. Hold means 1 of those is missing. Monitor means the account matters but this event does not.

Do the pass the same day the event hits the Catalysts feed. Outreach decays across the 2-to-4-week window, and day-1 notes read sharpest.

FlowCatalyst to outreach, one passOne pass takes about 15 minutes per account. Run it the same day the catalyst lands and log the exit.
  1. 01
    Capture the event

    Log the source, date, and actor from the feed.

  2. 02
    Map the account

    Open the project page, for example Injective.

  3. 03
    Find the owner

    Name the 1 person with a reason to care.

  4. 04
    Check the route

    A shared backer or warm path beats a cold send.

  5. 05
    Send, hold, or monitor

    Decide in the same sitting and note it for the weekly brief.

What crypto catalyst mistakes create bad outreach?

3 mistakes turn real catalysts into bad outreach: reading attention as intent, working stale events, and stacking weak signals. Each one produces a note that gets archived on sight. All 3 are avoidable.

Attention is not intent. A project can trend without wanting a partner, and a token can move without the founder caring. Trending tells you where to research, not who to message.

Stale events read worse than no event. Citing a raise from 2 quarters ago tells the reader you found them late. Inside the 2-to-4-week window, cite it. Outside it, find a fresher reason.

Stacking does not work either. 3 weak mentions never equal 1 strong catalyst. One dated, owned event beats the pile.

Frequently asked questions

Should every crypto catalyst trigger outreach?

No, most catalysts should end in monitoring. Send only when the event passes all 3 checks: a date, an owner, and a rewritten first line. Expect the filter to hold back more than it releases.

Are social signals enough to justify a send?

No, a viral post with no follow-through is 1 of the 3 noise types. It tells you where you looked, not why your contact should reply. Pair it with a dated event from the Catalysts feed or hold the account.

What makes a crypto catalyst strong?

A strong catalyst carries a date, a named actor, and a person who owns the outcome. A funding round with backers named on the profile, like Sentient's, is the cleanest case. If it rewrites your first line, it is strong enough.

Can an old catalyst still help?

Yes, as background rather than timing. Past the 2-to-4-week window an event explains the relationship but earns no urgency. Let it inform the note and lead with something current.

Where should catalyst research start in Compass?

Start on the Catalysts feed at /news for the dated event. Map the account on /projects, the person on /people, and the route on /investors. The full pass takes about 15 minutes.

Sources and methodology

This article pattern uses Compass data objects: people, companies, investors, catalysts, sectors, and relationship paths. The goal is to keep outreach decisions tied to visible evidence instead of generic market commentary.

Compass Catalysts feedCompass company directoryCompass people directoryCompass investor directoryCompass PulseOKX on CompassInjective on CompassAptos on CompassTON on CompassPhantom on CompassSentient on CompassYura, Head of BD at Sentient