Deal signals | Business Helper AI

Inputs and purpose

Use this workflow to prepare: Snapshot change/aging digest; no live monitoring.

Start with: Current and previous pipeline exports plus known activity.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

Procedure

Align the current and previous snapshots by stable opportunity identifier, scope and observation date.
Compare stage, value, timing, owner and activity changes, keeping missing records and genuinely closed records distinct.
Flag unusual aging or movement for review and connect each flag to the supplied evidence.
Return a change digest and follow-up questions. This is a comparison of supplied snapshots, not continuous monitoring.

Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Improve qualification, prioritization and deal follow-up.

Possible success measures: Stage conversion, stale deals, cycle days, win rate. Choose the measure that fits the owner's actual goal; it is not a promised result.

Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the input guide, calculation reference or output template. For tool setup, use the shared instructions.

Plain-text instructions

---
name: deal-signals
description: "Prepare snapshot change/aging digest; no live monitoring. Use for this workflow with supplied business information."
---

# Deal signals

## Inputs and purpose

Use this workflow to prepare: Snapshot change/aging digest; no live monitoring.

Start with: Current and previous pipeline exports plus known activity.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

## Procedure

1. Align the current and previous snapshots by stable opportunity identifier, scope and observation date.

2. Compare stage, value, timing, owner and activity changes, keeping missing records and genuinely closed records distinct.

3. Flag unusual aging or movement for review and connect each flag to the supplied evidence.

4. Return a change digest and follow-up questions. This is a comparison of supplied snapshots, not continuous monitoring.

## Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Improve qualification, prioritization and deal follow-up.

Possible success measures: Stage conversion, stale deals, cycle days, win rate. Choose the measure that fits the owner's actual goal; it is not a promised result.

## Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the [input guide](../../../references/INPUT_DATA_GUIDE.md), [calculation reference](../../../references/CALCULATIONS.md) or [output template](../../../references/WORKFLOW_OUTPUT_TEMPLATE.md). For tool setup, use the [shared instructions](../../../AGENTS.md).