GEO Prospect Manager

Purpose

Manage GEO agency prospects and clients through the full sales lifecycle. All data is stored in ~/.geo-prospects/prospects.json (persistent across sessions).

Commands

Data Structure

Each prospect is stored as a JSON record:

{
  "id": "PRO-001",
  "company": "Electron Srl",
  "domain": "electron-srl.com",
  "contact_email": "info@electron-srl.com",
  "contact_name": "",
  "industry": "Educational Equipment Manufacturing",
  "country": "Italy",
  "status": "qualified",
  "geo_score": 32,
  "audit_date": "2026-03-12",
  "audit_file": "~/.geo-prospects/audits/electron-srl.com-2026-03-12.md",
  "proposal_file": "~/.geo-prospects/proposals/electron-srl.com-proposal.md",
  "monthly_value": 0,
  "contract_start": null,
  "contract_months": 0,
  "notes": [
    {
      "date": "2026-03-12",
      "text": "Initial GEO quick scan. Score 32/100 - Critical tier. Strong candidate for GEO services."
    }
  ],
  "created_at": "2026-03-12",
  "updated_at": "2026-03-12"
}

Orchestration Instructions

/geo prospect new <domain>

1. Check if ~/.geo-prospects/prospects.json exists, create if not (empty array)
2. Auto-detect company name from domain (e.g., electron-srl.com → Electron Srl)
3. Assign next sequential ID: PRO-001, PRO-002, etc.
4. Ask user for:
   • Contact name (optional)
   • Contact email
   • Monthly contract value estimate (optional)
5. Set status to lead
6. Save to JSON file
7. Suggest next step: "Run /geo prospect audit electron-srl.com to score this prospect"

/geo prospect list

Read ~/.geo-prospects/prospects.json and render a summary table:

GEO Prospect Pipeline — March 2026
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

ID       Domain                  Company           Status      Score  Value
───────  ──────────────────────  ────────────────  ──────────  ─────  ──────
PRO-001  electron-srl.com        Electron Srl      Qualified   32/100  €4.5K
PRO-002  acme.com                ACME Corp         Lead        —       —
PRO-003  bigshop.it              BigShop           Won         41/100  €6.0K

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Pipeline: 1 lead | 1 qualified | 0 proposals | 1 won | 0 lost
Committed MRR: €6,000 | Pipeline Value: €4,500

/geo prospect audit <id-or-domain>

1. Run /geo quick <domain> to get GEO snapshot score
2. Save score to prospect record: geo_score, audit_date
3. Save audit output to ~/.geo-prospects/audits/<domain>-<date>.md
4. Update audit_file path in prospect record
5. Add auto-note: "Quick audit run. GEO Score: XX/100."
6. If score < 55: suggest "Score indicates strong sales opportunity. Run /geo proposal <domain> to generate proposal."

/geo prospect note <id-or-domain> "<text>"

1. Find prospect by ID or domain
2. Append note with current ISO date
3. Save back to JSON
4. Confirm: "Note added to Electron Srl (PRO-001)"

/geo prospect status <id-or-domain> <status>

Valid statuses: lead, qualified, proposal, won, lost

1. Update status field
2. Add auto-note: "Status changed to "
3. Save and confirm

/geo prospect pipeline

Visual revenue-focused pipeline summary:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
GEO AGENCY PIPELINE SUMMARY — March 2026
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

STAGE          COUNT   POTENTIAL VALUE   NOTES
─────────────  ─────   ───────────────   ─────────────────────
Lead             2      €8,000/mo        New discoveries
Qualified        1      €4,500/mo        Ready for proposal
Proposal Sent    1      €6,000/mo        Awaiting signature
Won              3      €18,500/mo       Active clients (MRR)
Lost             1      —                Budget freeze

COMMITTED MRR:        €18,500
PIPELINE (qualified+): €10,500
TOTAL POTENTIAL:      €29,000/mo → €348,000/yr

Next actions:
→ PRO-003 (acme.com): Send proposal — score 38/100 (strong case)
→ PRO-007 (shop.it): Follow up — proposal sent 8 days ago
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Storage Location

All data stored in ~/.geo-prospects/:

~/.geo-prospects/
├── prospects.json          # Main CRM database
├── audits/                 # Quick audit snapshots
│   └── electron-srl.com-2026-03-12.md
└── proposals/              # Generated proposals
    └── electron-srl.com-proposal.md

Create directory if it does not exist: mkdir -p ~/.geo-prospects/audits ~/.geo-prospects/proposals

Pipeline Stage Definitions

Output

• All commands print confirmation + current prospect status to terminal
• No external files unless explicitly saving audits/proposals
• JSON database is the single source of truth

Tooling

seogeo crm add example.com --name "Example Corp" --email hi@example.com \
  --stage lead --value 4800 --json
seogeo crm list --stage qualified --json
seogeo crm show example.com --json
seogeo crm update example.com --stage proposal_sent --value 6000 --json
seogeo crm note example.com "Sent the audit; call booked for Tuesday"
seogeo crm audit example.com --score 62 --report ./example-audit/GEO-AUDIT-REPORT.md
seogeo crm pipeline --json

Stages are fixed: lead, qualified, proposal_sent, won, lost. Any other value is rejected rather than silently created, so the pipeline totals stay meaningful.

crm audit is what makes geo-compare possible later — record a score every time you run an audit, even when nothing changed. Two stored audits are the minimum for a delta report.

State lives in a single JSON file (seogeo crm list --json prints its path) so it is easy to inspect, diff, and back up. Set SEOGEO_CRM_FILE to relocate it.