deal-slip-scenarios

name	deal-slip-scenarios
description	Model close-date slip scenarios; never invent win odds.
metadata	{"short-description":"Model close-date slip scenarios and impact"}

Deal Slip Scenarios

Outcome

Transparent timing scenarios showing which deals may slip, why, and what can still change the outcome.

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

1. Resolve the user, target records, requested scope, reporting window, timezone, and business objective. Ask only for missing details that materially change the result.
2. Retrieve the minimum authorized evidence needed from the following inputs: Close dates, stage history, remaining milestones, customer commitments, procurement and legal steps, recent engagement, dependencies, and historical cycle data when comparable.
3. Normalize relevant entities and fields while retaining native record identifiers and source timestamps.
4. Apply the analysis rules below. When evidence conflicts, show the conflict rather than averaging it away.
5. Deliver the required output in a compact form suited to the scope. Put urgent or decision-relevant items first.

Analysis rules

1. Anchor timing to explicit milestones and customer commitments rather than seller optimism.
2. Create baseline, upside, and downside timing cases only when evidence supports distinct cases.
3. State assumptions, blockers, required decision dates, and forecast impact for each scenario.
4. Do not treat a past cycle-time average as destiny; note sample size and comparability.

Required output

• Scenario summary
• Deal-by-deal timing table
• Assumptions and trigger dates
• Period impact
• Actions that could reduce slip risk

Actions and boundaries

Do not change close dates automatically. Offer exact proposed dates and evidence for confirmation.