| name | deal-review |
| description | Deep-review one deal; not pipeline prioritization. |
| metadata | {"short-description":"Diagnose one deal and recommend strategy"} |
Deal Review
Outcome
A structured diagnosis of deal position, evidence strength, gaps, risks, and the few actions most likely to improve clarity or progress.
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 fields and history, activities, stakeholders, customer needs, evaluation and decision process, commercial status, competition, service issues, and internal notes.
- 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
- Use the organization's chosen qualification method when available; otherwise organize findings without pretending a universal scorecard applies.
- Evaluate customer problem and impact, solution fit, stakeholders, decision process, timing, competition, commercial path, and next-step quality.
- Separate confirmed evidence, seller assertion, inference, contradiction, and unknown.
- Prioritize risks by impact and time sensitivity and identify disconfirming evidence as well as positive signals.
Required output
- Deal thesis
- Evidence and gap matrix
- Top risks and strengths
- Stakeholder and process summary
- Three recommended actions
- Suggested CRM updates
Actions and boundaries
Keep analysis read-only. Confirm any follow-on tasks or record updates separately.
