SALES

Champion-Gone-Quiet Re-Engagement Plan Builder

Detects when a deal's primary champion stops replying, then builds and assigns a multi-touch re-engagement plan that routes new outreach to alternate contacts and logs tasks…

CategorySales
Enginepaperclip
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule starts review
  • ActionFetch deals + champion last-reply dateHubSpotHubSpot
  • LogicIsolate deals with silent champions
  • ActionSequence alternate stakeholders + anglesOpenAI
  • ActionLog follow-up tasks in HubSpotHubSpotHubSpot
  • OutputSave first-touch Gmail draftsGmailGmail

What it does

This agent-driven workflow tracks reply activity from each deal's designated primary contact. When that champion goes silent past the threshold while the deal is still open, it builds a sequenced re-engagement plan: who to contact next, in what order, with what angle, and over what cadence. It then creates the corresponding follow-up tasks in HubSpot and drafts the first message for each new stakeholder.

When to use it

Reach for this when deals quietly die because the one person you talked to changed priorities or left, and no structured backup plan kicks in.

How it works

  1. 1A daily schedule starts the review.
  2. 2HubSpot returns open deals with the primary contact's last inbound reply date.
  3. 3A filter isolates deals where the champion has gone quiet.
  4. 4An agent reasons over the account to sequence alternate stakeholders and outreach angles.
  5. 5HubSpot logs dated follow-up tasks for each touch.
  6. 6Gmail saves the opening drafts so the rep can launch the plan immediately.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HubSpotCRM, deals, marketing, support.
  2. 2
    Connect GmailRead, draft, send, label.
  3. 3
    Connect OpenAIModels, embeddings, files.
  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.