Headless CRM

A CRM accessed primarily through APIs. The data and workflows are the product; the UI is optional. The same idea as headless e-commerce: separate the data from the interface so any front-end (or AI agent) can use it.

Three reasons: AI agents can read and write to it cleanly, custom front-ends can be built per team, and integrations are first-class instead of bolted-on. The cost is that everything has to be wired up. There's no out-of-the-box workflow.

Mostly internal builds at companies that outgrew Salesforce or HubSpot. A typical setup: Postgres or a warehouse as the data layer, an enrichment service feeding it, custom UIs for each role, and AI agents working across all of it.

For most Series B startups, no. You do not have the engineering capacity to maintain it. Most teams should stay on Salesforce or HubSpot and add a headless data layer (like Landbase) underneath.

A small number of post-Series-C companies do, usually after outgrowing Salesforce or HubSpot's customization limits. The pattern is typically Postgres or a warehouse as the data layer, an enrichment service feeding it, and custom UIs per role. Maintenance cost is the dealbreaker for most mid-market teams.