Bigmind

Deal signals

Bigmind’s agents scan your deals for what changed, reading warnings, account signals and dated activity, and return each risk or opening with its source, the deal it affects, its urgency and a next action.

By BigmindThe AI workspace for revenue teamsbigmind.ai
Built on Bigmind
Claude

Which of my deals went quiet this week?

Claude Opus 5.5

Which of my deals went quiet this week?

Your team

How it works

01

You set the scope

You name the deals or accounts and the time window the agent should cover.

02

It reads the signals

An agent reads warnings and account signals and looks into the evidence behind each.

03

It checks what’s new

The agent confirms changes with dated activity so an old warning isn’t sold as news.

04

You get the actions

The agent lists each finding with a next step and prepares the outreach you ask for.

The skill

Deal Signals

Read the workflow contract before execution. For this workflow, also read pipeline and frameworks, review actions, knowledge and coaching.

Resolve the requested pipeline/account scope and time window. Read warnings and relevant existing signals; inspect describeSignalById for evidence and meaning where needed. Use dated activity to confirm changes and deal relevance.

Return each finding's source/time, affected deal, urgency and specific next action. Avoid presenting a repeated old warning as a new event. Prepare requested outreach, tasks or opportunity reviews.

If the user asks for ongoing detection, use the configuration workflow and verify resulting tracker/automation state. A one-time signal review does not enable monitoring.

By Bigmind· Updated Oct 12, 2026· MIT· Source on GitHub

Run it

In your agentOne line installs it in Claude Code, Codex, Cursor and other agents, and it reaches your workspace through Bigmind’s MCP server.
npx skills add bigmindai/ext-plugins --skill deal-signals

Install with:

Checks

Works with Bigmind
Built on Bigmind: it reads and writes your workspace through Bigmind’s tools.
Needs
A Bigmind workspace.
Tested by Bigmind
Bigmind builds and maintains it.

What it reads

Your CRMAccounts, contacts, deals and their stages, in HubSpot or Salesforce.
Your callsWhat was said on every recorded call, with the transcript and summary.
Your emailThreads with customers, and the emails it drafts for you to send.
Signals and warningsWhat changed at an account and the risks Bigmind flagged on a deal.

When to use it

  • It’s Monday and you want to know which deals went quiet last week.
  • You heard Ripple has a new CFO and want to know which deals that touches.
  • Before a pipeline call, you want the risks that appeared since the last one.

When not to

  • You want ongoing alerts, not a one-time scan. Use Revenue intelligence setup.
  • You need a full read on one deal. Use Deal review.
  • You want what needs you today across email and meetings too. Use Daily briefing.

Questions

What are deal signals in sales?

Deal signals are events that change a deal’s odds, like a contact going quiet, a new executive at the account or a risk flagged on the deal. Reading them early lets a rep act before the deal slips.

Does the deal signals skill keep watching my deals?

No. The deal signals skill runs a one-time review of the deals and time window you choose. Ongoing detection needs a tracker or automation, which an agent can set up through the configuration workflow when you ask.

Does the deal signals skill need Bigmind?

Yes. The deal signals skill is free and installs in Claude Code, Codex, Cursor and other agents, but it reads warnings, signals and deal activity through Bigmind’s MCP server, so it needs a Bigmind workspace.

Skills to use with it