# Sales Pipeline Forecasting

> Maintain sales pipeline, forecast revenue, track win/loss rates, report on metrics

- Skill: `construct-ai-primary/sales-pipeline-forecasting` (Agent Skill)
- Install (CLI): `npx skillmds@latest add construct-ai-primary/sales-pipeline-forecasting`
- Raw SKILL.md: https://api.skillmd.com/api/skills/construct-ai-primary/sales-pipeline-forecasting/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: Construct-AI-primary (https://skillmd.com/u/construct-ai-primary)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/construct-ai-primary/sales-pipeline-forecasting

---


# Sales Pipeline and Revenue Forecasting

## Overview
Maintain sales pipeline, forecast revenue, track win/loss rates, report on metrics

**Announce at start:** "I'm using the sales-pipeline-forecasting skill for Sales operations."

## When to Use This Skill
**Trigger Conditions:** Maintain sales pipeline, forecast revenue, track win/loss rates, report on metrics task required, discipline-specific task or request received
**Prerequisites:**
- Domain knowledge available (Sales domain knowledge)
- Appropriate authority and permissions granted
- Relevant inputs and reference documents accessible
- Required coordination with related disciplines confirmed

## Step-by-Step Procedure

### Step 1: Initiation and Scoping
1. Identify the specific sales task triggering this skill
2. Verify the requestor has appropriate authority
3. Gather all required input documents, drawings, specifications, and supporting data
4. Confirm scope clearly matches this skill's purpose; escalate if out of scope

### Step 2: Analysis and Assessment
1. Review relevant domain knowledge sections for this discipline
2. Identify applicable standards, codes, specifications, and regulatory requirements
3. Assess dependencies on other disciplines, agents, or data sources
4. Document any gaps, ambiguities, or conflicting requirements

### Step 3: Execution
1. Apply discipline-specific methods and tools for maintain sales pipeline, forecast revenue, track win/loss rates, report on metrics
2. Generate required outputs using approved templates, formats, and systems
3. Maintain full audit trail of all actions, calculations, decisions, and outputs
4. Cross-reference with related contracts, policies, standards, and specifications

### Step 4: Quality Review
1. Validate all outputs against domain knowledge requirements and applicable standards
2. Verify compliance with regulatory requirements and project specifications
3. Ensure required documentation is complete, accurate, and properly formatted
4. Identify any exceptions, deviations, or non-standard items for specialist review

### Step 5: Approval and Routing
1. Route outputs through appropriate approval workflow based on value/complexity
2. Verify approval authority matches delegated authority limits
3. Incorporate any required revisions from reviewers
4. Obtain final approval and sign-off from authorized personnel

### Step 6: Close-Out and Filing
1. File all outputs in appropriate registers and repositories (EDMS, project registers)
2. Update relevant tracking systems and databases
3. Archive working documents per project retention policy
4. Update sales records, logs, and registers

## Success Criteria
- [ ] Task scope clearly defined and authorized
- [ ] All required inputs gathered and validated
- [ ] Sales Pipeline and Revenue Forecasting output generated per requirements
- [ ] Compliance with applicable standards and codes verified
- [ ] Quality review completed and documented
- [ ] Approval obtained through proper workflow
- [ ] Outputs filed in appropriate registers
- [ ] Audit trail complete and accurate
- [ ] Sales Pipeline and Revenue Forecasting completed successfully

## Common Pitfalls
1. **Incomplete Inputs** — Attempting execution without all required documents or data. Always verify completeness before starting.
2. **Outdated References** — Using superseded specifications, codes, or drawing revisions. Always check for current versions in EDMS.
3. **Missing Authority** — Acting beyond delegated authority limits. Always verify approver authority before routing.
4. **Inadequate Documentation** — Failing to maintain audit trail or file outputs properly. Every action requires documentation.
5. **Non-Compliant Outputs** — Generating outputs that don't meet applicable standards. Always validate against requirements before approval.
6. **Inter-Discipline Gaps** — Not coordinating with affected disciplines. Always identify and communicate interface impacts.

## Cross-References

### Related Skills
- Additional sales skills for related functions
- Skills from interfacing disciplines for cross-functional tasks

### Related Agents
- **Primary:** Sales Manager — Main execution
- **Supporting:** Sales Administrator — Document and data management
- **Oversight:** Sales Manager — Review, approval, and escalation

### Related Domain Knowledge
- Sales Domain Knowledge for role responsibilities and frameworks
- Sales Glossary for terminology, definitions, and abbreviations