macro
Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory.
Macro, a unified workspace built in Rust and SolidJS
Macro is an all in one team workspace joining email, chat, docs, tasks, agents, and CRM behind a shared team level memory and @links.
The all in one pitch
Macro is described as the all in one workspace for a team, unifying email, messages, docs, tasks, agents, and CRM in a single fast interface with shared team level memory. Everything in the workspace is @linked and searchable, so a team and its agents never have to switch tools. The block list runs from email with a multi account unified inbox to messages, tasks, docs, canvas, agents, calls, file storage, pull requests, and CRM.
The origin story
The team wanted a single operating system for their startup. They used Slack, Linear, Notion, HubSpot, and Superhuman, but the tools did not work together as one system, and as the previous venture grew the company was held together by MCP and Zapier. Macro was designed in NYC and Toronto, dogfooded by a team of about 15 for two years, and built in SolidJS and Rust. The README frames the goal as an operating system that any small company, or a team at a larger company, could adopt.
Blocks and one backend
Macro is composed of blocks designed to be modular and extensible, working together like Lego. Each surface is purpose built, but all share the same backend, with cross references between a doc and a task or a channel message and an email stored as a bidirectional graph.
Editorial conclusion
The README reads like a founding story as much as a product page, and this review stays with that framing. Using the product, or judging whether it holds together, is left to the reader.
Community notes