A CRM relationship layer for marketing and sales

What a CRM for marketing should do

A CRM for marketing teams should preserve the relationship and sales context that survives after a campaign click: who the person is, which organization they belong to, what source or campaign value your team recorded, whether a deal exists and who owns the next action. It should not blur the boundary between CRM records and the systems that collect consent, deliver campaigns, calculate attribution or observe engagement.

Customermates provides the relationship and pipeline layer. It does not provide a campaign object, form builder, tracking pixel, consent platform, native attribution model, lead-scoring engine, enrichment feed, nurture sequence or embedded n8n runtime.

The questions the CRM should answer

For a clean handoff, the CRM should answer a small set of operational questions:

• Has the person or organization already been created?
• Which source or campaign value was supplied, by which workflow and at what time?
• Is there an active deal, and which configured stage is it in?
• Who owns the relationship and the next CRM task?
• Which external system remains authoritative for consent, campaign delivery and analytics?

Custom fields can hold source names, campaign identifiers, qualification notes or a reference to an external consent record. Those values are only as trustworthy as the capture and mapping process that writes them. Customermates does not infer a first touch, last touch or multi-touch model.

A bounded marketing-to-sales workflow

1. Choose the acquisition authority

   Keep the form, ad platform, analytics system or event tool responsible for the data it collects, including consent and tracking controls.

2. Map only approved fields

   A customer-operated integration can create or update supported CRM records through REST or MCP. Define field mapping, validation and deduplication before enabling writes.

3. Create the sales context

   Link the contact to an organization and, when justified, create a deal with a configured pipeline stage and an accountable owner.

4. Measure from explicit values

   Use stored fields and deal outcomes for deterministic reporting. Keep the marketing analytics platform authoritative for impressions, clicks, sessions and its own attribution model.

Lead scoring and enrichment

Customermates does not score leads or enrich records natively. If a team needs scoring, a separately operated workflow may read permitted signals from systems the customer is entitled to use, calculate a documented value and write it to a custom field. The external workflow owns the formula, schedule, provider contracts, suppression rules, retries, monitoring and cost.

The same boundary applies to enrichment. A customer-selected provider may return company or profile data to a workflow; an authorized REST or MCP action may then write selected values. Customermates does not include the provider, verify its source or continuously refresh those values.

Inbox, campaigns and follow-up

The managed unified inbox is available from Pro upward for supported connected accounts. It can keep individual email and supported channel conversations close to a contact. It is not an email-marketing system: there is no bulk campaign composer, sequence engine, deliverability infrastructure, subscription center or campaign analytics layer.

An authorized external MCP client can work with supported CRM records. On an entitled cloud account it can also read an existing inbox thread, save a draft inside that thread or explicitly send an individual message. You choose the client, its model and its subscription, and the client, not Customermates, decides whether to ask before it sends. Brand-new outbound messages cannot be saved as drafts through that surface, and send tools deliver when called.

When a dedicated marketing platform should stay in place

Keep a specialist system when you need:

• forms, landing pages, cookie controls or consent records;
• bulk email, journeys, sequences, preference centers or deliverability tooling;
• ad audiences, conversion APIs, identity resolution or multi-touch attribution;
• website engagement, product analytics or behavioral scoring;
• enrichment, intent data or campaign-budget optimization.

Customermates can receive the CRM subset of that work through documented interfaces. It should not become the system of record for operational data it does not model.

Plans and deployment boundaries

Starter includes core CRM records, custom fields, REST, webhooks and MCP access for external clients from €12 per user per month. Pro adds the managed unified inbox and its connected-account allowance. Self-hosting runs the AGPL community core with the Starter feature set; it does not include the unified inbox, the Mate assistant or an n8n runtime.

In the managed cloud, the application database runs in the AWS Frankfurt region; hosting and other subprocessors, including US providers, are listed on the subprocessors page, and a DPA is available. That deployment fact is not a GDPR certification, and Customermates holds none. The organization remains responsible for legal basis, consent, retention, deletion, provider assessment and configuration. If you need full control over where data lives, self-host the open-source core.

Frequently asked questions