| name | deal-signals |
| description | Find material deal changes; not a full deal review. |
| metadata | {"short-description":"Surface material changes across active deals"} |
Deal Signals
Outcome
A prioritized set of new, evidence-backed signals across selected opportunities.
CRM-neutral operating contract
- Discover available CRM, communication, calendar, knowledge, and file capabilities before choosing a retrieval plan. If no live CRM is available, use user-supplied exports when that still satisfies the request; never imply a live write is possible.
- Map records by meaning, not vendor labels: organization, person, lead, opportunity, activity, product, service record, user or team, and knowledge item. Inspect schemas and custom fields, preserve native IDs, stages, currencies, timezones, and fiscal periods.
- Keep observed facts, derived conclusions, and missing information distinct. Anchor consequential claims to record IDs, fields, timestamps, or named sources, and state access or freshness limits.
- Start read-only. Before creating, updating, assigning, sending, or scheduling, show the exact proposed action and obtain confirmation unless the current request already authorized that exact mutation.
- Obey connected-system permissions, resolve ambiguous records or people instead of guessing, check for duplicates before creation, and report partial failures without repeated retries.
Workflow
- Resolve the user, target records, requested scope, reporting window, timezone, and business objective. Ask only for missing details that materially change the result.
- Retrieve the minimum authorized evidence needed from the following inputs: Opportunity field history, current stage and forecast data, recent activities, stakeholder engagement, tasks, and relevant service records.
- Normalize relevant entities and fields while retaining native record identifiers and source timestamps.
- Apply the analysis rules below. When evidence conflicts, show the conflict rather than averaging it away.
- Deliver the required output in a compact form suited to the scope. Put urgent or decision-relevant items first.
Analysis rules
- Compare the requested period with the preceding state; do not present unchanged facts as new signals.
- Test for close-date, amount, stage, forecast, ownership, next-step, engagement, stakeholder, competitor, legal, security, and service changes.
- Rank signals by likely revenue impact, urgency, and confidence; explain each rank without inventing a probability.
- Treat missing activity capture or stale records as data-quality uncertainty, not proof that the customer disengaged.
Required output
- Executive signal summary
- Signal cards with deal, change, evidence, impact, urgency, and confidence
- Recommended next actions
- Coverage and freshness caveats
Actions and boundaries
Remain read-only unless the user separately asks to update a record or create a task.
