Sales Pipeline

2. Deal Tracking

Maintain deal records in memory. For each deal, track:

• Company name and primary contact
• Deal value and stage (Discovery, Demo, Proposal, Negotiation, Closed Won, Closed Lost)
• Date entered current stage
• Next scheduled action and date
• Notes from last interaction

Use memory_save to persist deal updates. Use file_write to maintain a pipeline summary file.

3. Follow-up Reminders

Proactively alert the user when:

• A deal has been in the same stage for more than 7 days without activity
• A scheduled follow-up date has passed
• A high-value deal (>$50K) has had no contact in 5+ days
• A contact who was previously responsive has gone quiet

4. Revenue Forecasting

When asked for a forecast:

• Sum deals by stage with weighted probability:
  • Discovery: 10%
  • Demo: 25%
  • Proposal: 50%
  • Negotiation: 75%
  • Verbal Commit: 90%
• Present: pipeline total, weighted forecast, best case, worst case
• Compare to target if the user has set one

5. Deal Research

When a new deal or company is mentioned:

• Use web_search to research the company: size, industry, recent news, key people
• Save findings to memory for future reference
• Flag any relevant information (recent funding, leadership changes, competitor wins)

Proactive Monitoring (HEARTBEAT.md)

This skill works as a periodic task. Add to HEARTBEAT.md:

- [ ] Check sales pipeline for stalled deals and overdue follow-ups — alert if any found

When triggered by the scheduler:

1. Read the pipeline from memory/files
2. Identify any deals that need attention (stalled, overdue, at-risk)
3. Generate a brief alert summary
4. Save the alert to ~/.osa/alerts/pipeline-YYYY-MM-DD.md

Data Storage

Pipeline data is stored in two places:

• Memory — Quick-access deal snapshots for real-time queries
• File — ~/.osa/data/pipeline.json for structured data, updated on every deal change

Important Rules

• Never fabricate deal information — only work with what the user provides or what you find via research
• When the user updates a deal, confirm the change and save it immediately
• Always show the date of last activity when presenting pipeline data
• Revenue forecasts must show their assumptions (stage weights) so the user can adjust
• If the user mentions a new deal, prompt them to provide: company, contact, estimated value, and current stage

Examples

User: "Show me the pipeline"

Expected behavior: Read pipeline data from memory/file, present the formatted table with all active deals, highlight any at-risk items, show total pipeline value and weighted forecast at the bottom.

User: "Update the Acme deal — they accepted the proposal, moving to negotiation. Value is now $135K."

Expected behavior: Update the deal record (stage, value, date), save to memory and file, confirm the update, and note the next recommended action for the negotiation stage.

User: "Which deals need attention this week?"

Expected behavior: Scan all deals, identify those with overdue follow-ups, stalled stages, or upcoming deadlines. Present a prioritized action list with specific recommended next steps for each.

User: "What's our revenue forecast for Q1?"

Expected behavior: Calculate weighted pipeline value by stage, present pipeline total vs weighted forecast vs best case vs worst case, compare to Q1 target if one has been set, and flag deals that most impact the forecast.

User: "Research Delta Co — I have a call with them tomorrow"

Expected behavior: Use web_search to find company info, recent news, key personnel. Save findings to memory. Present a brief one-page company profile with anything relevant to the upcoming call.