koios/docs/tools/athena.md

Athena

Business relationship and pipeline management — clients, vendors, contacts, opportunities.

• MCP server name: athena
• Prompt snippet: prompts/tools/athena.md

What It Is

Athena is Robert's CRM-like system for the consulting practice. It tracks clients (organizations he works with), vendors (technology partners and potential competitors), contacts (people at those organizations), and opportunities (deals in the pipeline). It also includes a pipeline dashboard view.

Athena is the source of truth for pipeline state. Neo4j tracks the assistants' interpretation and history; Athena tracks the records of record.

MCP Capabilities

Athena's MCP coverage is expanding incrementally. The shape of what agents can do:

• CRUD on CRM and vendor data — read, create, update, and delete clients, vendors, contacts. Available today via MCP.
• Opportunity tracking — read and (progressively) write opportunity records, stage transitions, notes
• Pipeline dashboard — read pipeline summaries (counts, values by stage and status)

The specific MCP tool names available at any moment are surfaced by MCP discovery — check tools/list rather than relying on a static catalog here. New tools are added as Athena's MCP coverage grows; documenting specifics here would go stale fast.

What It's Good For

• Looking up a client before any conversation about them (history, services provided, key people)
• Pipeline visibility — what opportunities are active, in what stage, at what value
• Contact intelligence — who works at which org, what's their role, how to reach them
• Vendor research — what's the vendor's footprint, are they a competitor, what's the partnership status
• Pre-call prep for sales conversations
• Identifying at-risk accounts, stale opportunities, or expansion candidates
• Writing back what was learned — updating a contact's notes after a meeting, advancing an opportunity stage after a milestone, recording a new contact at an existing client

What It's Not Good For

• Strategic analysis on its own — Athena provides the data; the agents (Alan especially) interpret it
• Replacing Neo4j — Athena is the system of record; Neo4j is the institutional memory of how deals progressed, what was said, what was learned across all four work agents
• Operations outside CRM scope — engineering infrastructure, personal data, etc. are not Athena's domain

Vocabulary

These values appear across Athena records and matter for filtering and conversation:

• Opportunity status: Active, Won, Lost, Dropped
• Opportunity stage: Prospecting, Qualification, Workshops, Proposal, Negotiation, Closed
• Vendor is_competitor flag — same vendor table, different lens. Competitive-intel queries and partnership queries both run against vendors.

Known Gotchas

• Tool coverage is incremental. If MCP discovery doesn't surface a tool you expected, it may not be wired up yet rather than missing by design. Surface that rather than confabulating around the gap.
• List vs. detail. List endpoints return truncated overviews; for any depth, follow up with the corresponding detail call. The list view is for browsing; the detail view is for analysis.
• Stage and status are independent. A Closed stage can be paired with Won, Lost, or Dropped status. Don't infer one from the other.
• incumbent_vendor is competitive intelligence. When an opportunity has an incumbent, the sales motion is fundamentally different from a greenfield deal — flag it to Jeffrey and Alan.
• Updates have consequences in the real system. Unlike Neo4j (where assistants own their own interpretation), Athena writes touch the system of record that Robert and any downstream automation depend on. Confirm before writes that materially change pipeline state — opportunity stage transitions, status changes, contact deletions.