prospect-research

Prospect Research

A seller needs a reason to write, a first question that tests it, and a verdict on whether to bother. This skill keeps only the signals that map to a pain your brain says you solve and turns them into one hypothesis. It never drafts or sends outreach. What it learns goes back to the PMM as proposals, never silent writes.

Trigger

• When: Someone is about to reach out to one named non-customer company, or asks in a Slack thread.
• Not for: A customer → customer-context. A competitor → competitive-profile. A competitor in a live deal → competitive-battlecard. Writing the message → writing-assistant. The deal committee → buyer-personas or stakeholder-maps. A ranked account list → not in this plugin.
• Examples: "@Claude research Lumio Logistics before I reach out" (Slack) · "Is there a reason to contact Lumio now?" (ask) · "What changed at Lumio since my last brief?" (since)

Inputs

• Args: company name or domain; optionally the role you will contact; mode brief (default), since or ask (one question, thread-sized). A line starting log: records an outcome.
• Depth: quick (default) or deep (adds Step 6). The request beats _config.md.
• Context keys: the brain; /context/prospects/; other skills' ledgers read-only (references/learn-from.md); ~~ connectors (references/connectors.md).
• Brain contract: Reads Section 1 (claims), Section 2 (pains, triggers, anti_persona, geography, committee_roles, size, industry), Section 3 (alternatives, status_quo), Section 5, Section 6 (proof, forbidden_claims), Section 8 (prohibited, approvals). Never writes the brain; learnings are proposals (references/feed-forward.md).

Connectors (Optional)

Categories: references/connectors.md. Rules on sources, links, untrusted text, people data: references/rules.md. No connectors: web search and pasted notes give the same shape. Pulled facts are drafts, tagged with category, tool and date.