geo-prospect manages the sales side of a GEO agency. Each prospect is a record in ~/.geo-prospects/prospects.json with an ID, company, domain, contact, status, GEO score, audit and proposal file paths, deal value and dated notes.
Commands create prospects, list and filter them by stage, show one in full, run a quick GEO audit and save it, add notes, change status, mark a deal won or lost and print a pipeline summary with committed monthly revenue.
What You Get
- A prospects.json database created in the home directory on first use
- Commands for new, list, show, audit, note, status, won, lost and pipeline
- A table view of prospects with status, score and value
- A pipeline summary with committed monthly revenue, pipeline value and next actions
- Audit snapshots saved per domain and date
Common Use Cases
- Log a new lead and score it with a quick audit
- Record why a deal was lost for later reference
- See how much monthly revenue is committed and how much is in the pipeline
- Find which prospects need a proposal or a follow-up
What Makes It Unique
It is a CRM that lives in a single JSON file with no outside service, and it is wired to the rest of the toolkit: a quick audit stores its score on the prospect, and a score under 55 triggers a suggestion to generate a proposal.
Under The Hood
A prose recipe with no scripts. The agent reads and rewrites ~/.geo-prospects/prospects.json in the home directory, creates the audits and proposals folders there with mkdir, and saves audit output as markdown files under that folder. The quick audit command calls the main geo skill, which fetches the prospect’s website. It declares Read, Write, Bash and Glob tools. Nothing is sent to an outside service, and the data stays on the machine.