The customer record, without the CRM tax.

Status: an idea on the roadmap. Not committed, not scheduled, and no dates. This page exists so you can see where our thinking is going and tell us if it is going somewhere useful to you.

Most SMB teams outgrow a spreadsheet long before they can justify a full CRM — and then pay for a full CRM anyway, mostly to store contacts and remember follow-ups. A CRM Workbench would cover the mechanics that actually get used: lead intake, contact records, a pipeline you can see, communication history, and lifecycle stages.

Why it belongs in the suite rather than beside it

The argument for building this is not feature parity with the established CRMs — they cover that surface well. It is that a CRM sitting inside the suite can be asked questions that span workbenches.

Lead capture on a marketing site flows into a CRM. Community activity tells you which accounts are engaged. Content can be targeted at a segment. Today each of those connections is per-system plumbing you build and maintain. In the suite they are the same data, so an agent can answer "this lead read three posts, asked a question in the community, then visited pricing" without anyone wiring it together first.

What would have to be true first

We would want AIM Engines' cross-workbench correlation shipped, so the CRM has something to talk to, and enough real lead volume to be worth managing. Until then, integrating with an external CRM through an adapter is the honest answer, and it is what we would recommend.

This is a roadmap idea, not a product. If lead and pipeline mechanics are a live problem for you, tell us what you actually need — roadmap order is driven by the jobs that come up most often, and that is decided by conversations like that one.