SALES

Stalled-Deal Pricing Re-Engagement Sweep

Each morning, scans open HubSpot deals that have gone quiet for 14+ days and flags any whose contacts revisited the pricing page in the last day.

CategorySales
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily morning schedule
  • ActionPull open deals idle 14+ days from HubSpotHubSpotHubSpot
  • ActionQuery pricing-page views in last 24h for those contactsPostgreSQLPostgres
  • LogicKeep deals with a fresh visit; rank by value and recency
  • OutputPost prioritized re-engagement list to sales channelSlack

What it does

Surfaces dormant pipeline that just showed fresh life. Every morning it pulls deals stuck without activity for two weeks, cross-checks each contact against recent pricing-page visits stored in your events table, and builds a ranked list of deals worth a same-day nudge — so reps spend their morning on opportunities that re-warmed themselves overnight.

When to use it

Use it when pipeline is large enough that reps cannot manually watch every stalled deal, and you log pricing-page views to a database. Ideal for a daily standup feed of "who went quiet but came back."

How it works

  1. 1A daily schedule kicks off the sweep each morning.
  2. 2HubSpot returns open deals with no activity for 14 or more days.
  3. 3The events database is queried for pricing-page views in the last 24 hours matching those contacts.
  4. 4Deals with a fresh visit are kept and ranked by deal value and recency.
  5. 5A prioritized re-engagement list is posted to the sales Slack channel with deal owner mentions.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HubSpotCRM, deals, marketing, support.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.