Macro CRM

Capabilities

• Self-building People, Company, Deal, and Job records Records are created and updated from email and calendar activity, so the pipeline reflects what actually happened instead of what someone remembered to log.[1]

• Activity timelines with AI summaries Every record carries a history of interactions plus an AI-generated summary, which makes handoffs and pipeline reviews faster without reading whole threads.[1]

• AI Playbooks that run follow-ups automatically Playbooks are configured once and then execute routine follow-up work on their own, shifting CRM upkeep from daily discipline to one-time setup.[1]

• Tasks and follow-ups tied to records Action items live on the record they belong to, keeping next steps visible where the context already is.[1]

• Meeting preparation from shared workspace memory Because the CRM shares AI memory with email, chat, and docs, pre-meeting briefs can draw on the full workspace rather than the CRM alone.[1][2]

• Gmail and Outlook sync with Salesforce and HubSpot import The two dominant business mailboxes are supported, and documented import paths cover moves from spreadsheets or the two largest incumbents.[1]

• Automatic dedupe and enrichment Duplicate records are merged and records enriched without manual cleanup, addressing the data-rot problem that normally requires an admin.[1]

• Free tier with self-hosting under AGPLv3 The workspace is free with no seat licenses, and the macro-inc/macro repository documents self-hosting under the AGPLv3 alongside managed cloud editions.[1][2]

Who it fits

• When the choice is between updating the CRM and following up with the customer, automatic record building keeps the pipeline visible without hiring an operator.[1][2]

• Companies already paying for separate mail, chat, docs, task, and CRM products get one workspace where a record, its history, and its next step sit together.[1][2]

• Macro positions its free tier and $20-per-user Business plan against Salesforce seat economics, which suits teams whose needs fit inside the documented scope.[1]

Boundaries to check

• SSO, audit, residency, and SLA terms are documented at the workspace plan level, but CRM-specific governance evidence and a track record are thin.[1]

• No public API reference was found for Macro in this pass, so designs that sync the CRM with the rest of the stack over documented endpoints cannot be confirmed.[1][2]

• With no inspectable Reddit or G2 reports and a rollout still in progress, teams that require peer evidence should wait or pick an established option.[1]

Fit and compatibility