Customermates CRM Overview

What is Customermates?

Customermates is a CRM built for modern teams that want a clear system for customer relationships without complex setup.
It combines classic CRM workflows with practical AI support, integrations, and automation. This page is the best starting point if you want a quick product overview before moving into API docs, AI-agent workflows, self-hosting, or feature-specific guides.

Our vision

Customermates was born out of a frustration with the two extremes in the market: platforms that are so simple they end up being little more than dashboards, and platforms that are so bloated, complicated, and enterprise-heavy that they slow great teams down.

We love building SaaS anyway, so instead of accepting that trade-off, we decided to build the CRM platform we wanted to use ourselves. With automation tools and AI agents taking over more repetitive and operational work, entire layers of legacy workflow software and enterprise add-ons can be replaced, while many older tools already feel behind what modern teams now expect.

Product overview

Customermates combines four connected building blocks: a practical core CRM, integrations for your technical stack, team settings that keep account and organization management clean as your workspace grows, and paid Enterprise capabilities for teams with stricter governance requirements.

Paid Enterprise capabilities currently include Audit Logging, Single Sign-On, AI Agent, and Whitelabeling.

How to use these docs

The easiest way to navigate this documentation is to start with CRM Comparison for strategic context, then continue with CRM Integrations when you want to connect systems. If you want to run a self-hosted CRM deployment, continue with Self-Hosting Get Started and Self-Hosted CRM vs Cloud CRM. From there, move into OpenAPI 3.1.0, MCP, n8n, or Skills depending on your setup.

For implementation patterns and product walkthroughs, continue with Report & Statistics, Custom Columns, Table & Kanban View, Webhooks & Events, Permissions & Roles, and Audit Logging.

If you are new, begin here and then move into the feature pages from the sidebar.

Core CRM model

Customermates keeps the CRM model intentionally compact. Instead of scattering information across many object types, the product centers on a handful of records that can be connected to each other in different ways. That makes it easier to understand a customer, see the commercial context around them, and move from one related record to another without losing orientation.

One important distinction is the difference between an organization and a company. An organization is a CRM record inside your workspace. The company is the workspace or tenant itself. This page is about CRM records and how they work together in the product.

Core entities

The main business records in Customermates are:

• Contacts for individual people
• Organizations for customer companies or accounts
• Deals for commercial opportunities and sales work
• Services for deliverables or line items connected to a deal
• Tasks for actionable follow-ups and internal work

Users sit across those areas as assignees. Contacts, organizations, deals, services, and tasks can all be assigned, filtered, and reviewed through the same workspace.

Relationship model

The product is designed so related records remain visible while users work. Contacts can be linked to organizations and deals, deals can carry services, and users can move across those connections from tables, cards, modals, and detail views.

That relationship model matters because it keeps commercial context, operational work, and ownership visible at the same time. Instead of understanding one record in isolation, teams can follow the links between records and work from a fuller picture.

How teams usually read the model

In practice, many teams use the model in this order:

1. Start with the contact or organization to understand the customer context.
2. Move into the deal to understand the commercial situation.
3. Review linked services to see what is part of the commercial scope.
4. Check tasks and assignees to understand operational follow-up.

That flow is important because Customermates is not built as a collection of isolated modules. It is built as a connected workspace where the same records support day-to-day work, grouped views, reporting, integrations, and permission-aware collaboration.