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
- Identify the specific sales task triggering this skill
- Verify the requestor has appropriate authority
- Gather all required input documents, drawings, specifications, and supporting data
- Confirm scope clearly matches this skill's purpose; escalate if out of scope
Step 2: Analysis and Assessment
- Review relevant domain knowledge sections for this discipline
- Identify applicable standards, codes, specifications, and regulatory requirements
- Assess dependencies on other disciplines, agents, or data sources
- Document any gaps, ambiguities, or conflicting requirements
Step 3: Execution
- Apply discipline-specific methods and tools for maintain sales pipeline, forecast revenue, track win/loss rates, report on metrics
- Generate required outputs using approved templates, formats, and systems
- Maintain full audit trail of all actions, calculations, decisions, and outputs
- Cross-reference with related contracts, policies, standards, and specifications
Step 4: Quality Review
- Validate all outputs against domain knowledge requirements and applicable standards
- Verify compliance with regulatory requirements and project specifications
- Ensure required documentation is complete, accurate, and properly formatted
- Identify any exceptions, deviations, or non-standard items for specialist review
Step 5: Approval and Routing
- Route outputs through appropriate approval workflow based on value/complexity
- Verify approval authority matches delegated authority limits
- Incorporate any required revisions from reviewers
- Obtain final approval and sign-off from authorized personnel
Step 6: Close-Out and Filing
- File all outputs in appropriate registers and repositories (EDMS, project registers)
- Update relevant tracking systems and databases
- Archive working documents per project retention policy
- Update sales records, logs, and registers
Success Criteria
Common Pitfalls
- Incomplete Inputs — Attempting execution without all required documents or data. Always verify completeness before starting.
- Outdated References — Using superseded specifications, codes, or drawing revisions. Always check for current versions in EDMS.
- Missing Authority — Acting beyond delegated authority limits. Always verify approver authority before routing.
- Inadequate Documentation — Failing to maintain audit trail or file outputs properly. Every action requires documentation.
- Non-Compliant Outputs — Generating outputs that don't meet applicable standards. Always validate against requirements before approval.
- 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
1---2name: sales-pipeline-forecasting3description: Maintain sales pipeline, forecast revenue, track win/loss rates, report on metrics4---56# Sales Pipeline and Revenue Forecasting78## Overview9Maintain sales pipeline, forecast revenue, track win/loss rates, report on metrics1011**Announce at start:** "I'm using the sales-pipeline-forecasting skill for Sales operations."1213## When to Use This Skill14**Trigger Conditions:** Maintain sales pipeline, forecast revenue, track win/loss rates, report on metrics task required, discipline-specific task or request received15**Prerequisites:**16- Domain knowledge available (Sales domain knowledge)17- Appropriate authority and permissions granted18- Relevant inputs and reference documents accessible19- Required coordination with related disciplines confirmed2021## Step-by-Step Procedure2223### Step 1: Initiation and Scoping241. Identify the specific sales task triggering this skill252. Verify the requestor has appropriate authority263. Gather all required input documents, drawings, specifications, and supporting data274. Confirm scope clearly matches this skill's purpose; escalate if out of scope2829### Step 2: Analysis and Assessment301. Review relevant domain knowledge sections for this discipline312. Identify applicable standards, codes, specifications, and regulatory requirements323. Assess dependencies on other disciplines, agents, or data sources334. Document any gaps, ambiguities, or conflicting requirements3435### Step 3: Execution361. Apply discipline-specific methods and tools for maintain sales pipeline, forecast revenue, track win/loss rates, report on metrics372. Generate required outputs using approved templates, formats, and systems383. Maintain full audit trail of all actions, calculations, decisions, and outputs394. Cross-reference with related contracts, policies, standards, and specifications4041### Step 4: Quality Review421. Validate all outputs against domain knowledge requirements and applicable standards432. Verify compliance with regulatory requirements and project specifications443. Ensure required documentation is complete, accurate, and properly formatted454. Identify any exceptions, deviations, or non-standard items for specialist review4647### Step 5: Approval and Routing481. Route outputs through appropriate approval workflow based on value/complexity492. Verify approval authority matches delegated authority limits503. Incorporate any required revisions from reviewers514. Obtain final approval and sign-off from authorized personnel5253### Step 6: Close-Out and Filing541. File all outputs in appropriate registers and repositories (EDMS, project registers)552. Update relevant tracking systems and databases563. Archive working documents per project retention policy574. Update sales records, logs, and registers5859## Success Criteria60- [ ] Task scope clearly defined and authorized61- [ ] All required inputs gathered and validated62- [ ] Sales Pipeline and Revenue Forecasting output generated per requirements63- [ ] Compliance with applicable standards and codes verified64- [ ] Quality review completed and documented65- [ ] Approval obtained through proper workflow66- [ ] Outputs filed in appropriate registers67- [ ] Audit trail complete and accurate68- [ ] Sales Pipeline and Revenue Forecasting completed successfully6970## Common Pitfalls711. **Incomplete Inputs** — Attempting execution without all required documents or data. Always verify completeness before starting.722. **Outdated References** — Using superseded specifications, codes, or drawing revisions. Always check for current versions in EDMS.733. **Missing Authority** — Acting beyond delegated authority limits. Always verify approver authority before routing.744. **Inadequate Documentation** — Failing to maintain audit trail or file outputs properly. Every action requires documentation.755. **Non-Compliant Outputs** — Generating outputs that don't meet applicable standards. Always validate against requirements before approval.766. **Inter-Discipline Gaps** — Not coordinating with affected disciplines. Always identify and communicate interface impacts.7778## Cross-References7980### Related Skills81- Additional sales skills for related functions82- Skills from interfacing disciplines for cross-functional tasks8384### Related Agents85- **Primary:** Sales Manager — Main execution86- **Supporting:** Sales Administrator — Document and data management87- **Oversight:** Sales Manager — Review, approval, and escalation8889### Related Domain Knowledge90- Sales Domain Knowledge for role responsibilities and frameworks91- Sales Glossary for terminology, definitions, and abbreviations