CRM
A working sales CRM, independent of every other domain. Run a shop’s own sales book, an agency’s client book, or both on one deployment.
What it owns
Section titled “What it owns”- Accounts and contacts — the organisation you’re selling to, and the people at it. A contact can exist before it’s tied to an account (an inbound enquiry from an unknown org).
- Leads — flat, contactless raw capture at the top of the funnel. The API supports converting a lead into an Account + Contact + Opportunity in one transaction, linked back for attribution — the staff admin doesn’t wire a Convert button to it yet, so today that’s a manual create-and-link.
- Pipelines and opportunities — a tenant-configured funnel (stages are data, freely renamed/reordered) with kanban deal boards. An opportunity is the CRM’s analogue of a commerce order: the keystone record everything else hangs off.
- Quotes — a priced proposal behind a deal, with server-owned line and quote totals. When Commerce is installed, quote lines can pull real products from Catalog; without it, lines are freeform.
- Activities — notes, calls, emails, meetings and tasks logged against an account, contact, lead or opportunity, with a due-date reminder sweep and a shared timeline.
- Role and team visibility — unlike a storefront (same catalog for everyone), CRM shows each rep a different slice of the same tenant’s data based on ownership and team.
CRM in the staff admin: accounts, contacts, leads, pipeline board, deal drawer with quoted items and files, and an activity timeline.
/api/v1/crm/ — staff-facing only, consumed by the Next.js admin.
Related: CRM admin guide · Commerce (quote lines can reference its catalog) · Users & roles.