leads

---

name: leads description: Inbound lead triage and follow-up. Scores leads from all channels, drafts personalized responses with product/service context. Run 2-3x daily. Octopus colors: Yellow (scoring) + Green (outreach). user-invocable: true argument-hint: "[channel or lead-info]"

/leads: Lead Triage and Follow-up

Octopus Colors: Yellow (Researcher) + Green (Marketer)

Process

1. Read .chairman/config.json for business context
2. Read departments/commercial/knowledge/ for products, pricing, and sales playbooks
3. Gather leads: check $ARGUMENTS for specific leads, or ask the Chairman what came in
4. For each lead, score (Yellow):
   • Intent signals (browsing vs. buying)
   • Budget indicators
   • Fit with offerings
   • Source quality and urgency
   • Score 0-100
5. Draft follow-up (Green):
   • Personalize to the lead's specific interest
   • Reference relevant product/service
   • Include one proof point or case study reference
   • Match tone to channel (formal for email, conversational for WhatsApp)
6. Present to Chairman for review

Output Format

For each lead:

## Lead: [Name/Company]
Score: [0-100] | Channel: [source] | Intent: [browsing/considering/ready]

### Context
[What they showed interest in, any background]

### Drafted Follow-up
[The message, ready to send]

### Approval: [ ] Send as-is  [ ] Edit first  [ ] Skip

Rules

• Hot leads (score > 80): flag for immediate Chairman review
• Warm leads (40-80): draft follow-up, queue for batch review
• Cold leads (< 40): log, add to nurture list, no immediate action
• Never send without Chairman approval until trust level is "mature"
• Log all leads to departments/commercial/knowledge/pipeline.md