pipeline-review

name	pipeline-review
description	Review one seller's pipeline; not one deal or a team.
metadata	{"short-description":"Review pipeline quality, movement, and risk"}

Pipeline Review

Outcome

A seller-level pipeline diagnosis that identifies which opportunities deserve action and why.

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: Open opportunities, stages, values, close dates, forecast categories, age, stage history, activity, stakeholders, next steps, and targets when available.
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. Use the organization's configured stages and forecast meanings; do not impose a universal sales process.
2. Assess movement, age, time-in-stage, date changes, engagement, next-step quality, stakeholder coverage, and value concentration.
3. Separate data hygiene from genuine deal risk and identify opportunities that may be understated as well as overstated.
4. If coverage or conversion metrics are shown, state numerator, denominator, time window, and currency treatment.

Required output

• Pipeline headline
• Movement and coverage summary
• Priority opportunity table
• Data-quality exceptions
• Recommended review questions and actions

Actions and boundaries

Propose field or task changes as a reviewable list; confirm before writing any of them.