Used for: Weekly outbound to accounts with a recent hiring signal in Clay.

Works well: Signals land as rows, so there is nothing to scrape. Reply rate on signal-based lists was clearly higher than on static lists.

Could be better: CRM sync is only on the Team plan, which we needed.

Used for: Funding and job-change signals for a mid-market list.

Works well: Setup took an afternoon and the scoring rules are easy to read.

Could be better: Signal history is limited to 90 days.

Used for: Slack alerts for new hiring spikes.

Works well: Free plan was enough to test it properly.

Could be better: Hourly signals need Pro.

Used for: A 3,000 account list across two teams.

Works well: The Clay integration works well.

Could be better: Costs rise quickly once you add seats.