Macro folds email, messages, docs, tasks and CRM into one workspace: cross-references live in a bidirectional graph, and agents search attachments directly

Macro puts email, messages, docs, tasks, calls, agents, CRM and databases into a single interface with shared team-level memory, and everything in the workspace is @-linked and searchable. Teams have typically used separate products such as Slack, Linear, Notion, HubSpot and Superhuman, which do not work together as one system. The Macro team says that as its previous venture scaled to about 20 people, each team picked its own tools and the company was held together by MCP and Zapier, described as not computable and chaotic.

Each surface is purpose-built for its job but shares the same backend, and cross-references between a doc and a task or a channel message and an email are stored natively as a bidirectional graph. Email, messages, docs and tasks are no longer separate products but link to each other under the same permissions system. Macro was dogfooded by a team of about 15 for two years, is built in SolidJS and Rust, and is organized as modular blocks.

Macro Mail's unified search tool lets agents search all attachment PDFs parsed out of email directly, rather than pulling email threads and then attachments. The prior retrieval path was to pull email threads first and then take attachments from them. Macro says the tool is designed for cross-inbox retrieval, and agents can also draft, edit and send emails from AI chats.

The demonstrated scope is the Macro team's two-year internal trial with about 15 people and the integration of email, messages, docs, tasks, calls, agents, CRM and databases in one interface, aimed at teams that want one system for collaboration and agent retrieval.

The available description comes from a product introduction and the team's own account, with no external-team comparison or quantitative metrics; how the unified workspace performs in larger teams is not addressed in the material.