# GEO prospect manager Human Guide ## What This Is For CRM-lite for managing GEO agency prospects and clients. It gives the agent a clearer input/output frame for search and SEO workflows: what context to ask for, what decisions to make, and what usable artifact to return. Use this as a human-readable version of the GEO prospect manager agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions. ## When To Use This - Use this when you need a repeatable process for GEO prospect manager. - Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt. - Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact. ## When Not To Use This - Do not use this when you only need a quick factual answer. - Do not use this when the work depends on private data you cannot share with the assistant. - Do not use this as a replacement for legal, compliance, financial, or medical review. ## What You Need Before Starting - The goal or business outcome you want. - The audience, customer segment, or market context. - Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance. - Constraints such as tone, length, channel, deadline, region, or approval requirements. - A clear definition of what a good final answer should look like. ## Step-By-Step Workflow 1. State the job clearly: "Use the GEO prospect manager guide to help me with..." 2. Add context: audience, goal, offer, channel, source material, and constraints. 3. Ask the assistant to identify missing inputs before producing the final output. 4. Have the assistant follow the skill-specific guidance below. 5. Review the result against the final checklist and ask for revisions where needed. ## Skill-Specific Guidance - Check if `~/.geo-prospects/prospects.json` exists, create if not (empty array) - Auto-detect company name from domain (e.g., `electron-srl.com` → `Electron Srl`) - Assign next sequential ID: `PRO-001`, `PRO-002`, etc. - Monthly contract value estimate (optional) - Suggest next step: "Run `/geo prospect audit electron-srl.com` to score this prospect" - Run `/geo quick ` to get GEO snapshot score - Save score to prospect record: `geo_score`, `audit_date` - Save audit output to `~/.geo-prospects/audits/-.md` - Update `audit_file` path in prospect record - Add auto-note: "Quick audit run. GEO Score: XX/100." - If score < 55: suggest "Score indicates strong sales opportunity. Run `/geo proposal ` to generate proposal." - Find prospect by ID or domain ## Decision Points And Nuance The original skill emphasizes: Purpose, Commands, Data Structure, Orchestration Instructions, `/geo prospect new `, `/geo prospect list`, `/geo prospect audit `, `/geo prospect note ""`, `/geo prospect status `, `/geo prospect pipeline`. Use these questions to steer the work: - What is the intended audience or buyer? - What source material must be preserved? - What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion? - What examples represent the desired quality bar? - What should the assistant avoid? ## Common Mistakes - Starting without a clear audience or goal. - Asking for a final artifact before sharing examples or constraints. - Accepting a generic first draft without checking it against the intended use. ## Copy-And-Paste Prompt ```text Use the GEO prospect manager human guide. My goal: [Describe the business outcome] Audience: [Describe who this is for] Context and source material: [Paste notes, examples, links, or existing copy] Constraints: [Tone, length, channel, timeline, must-include items, must-avoid items] Before producing the final output, ask me for any missing information that would materially improve the result. ``` ## Final Checklist - [ ] The output matches the original goal. - [ ] The audience and context are reflected in the answer. - [ ] Important constraints and source material were preserved. - [ ] The assistant made the relevant decisions explicit. - [ ] The final artifact is ready to use, review, or hand to the next person. ## Source This guide was generated from the zubair-trabzada/geo-seo-claude skill entry for `geo-prospect`. ## Source Skill Notes These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic. # 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 | Command | What It Does | |---------|-------------| | `/geo prospect new ` | Create new prospect (interactive prompts) | | `/geo prospect list` | Show all prospects with pipeline status | | `/geo prospect list ` | Filter: lead, qualified, proposal, won, lost | | `/geo prospect show ` | Full prospect detail with history | | `/geo prospect audit ` | Run quick GEO audit and save to prospect record | | `/geo prospect note ""` | Add interaction note with timestamp | | `/geo prospect status ` | Move through pipeline | | `/geo prospect won ` | Mark as won, set contract value | | `/geo prospect lost ""` | Mark as lost with reason | | `/geo prospect pipeline` | Visual pipeline summary with revenue forecast | --- ## Data Structure Each prospect is stored as a JSON record: ```json { "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 ` 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: ```