# CRM-lite Prospect Management Command: A Complete Guide to `/geo prospect` in geo-seo-claude > Discover the CRM-lite prospect management command in geo-seo-claude. Effortlessly track leads from contact to closure with the /geo prospect tool, avoiding external CRM costs. - Repository: [Zubair Trabzada/geo-seo-claude](https://github.com/zubair-trabzada/geo-seo-claude) - Tags: how-to-guide - Published: 2026-09-08 --- **The CRM-lite prospect management command is a lightweight, JSON-based sales pipeline tool accessible via the `/geo prospect` sub-command family in geo-seo-claude, enabling GEO-SEO agencies to track leads from initial contact through revenue closure without external CRM overhead.** The CRM-lite prospect management command provides GEO-SEO agencies with a native terminal-based customer relationship management layer. Implemented in the `zubair-trabzada/geo-seo-claude` repository, this feature eliminates the need for third-party CRM subscriptions by storing prospect data locally in structured JSON while integrating directly with automated GEO audit workflows. ## What Is the CRM-lite Prospect Management Command? The CRM-lite prospect management command exposes nine distinct operations through the `/geo prospect` interface, as defined in [`skills/geo-prospect/SKILL.md`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/skills/geo-prospect/SKILL.md). It functions as a **skill router** sub-component that intercepts prospect-related instructions and orchestrates data persistence, audit integration, and pipeline stage transitions. Unlike traditional CRM platforms, this implementation maintains all records in a single persistent JSON file at `~/.geo-prospects/prospects.json`, ensuring portability and command-line accessibility across sessions. ## Core `/geo prospect` Sub-Commands The command family supports the complete prospect lifecycle through specialized sub-commands that handle creation, tracking, auditing, and closure. ### Creating and Viewing Prospects Use the `new` sub-command to initialize a prospect record with automatic company name detection and ID assignment: ```bash /geo prospect new electron-srl.com ``` The system generates a unique prospect ID (e.g., `PRO-001`) and seeds the JSON database. To retrieve records, use `list` with optional status filtering or `show` for detailed views: ```bash # Display all prospects /geo prospect list # Filter by pipeline stage /geo prospect list qualified # View specific prospect details /geo prospect show PRO-001 ``` ### Auditing and Note-Taking The `audit` sub-command triggers an internal call to `/geo quick `, stores the resulting GEO score, and attaches the audit file to the prospect record. This creates a tight feedback loop between sales management and technical evaluation: ```bash /geo prospect audit electron-srl.com ``` For activity tracking, the `note` sub-command appends timestamped entries to the prospect's history: ```bash /geo prospect note PRO-001 "Discovery call completed; budget confirmed at €5,000/month" ``` ### Pipeline Status Management Prospects progress through five defined stages: `lead`, `qualified`, `proposal`, `won`, and `lost`. The `status` sub-command transitions records between stages while automatically logging contextual history entries: ```bash /geo prospect status PRO-001 qualified ``` This updates the `status` field in `~/.geo-prospects/prospects.json` and records the transition timestamp. ### Revenue Tracking and Closure The `won` and `lost` sub-commands handle terminal pipeline states with financial or analytical data capture. When closing a deal, specify the monthly recurring revenue (MRR): ```bash /geo prospect won PRO-001 4500 ``` For lost opportunities, document the reason for future churn analysis: ```bash /geo prospect lost PRO-002 "Budget constraints" ``` The `pipeline` sub-command renders a revenue-focused summary displaying MRR forecasts and stage distributions across the entire prospect database. ## Data Architecture and Persistence All prospect data resides in `~/.geo-prospects/prospects.json`, as implemented in the skill definitions within [`skills/geo-prospect/SKILL.md`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/skills/geo-prospect/SKILL.md). This single-source architecture ensures that both the command interface and the visual dashboard read from identical data structures. The JSON schema stores company metadata, current status, audit scores, note history, and financial projections, enabling survival across CLI sessions and compatibility with external data processing tools. ## Integration with the GEO Audit System According to the source code in [`skills/geo-prospect/SKILL.md`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/skills/geo-prospect/SKILL.md), the prospect management command integrates deeply with the platform's audit capabilities. When executing `/geo prospect audit `, the skill router invokes the same scoring engine used by the standalone quick audit agent, then persists those results within the prospect record. This integration eliminates manual data entry between technical analysis and sales tracking, as documented in [`docs/skills-and-agents.md`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/docs/skills-and-agents.md). ## Visual Dashboard and Reporting While the command-line interface handles data manipulation, the [`scripts/crm_dashboard.py`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/scripts/crm_dashboard.py) file implements a complementary visualization layer using the **rich** library. This script loads `~/.geo-prospects/prospects.json` and renders KPI cards, sortable tables, and status-by-pipeline views: ```bash python scripts/crm_dashboard.py ``` The dashboard supports direct execution without command prefixes, offering sales teams an immediate visual overview of pipeline health and revenue forecasts without leaving the terminal environment. ## Summary - The CRM-lite prospect management command provides a **complete sales pipeline** through the `/geo prospect` sub-command family in geo-seo-claude. - **Nine distinct operations** cover prospect creation, auditing, note-taking, status transitions, and financial closure. - Data persists in `~/.geo-prospects/prospects.json`, ensuring **cross-session durability** and compatibility with external tools. - **Direct integration** with the GEO audit system automatically attaches technical scores to sales records. - The **rich-based dashboard** in [`scripts/crm_dashboard.py`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/scripts/crm_dashboard.py) offers visual pipeline analytics without leaving the terminal environment. ## Frequently Asked Questions ### How does the CRM-lite prospect management command store data? The command stores all prospect information in a local JSON file located at `~/.geo-prospects/prospects.json`. This file-based approach ensures data persistence across terminal sessions and allows the information to be read by both the command interface and the optional Python dashboard script. ### What pipeline stages does the CRM-lite system support? The system implements five standard sales stages: `lead`, `qualified`, `proposal`, `won`, and `lost`. You can move prospects between the first three active states using the `status` sub-command, while the `won` and `lost` sub-commands handle terminal states with additional metadata like MRR or closure reasons. ### Can I run GEO audits directly from prospect records? Yes. The `audit` sub-command internally calls the `/geo quick ` agent, executes a full GEO analysis, and automatically attaches the resulting score and audit file to the specific prospect record. This creates a direct link between technical SEO evaluation and sales pipeline management. ### Where are the command definitions and documentation located? The primary command definitions and orchestration logic reside in [`skills/geo-prospect/SKILL.md`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/skills/geo-prospect/SKILL.md). Additional architectural context appears in [`docs/architecture.md`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/docs/architecture.md), while usage reference is available in [`docs/commands-reference.md`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/docs/commands-reference.md) and [`docs/skills-and-agents.md`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/docs/skills-and-agents.md).