CRM for SaaS teams that connect their own product data

A CRM for SaaS keeps every account that trials, buys, expands or churns in one place, with the people in it, the deals around it and the conversations behind it. Customermates is an open-source, AI-native CRM made in Germany for product-led SaaS teams that want to shape their own lists and connect their own product through a REST API, webhooks and n8n; it has no native billing or product-analytics sync.

"SaaS CRM" also means a CRM that is itself delivered as a cloud service, and Customermates is that too, so the first section below separates the two meanings.

At a glance

Fits

B2B SaaS teams from the first sales conversations to a small sales and success team, who are comfortable wiring product data in themselves.

Model

Accounts, contacts, trials, subscriptions and deals as lists and fields you define. A new workspace starts without lists.

Connections

REST API, 16 webhook events, an n8n community node and 59 MCP tools for your own AI client, on every plan and when self-hosted.

Not included

Native billing or product-analytics integrations, lead scoring, sequences, web forms, SSO and native mobile apps.

Accounts

Plan, trial end and renewal as fields

Product data

In through REST API or n8n

Change events

Out through signed webhooks

AI access

Your own client over MCP

Hosting

Cloud or your own server

What is a SaaS CRM?

The phrase has two meanings, and search results mix them.

Customermates covers both. It runs as Customermates Cloud, a hosted service billed monthly per user, and as a self-hosted installation of the open-source core. What it does not do is understand subscriptions on its own. There is no built-in subscription, trial or billing model, so you define those as fields and lists and decide how product data reaches them.

What does a SaaS company need from a CRM?

• Accounts, not just people. A B2B product is bought by a company and used by many users. The record you open before a call is the account, with its users as linked contacts.
• Lifecycle on the record. Trial, paying, at risk and churned, with the dates that matter: trial end, renewal, last activity.
• Product data next to the relationship. Plan, seats and a usage number belong beside the notes and deals, not in a separate dashboard that sales never opens.
• Sales-led and self-serve at once. Most deals close without a call, while larger accounts need a pipeline and an owner.
• An API your own engineers can use. A SaaS team usually prefers a documented API and webhooks to a catalog of ready-made connectors.
• A way to hand over. When the first customer success hire arrives, the account history is in the CRM and not in someone's inbox.

How do you model accounts, trials and subscriptions in Customermates?

A new workspace starts without lists, so everything below is an example you create yourself in Configure, or let the AI workspace setup in Customermates Cloud build from your description. Every field name is yours to choose.

Accounts and contacts are linked by a relationship, and one contact can belong to several accounts. If you keep Subscriptions as its own list, a calculated field on Accounts can total the MRR of the linked subscriptions, and another calculated field can multiply MRR by 12 for annual recurring revenue (how calculated fields work). Without a Subscriptions list, MRR is a plain money field on the account that you or your integration set.

Two things to know. First, MRR here is a number someone or something writes into a field; Customermates does not compute it from invoices. Second, tasks have no built-in due date or status, so a follow-up date is another date field you add.

Useful saved views for a SaaS team:

1. Trials ending: accounts with Lifecycle Trial, sorted by Trial ends, earliest first.
2. Renewals: paying accounts sorted by Renewal date.
3. Expansion board: deals on the pipeline board, one card per deal, linked to its account.
4. Quiet accounts: accounts with a Last active date older than 14 days (filter reference).

Saved views are personal, so each person saves their own. To group accounts by plan, size or lifecycle in the first place, the customer segmentation guide shows the fields and views.

How does product data get into the CRM?

Customermates has no native integration with a billing tool or a product-analytics tool, so product data arrives through the API: your backend, a scheduled job or an n8n workflow writes it into the fields above.

1. Create an API key

   Open Settings → API keys and create a key. It acts with the role of the person who owns it, so there are no per-key scopes, and on Customermates Cloud that person is a paid seat like any other. The API keys guide covers expiry and rotation.

2. Read your lists and fields

   Call POST /api/v1/model/discover and POST /api/v1/model/read to get the stable IDs of your Accounts list and its fields. They stay the same when you rename a field.

3. Write on signup

   Send a create mutation with an idempotency key, so a retried job does not write the account twice. Records are addressed by their own ID, so keep your product's account ID in a text field and find the record with an exact-match query before you write.

