Most teams that run outbound off funding announcements define the trigger as "companies that raised". That is not a trigger. It is a firehose, and working it costs more time than doing nothing.
The fix takes about twenty minutes and it happens before you touch any tooling.
Write the trigger as a filter someone else could run
Four dimensions. Be specific on each one.
Stage. A seed company and a Series D company buy completely differently. Seed has one person making the call and no procurement. Series D has a security review. Pick the stages that match how you actually sell. A $50k ACV product has no business chasing pre-seed.
Amount. Round size is a rough proxy for what they can spend. Set a floor and be willing to raise it. If your product costs $2k a month, a $500k round is not your customer.
Geography. Only the countries you can sell into and support. Timezone and language matter more than people admit when they are drawing the map.
Industry. Narrow to segments where you have proof. A reference in the same vertical is worth more than three extra prospects outside it.
Written out, mine would read: seed through Series B, at least $2M, in Germany, France, the Netherlands or the Nordics, in software or fintech.
If you have not defined an ICP this precisely before, the ICP framing in Lenny Rachitsky's newsletter is a reasonable starting point. The funding trigger is just your ICP plus a timing condition.
The test
A good trigger produces a handful of companies a day that a rep is glad to see. Not a hundred. If your filter returns two hundred rows, you have built a list, and a list gets ignored.
The instinct is to widen so nothing is missed. Resist it. Reps calibrate on the first twenty rows they work. If those are bad, they stop opening the feed, and it does not matter what you send after that.
Timing is part of the trigger
Every vendor in your prospect's category reads the same announcements. The company that raised on Tuesday gets a wave of outreach by Friday, most of it identical.
Two consequences worth planning around. A weekly batch is usually too slow, because by the time you send you are in the middle of the wave. And being early beats being clever: a plain short message on day one outperforms a polished sequence on day ten.
If you fix one thing about your current process, make it the gap between the announcement and your first touch. If that is more than a few days, nothing else you tune will matter much.
What to measure
Three numbers, and be honest about them.
- Announcement to first touch. Days, not weeks.
- Reply rate against your non-triggered baseline. If funding-triggered outreach is not clearly better, the trigger is too broad.
- Share of delivered rows a rep actually works. If they ignore most of it, tighten the filter. A small list that gets worked beats a big one that does not.
Then go build it
Once the trigger is written down, wiring it up is the easy part. I covered a working setup in Build a daily feed of recently funded companies without writing code, and the data quality issues that quietly corrupt these pipelines in Four traps that quietly break funding data pipelines.
If you want to sanity check your filter against real volume before committing, the Datahyena funding rounds actor runs without signup and shows you how many companies a given filter actually returns per day. Worth doing before you promise a rep a feed.
I work on Datahyena, a self-serve API for funding, acquisition and executive-move signals.
Top comments (0)