Automations are one of the most powerful parts of Pesql. They allow you to monitor entire markets, thesis areas and watchlists without constantly refreshing dashboards or manually checking for updates. Instead of spending hours scanning data, you set the intent—and Pesql quietly tracks everything that matters behind the scenes.

This guide shows you how to design automations that surface early signals, detect momentum shifts, and keep your sourcing pipeline consistently warm.

Why automations matter

Private markets move quietly, then suddenly. A company can go from stable to fundraising-ready in a span of weeks. Categories can accelerate before anyone publicly talks about them. Hiring spikes, product releases and domain changes often appear long before capital does.

Automations ensure you never miss these catalysts. They turn Pesql into an always-on assistant: monitoring your thesis, filtering noise, and routing only the most relevant signals back to you.

Designing your first automation

Start by choosing the lens you want to track. The simplest starting point is Fundraising Probability. Select a threshold—such as companies crossing 65 or 70—and link it to the geography, stage or themes you care about. From that moment onward, Pesql actively watches every company that meets those criteria and notifies you when new candidates emerge.

You can refine this further by adding filters around category, headcount, funding history or team size. The tighter the inputs, the more precise the outputs.

Tracking momentum through signal changes

Beyond fundraising, many analysts set up automations to track significant movements inside Heat Score or Growth Score. A company jumping ten points in a week is often an early indicator that something meaningful is shifting internally.

Pesql allows you to monitor:

• Hiring spikes
• Sudden domain or product activity
• Category momentum surges
• Founder role changes
• Comparative outperformance against a peer cluster

These automations are useful because they surface activity you would rarely catch manually.

Automations for watchlists

If you’re managing an active pipeline or longlist, consider linking automations directly to your watchlist. This lets you track when companies you already care about begin to accelerate. You can receive notifications when:

• A watchlisted company crosses a fundraising threshold
• A founder begins to publicly signal a new phase
• Growth momentum significantly outperforms peers
• A hiring change suggests expansion or maturity

This turns your watchlist from static storage into a dynamic monitoring system.

Choosing how you receive updates

Pesql allows you to customise delivery based on how you work.

If you source actively, real-time alerts help you reach companies before others do. If you prefer a more structured cadence, daily or weekly summaries consolidate signals into a digestible view for your workflow or partner meetings. Many teams set weekly updates for IC prep and real-time updates for anything involving fundraising probability.

Building a multi-layered automation system

Most sophisticated users eventually create a system with three layers:

1. Thesis-level automations that watch your entire category for new entrants, movers or fundraising candidates.

2. Watchlist-level automations that monitor companies you're already tracking for momentum shifts.

3. Signal-level automations that fire when specific catalysts occur—hiring surges, category changes, or digital traction spikes.

This layered structure ensures you stay ahead of the market without feeling overwhelmed by noise.

How automations strengthen your sourcing pipeline

Used consistently, automations build a steady pipeline over time. You receive surfaces earlier, reach founders faster, form theses sooner and build more conviction before a round formally opens. The consistency compounds: every week, you’re picking up signals your competitors aren’t watching.

Pesql becomes less of a dashboard and more of a predictive engine that continually feeds your dealflow.