team-pipeline

name	team-pipeline
description	Analyze a team's pipeline; not employee performance.
metadata	{"short-description":"Analyze team pipeline without false rankings"}

Team Pipeline

Outcome

A comparable team-level view of pipeline shape, movement, concentration, risk, and coaching needs.

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: Team membership, ownership, opportunity pipeline, targets, currencies, stages, changes, activity coverage, and reporting period.
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. Normalize only comparable teams, periods, stages, and currencies; expose differences that prevent fair comparison.
2. Analyze distribution, concentration, movement, aging, forecast mix, new creation, slippage, and missing next steps.
3. Use record evidence for coaching prompts; do not infer effort, ability, or intent from incomplete CRM activity.
4. Avoid simplistic leaderboards when territories, tenure, books of business, or data capture differ materially.

Required output

• Leadership summary
• Team rollup with metric definitions
• Material changes and concentration risks
• Coaching questions by owner
• Coverage and comparability caveats

Actions and boundaries

Remain read-only unless the leader asks for specific, reviewable CRM changes.