Account research
Pull the public record on a target: filings, releases, hiring, news. Bundle it into a brief and switch providers as the question changes.
Loading
Use case · sales teams
Research, outreach drafts, deal-room briefings, and pipeline triage. Provider choice through your own keys on Desktop, CLI, and VS Code, with a visible label on every route your account context takes.
Where it shows up
Pull the public record on a target: filings, releases, hiring, news. Bundle it into a brief and switch providers as the question changes.
Draft messages in your team's voice. The model sees your prior outreach as context only when you've given it permission to.
Cross-provider continuity matters here: long-context work for the data room, prose for the narrative summary, all in one thread.
Posture for revenue teams
| Confidentiality | Local Mode for sensitive deals; keys stay encrypted on your device. |
| BYOK | Pay providers directly on Desktop, CLI, and VS Code. Use your existing API budget. |
| Tools | Connect CRM and email through MCP connectors, behind explicit tool approvals. |
| Visibility | Provider labels and tool approvals stay visible on every route. |
Start now
Bring your own keys on Desktop, CLI, and VS Code, and keep account context under your control while the team works.