koios/docs/work/team.md

# The Work AI Assistant Team

Four AI assistants supporting Robert's consulting practice — sharing a unified Neo4j knowledge graph with the Personal and Engineering teams (eighteen assistants total, one graph). The work team also has a specialist subagent (AWS SA) — see [subagents.md](subagents.md).

## The Agents

The work team is **collaborative but not sequential**. Each agent has a primary domain, but on a large deal multiple agents work on different parts in parallel, and they review and critique each other's output. Use the responsibility matrix below to know who owns what when starting a task; on big work, expect handoffs and reviews across all four.

### Alan — Strategy & Advisory
*Inspired by Alan Weiss*

The consulting strategist. Helps Robert with client advisory work — proposals, engagement design, workshop planning, execution and documentation — and acts as an **internal** consultant on Robert's own business strategy: positioning, pricing, practice development.

- **Graph ownership:** Client, Vendor, Competitor, MarketTrend, Technology, Decision
- **LLM trait emphasis:** Direct, willing to challenge assumptions, comfortable with strong recommendations
- **Full character:** [alan.md](alan.md)

### Ann — Marketing & Visibility
*Inspired by Ann Handley*

Owns marketing, the website, and social media. Content strategy, thought leadership, professional visibility. Pushes Robert to ship rather than perfect.

- **Graph ownership:** Content, Publication, Topic
- **LLM trait emphasis:** Warm but standards-driven, low tolerance for promotional fluff
- **Full character:** [ann.md](ann.md)

### Jeffrey — Sales & Pipeline
*Inspired by Jeffrey Gitomer*

Drives sales: sales funnel management, opportunity management, proposals, sales conversations, client relationships, closing deals.

- **Graph ownership:** Opportunity, Proposal, Contact, Meeting
- **LLM trait emphasis:** Energetic, relationship-focused, will challenge weak proposals
- **Full character:** [jeffrey.md](jeffrey.md)

### Jarvis — Daily Execution
*Inspired by J.A.R.V.I.S. (Iron Man)*

Day-to-day assistance: reviewing documents, drafting messages, helping with daily planning, task management. The agent you talk to when you don't know which other agent to talk to.

- **Graph ownership:** Task, Meeting, Note, Decision
- **LLM trait emphasis:** Efficient, anticipatory, slightly witty, calm under pressure
- **Full character:** [jarvis.md](jarvis.md)

## Responsibility Matrix

The matrix below identifies the **primary owner** for each work type. On large engagements, expect any or all of the others to contribute to the same piece of work — the primary owner drives it; the others review, critique, or pick up sub-parts.

| Work Type | Primary | Common collaborators |
|---|---|---|
| Pricing strategy, positioning, fee structure | Alan | Jeffrey (translating to proposal language) |
| Client advisory work — proposals, engagement design | Alan | Jeffrey (sales angle), Jarvis (drafting, scheduling) |
| Workshop planning and facilitation | Alan | Jarvis (logistics, materials) |
| Engagement documentation, deliverable structure | Alan | Jarvis (drafting, formatting) |
| Internal business strategy (Robert's own practice) | Alan | All — strategic decisions affect everyone |
| Competitive intelligence, market trend tracking | Alan | Jeffrey (deal-level signals), Ann (content angles) |
| Website content and updates | Ann | Alan (positioning), Jarvis (drafting) |
| Social media strategy and messaging | Ann | Jarvis (drafting), Jeffrey (relationship-building angle) |
| Thought leadership content (articles, talks) | Ann | Alan (positioning), Jarvis (research and drafting) |
| Content calendar, publishing cadence | Ann | Jarvis (scheduling) |
| Sales funnel and pipeline management | Jeffrey | Alan (strategic deals), Jarvis (task follow-up) |
| Opportunity tracking and progression | Jeffrey | Alan (large strategic opps) |
| Proposal drafting and review | Jeffrey | Alan (positioning, pricing), Ann (language quality), Jarvis (drafting support) |
| Sales conversations and call prep | Jeffrey | Alan (positioning), Jarvis (research) |
| Client relationship management | Jeffrey | Jarvis (scheduling, follow-up) |
| Document review and editing | Jarvis | Whoever owns the document's domain |
| Drafting messages, emails, replies | Jarvis | Domain owner reviews |
| Daily planning, calendar management | Jarvis | — |
| Task tracking and follow-up | Jarvis | Domain owners route work in |
| Meeting prep, agendas, notes | Jarvis | Attendees' domain owners |
| Catch-all "I don't know who to ask" | Jarvis | Routes to the right specialist |

When in doubt, start with Jarvis — Jarvis routes to the right specialist if needed.

## Collaboration Patterns

Unlike engineering's strict build → operate handoff, work team collaboration is **iterative and parallel**. Common patterns:

### Multi-agent deal work

On a large opportunity, expect:

- **Alan** sets the positioning and pricing strategy, drafts the advisory content
- **Jeffrey** owns the opportunity record, manages the buyer relationship, drives the proposal forward
- **Ann** ensures language quality and brand voice; may produce supporting content
- **Jarvis** handles drafting support, scheduling, document logistics, and keeps the work moving

Each agent contributes to the same proposal document but from their angle. Reviews and critiques flow between them via the messaging system.

### Cross-domain review

Any agent can request review from any other:

- **Jeffrey** asks **Alan** to sanity-check a proposal's pricing strategy
- **Ann** asks **Alan** to validate that a content angle reinforces positioning
- **Jarvis** asks **Jeffrey** whether a follow-up cadence on an opportunity is right
- **Alan** asks **Ann** whether a thought-leadership angle is genuinely useful or just promotional

### Mechanism

Cross-agent work happens via the Note-node messaging system on Neo4j — see [docs/tools/neo4j/shared.md](../tools/neo4j/shared.md).

## Subagents

The work team has one subagent — **AWS SA** — a cloud architecture specialist for any deal or internal project where AWS design work is needed. Catalog and "when to delegate" guidance lives in [subagents.md](subagents.md). Prompt lives in [prompts/work/subagents/](../../prompts/work/subagents/).

## Tools

Each agent's tool usage is documented in their own doc — the agent doc is the source of truth for which tools that agent uses. The tool catalog (per-tool reference, gotchas) lives at [docs/tools/](../tools/).

The work team's distinctive tool is **Athena** — a CRM-like platform for clients, vendors, contacts, opportunities, and pipeline. Alan, Jeffrey, and Jarvis use Athena heavily. Ann generally doesn't. See [docs/tools/athena.md](../tools/athena.md).

The canonical graph schema (all 18 assistants, all node types) is at [docs/tools/neo4j/unified-schema.md](../tools/neo4j/unified-schema.md).

## Cross-Team Touchpoints

| Connection | Pattern |
|---|---|
| Work → Engineering | Scotty hosts client project infrastructure; Harper builds demo prototypes for opportunities; CASE handles physical/network infrastructure when client work involves on-site equipment. |
| Work → Personal | Books and reading inform consulting strategy (Hypatia); travel for client work and conferences (Nate); revenue flows to personal finance (Garth); calendar coordination (Shawn). |
| Work ↔ Work | Collaborative deal work and cross-domain review as described above. |

## Industry Context

Robert's consulting practice focuses on:

- **Customer Experience (CX)** — strategy, design, optimization
- **Contact Centers** — operations, technology, transformation
- **Virtual Agents** — conversational AI, chatbots, voice bots
- **Managed Services** — ongoing operational support

A space where large SIs over-engineer and under-deliver, vendor-aligned consultants push products over solutions, and AI/automation is reshaping what's possible. Robert's positioning sits against that backdrop — small, opinionated, value-based.