SALES
Win-back agent: pounce when a lost account drops your competitor
An agent monitors closed-lost accounts for signs they're leaving the competitor that beat you.
How it runs
The automated pipeline, trigger to output.
- TriggerRecurring win-back scan
- ActionRetrieve deals lost to the competitor in HubSpotHubSpot
- ActionSearch Exa for competitor churn signalsExa
- LogicAgent judges signal strength, drops noise
- ActionWrite brief and reopen deal in HubSpotHubSpot
- OutputDeliver win-back brief to rep in SlackSlack
What it does
When you lose to a competitor, the best second chance is the moment that competitor falls out of favor. This agent watches for churn signals at accounts you lost to a named rival and builds a complete win-back case when the wind shifts.
When to use it
Use it when a specific competitor wins deals against you and you want to be first in the door when their customers get frustrated. Best for teams comfortable with an agent that reasons over messy public signals rather than a rigid rule.
How it works
- 1On a recurring schedule, the agent retrieves accounts in HubSpot lost to a competitor, with the rival's name on the deal.
- 2It runs targeted Exa searches for churn signals: migration posts, layoffs in that vendor's team, negative reviews, RFP reissues.
- 3The agent weighs the evidence and decides whether the signal is strong enough to act on, discarding noise.
- 4For qualified accounts it writes a win-back brief: original loss reason, the competitor pain found, and a differentiated pitch.
- 5It updates the HubSpot deal with the brief and re-opens the stage.
- 6It delivers the brief to the rep in Slack with a suggested first-touch message.
Set it up
What you configure once, before turning it on.
- 1Connect HubSpotCRM, deals, marketing, support.
- 2Connect ExaNeural search across the web.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Sales workflows
API-Usage Surge PQL Router
When an account's API call volume surges past a rolling baseline in the product DB, it qualifies the account as a product-qualified expansion lead.
Seat-Limit Approaching Upsell Alert
Fires the moment an account's active-seat count crosses 90% of its contracted limit in the product database.
Enrich new MAP steps with Salesforce deal context on creation
When a new card is added to the mutual action plan Trello board, it looks up the linked Salesforce opportunity and writes deal owner, amount, and close date onto the card…
Power-Feature Adoption Expansion Digest
Each Monday, finds accounts that started heavily using a premium or add-on feature in BigQuery, ranks them by expansion potential.
Send buyers a weekly mutual action plan health recap
Each week it reads the MAP Trello board, computes completed, on-track, and overdue steps, and emails the buyer champion a clean recap of progress and what is due next.
Escalate to the deal team when the buyer side of a MAP stalls
Detects when buyer-owned mutual action plan steps have been idle past their due date and escalates with a Slack alert to the AE plus an email summary to the account executive's…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.