Ops Vendor Management

For ADD command — Create vendor profile:

• Search Gmail for vendor communications:

  Use the `search_emails` MCP tool with gmail_query: "from:<vendor-domain> OR to:<vendor-domain>"
  

• Extract: contact names, support channels, communication frequency
• Search vault for related vendor info:

  Use the `search_memory` MCP tool with query: "<vendor-name> contract SLA"
  

For REVIEW command — Evaluate vendor performance:

• Load vendor profile:

  cat ~/.second-brain/vault/ops/vendors/<vendor-slug>.md
  

• Search for incident/complaint history:

  grep -r "<vendor-name>\|incident\|issue\|downtime\|complaint" ~/.second-brain/vault/daily/ | tail -30
  

• Retrieve recent emails for sentiment analysis:

  Use the `search_emails` MCP tool with gmail_query: "from:<vendor-email>"
  

• Generate performance scorecard: uptime %, responsiveness, cost efficiency, feature delivery

For RENEW command — Prepare renewal negotiation:

• Load current contract:

  cat ~/.second-brain/vault/ops/vendors/<vendor-slug>.md
  

• Calculate days until renewal expiration
• Search calendar for renewal deadline:

  Use the `calendar_events` MCP tool with the relevant date
  

• Pull 6-12 month email history with vendor:

  Use the `search_emails` MCP tool with gmail_query: "from:<vendor-email>"
  

• Create negotiation brief with:
  • Current terms vs. market rates
  • Performance metrics and issues
  • Leverage points (competitor options)
  • Must-haves for renewal vs. nice-to-haves

For LIST command — Display all vendors:

ls -la ~/.second-brain/vault/ops/vendors/*.md | sort

Generate summary table: vendor name, service, contract end date, status (active/renewal-due/at-risk)

Generate vendor profile document with sections:

• Company Profile — Name, headquarters, industry, founded year
• Service/Product — What they provide, critical for operations (Y/N)
• Key Contacts — Primary contact, support team, escalation contact
• Contract Terms:
  • Contract start date, end date, renewal date
  • Auto-renewal terms (Y/N), notice period required
  • Annual cost, payment schedule (monthly, annually, etc.)
• SLA & Performance Metrics:
  • Uptime SLA %, support response time, availability window
  • Historical performance score (0-100)
  • Recent incidents and resolutions
• Performance Notes — Strengths, weaknesses, reliability, responsiveness
• Renewal Status — Days until renewal, decision needed by [date]
• Alternatives Considered — Competitor options with cost/feature comparison
• Last Review — Date reviewed, reviewer, decision

Save vendor profile to:

~/.second-brain/vault/ops/vendors/<vendor-slug>.md

Include YAML frontmatter:

---
vendor_name: "[Name]"
service: "[Service]"
contract_end: "[YYYY-MM-DD]"
status: "active|renewal-due|at-risk|inactive"
cost_annual: "$[amount]"
last_reviewed: "[YYYY-MM-DD]"
---

Add renewal date to calendar if renewing:

Log the calendar item with `log_note` (calendar creation not yet in MCP)
  --title "Vendor Renewal Deadline: [vendor-name]" \
  --date "[renewal-date]" \
  --reminder "14 days before"

Optionally create Asana task for renewal action:

Use the `list_tasks` MCP tool (task creation via Asana API — log the action item with `log_note` instead)
  --project "Operations" \
  --name "Renew contract: [vendor-name] (due YYYY-MM-DD)" \
  --due-date "[30-days-before-expiry]"

Log to daily log:

- **HH:MM** — [OPS] Vendor [action]: <vendor-name> — Status: <status> — Renewal: <renewal-date>