CRM

Pipeline Decay Scorer to Warehouse

Reads the full open pipeline from Postgres, computes a per-deal decay score from inactivity, stage age, and engagement drop, writes scores back.

CategoryCRM
Enginesim
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule
  • ActionRead open pipeline from PostgresPostgreSQLPostgres
  • LogicCompute per-deal decay score
  • ActionWrite scores back to PostgresPostgreSQLPostgres
  • LogicCheck aggregate decay threshold
  • OutputAlert managers in Slack on breachSlack

What it does

Quantifies pipeline rot. It scores every open deal on how badly it has decayed using inactivity, time-in-stage, and falling engagement, persists those scores back to your warehouse for reporting, and pings managers when the overall decay level breaches a set limit.

When to use it

Use it when you run analytics on a Postgres data warehouse and want a defensible, numeric measure of pipeline health rather than gut feel. Ideal for RevOps teams powering dashboards and weekly business reviews.

How it works

  1. 1A nightly schedule trigger starts the scoring job.
  2. 2Read all open deal records and their activity timeline from the Postgres pipeline tables.
  3. 3Compute a decay score per deal blending days idle, stage age, and engagement trend.
  4. 4Write the scores and a decay tier back to a Postgres scoring table for dashboards.
  5. 5A threshold check evaluates aggregate pipeline decay; if it crosses the limit, post an alert with the worst offenders to Slack.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.