4. Update from your billing and usage data

   Write plan, MRR, seats and last-active from the system that owns them. That system stays the source of truth; the CRM holds a copy for the people who sell and support.

5. Subscribe to changes

   Add a webhook for Record updated on the Accounts list, with a secret and, if you like, only the Lifecycle field as the trigger. Every delivery is signed with HMAC-SHA256, retried up to 10 attempts in total and can arrive out of order, so deduplicate by event ID.

The REST API page lists every route and the OpenAPI document, and the webhooks reference lists the event payloads. If you prefer visual flows to code, the Customermates community node for n8n covers the same record API, and its trigger creates the webhook subscription for you. n8n is a separate product with its own plans and is not included; the n8n guide and the workflow automation page show the setup.

What can your own AI client do with account data?

Customermates has an MCP server with 59 tools on every plan, self-hosted included. Connect Claude, ChatGPT, Gemini, Cursor or another client, and it reads and updates the records your role allows, using your own AI provider and subscription. The MCP server explainer covers what the protocol is and how clients connect.

For a SaaS team, a typical use is account research before a call: ask the client which accounts have a trial ending this week, and it reads the Trial ends field of your Accounts list and the linked contacts. After the call, ask it to set the Lifecycle and add a note. What the client may change is limited by your role. Any confirmation before deleting or sending is the client's own behavior, not a check in Customermates, so review what you ask it to do.

What changes on Customermates Cloud?

Some features exist only in Customermates Cloud. The unified inbox brings email from Gmail, Outlook or IMAP together with LinkedIn, WhatsApp, Instagram and Telegram, and the plan decides what you can connect:

• Starter and self-hosted: no connected messaging accounts.
• Pro: each person's own accounts, 1 connected account per user included, plus threads shared one at a time.
• Business, Max or Enterprise: needed to share a whole account, for example a shared sales or success mailbox.

Participants are matched to contacts by email, phone or LinkedIn identity. A conversation is linked to an account only when a person, or an agent you ask, links it.

Mate, the assistant inside Customermates Cloud, summarizes an account, updates records and drafts replies within your plan's hosted AI credits. A routine can run Mate when a record changes, for example when Lifecycle changes to At risk, to save a check-in draft for you to review. Mate sends a message as soon as you ask it to, so ask for drafts when you want to read first. Mate and routines are not available when self-hosted.

Where is Customermates the wrong choice for a SaaS company?

• No native billing or product-analytics integration, so you build or buy the connection.
• No lead scoring, health scoring or enrichment.
• No sequences, drip campaigns or bulk messaging.
• No embeddable web forms: a demo-request form on your site needs your own backend to write to the API.
• No SSO or SAML sign-in, no certification such as ISO 27001 or SOC 2, no native mobile apps.
• Saved views are personal, and there are no field-level permissions.

If one of these decides the purchase, look at a tool built for it. Customermates publishes this page, so read the table as pointers, not a ranking. Vendor details were checked on 8 November 2026 on each vendor's own website.

Product analytics, billing and subscription management, support desks and in-app messaging stay in the tools built for them. Customermates is the place where sales and success see the account, not where those systems run.

Should a SaaS company self-host its CRM?

Some SaaS teams prefer to run their CRM next to their own infrastructure. Customermates is open core, and a self-hosted installation runs with Docker Compose on PostgreSQL 16. It has the Starter feature set with REST, webhooks and MCP, but no inbox, no Mate and no AI workspace setup, and you operate the server, backups and updates. Self-hosting is not a compliance guarantee by itself.

In Customermates Cloud, the primary database is in the AWS Frankfurt region. Subprocessors, US providers among them, are on the subprocessors page, and a data processing agreement is available. Customermates holds no certification such as ISO 27001 or SOC 2, which matters when a customer's security questionnaire asks about your vendors.

What does it cost?

Prices are per user per month, billed monthly in euros. The trial runs 7 days on Customermates Cloud without a credit card. The API, webhooks and MCP have no surcharge.

Details are on the pricing page. If founders still sell every deal themselves, the CRM for startups page covers the handover to the first sales hire.

Frequently asked questions