CMP42 // USE CASES // AGENCIESUSE CASE 03 OF 04
// Use case 03 · Agencies with AI ambitions

SELL THE AGENT
THAT KNOWS THE ACCOUNT.

You are already selling AI to your clients. Sell them the version that grounds on their actual accounts — not the demo that hallucinates a competitor.

// The problem

DEMOS ARE EASY. GROUNDING IS THE WORK.

The first AI project for a client usually looks great in the pitch. A capable model, a tidy prompt, a few sample records. Then it meets the client’s real data: a CRM configured over years for people clicking through screens, fields nobody remembers adding, knowledge spread across drives and wikis.

Now the agent answers confidently and wrongly. It invents a field. It names a competitor as a customer. And the reputation on the line is not the model vendor’s — it is your agency’s.

The durable part of an AI engagement is not the prompt. It is the structured context underneath it: an ontology that describes the client’s business, a graph an agent can read, and a trail that shows what the agent did. That is what CMP42 is for.

// What you build on

ONE ONTOLOGY PER CLIENT.

Models

A per-client ontology

Every client’s business is different: distributors here, franchise locations there. Describe it in Models — TypeScript-shaped YAML, versioned in git, migrated with one command.

Migrations are backwards-compatible, so a schema change for one client does not surprise the agents already in production.

Any model

The model your client approved

CMP42 ships no proprietary AI layer. Your client decides which model they trust; CMP42 provides the context. Anything MCP-compliant connects — Claude Desktop, Claude Code, Cursor, Cline or a custom agent on the MCP SDK.

For everything else, REST and GraphQL expose the same operations. Bring your own model →

Processes

Delivery you can show

Wrap agent work in Processes with human approval steps. Every run records what the agent read, what it wrote and what it cost in tokens — per process, per run.

That turns “the AI is working” into something you can review with the client, line by line.

// Where it runs

MANAGED OR SELF-HOSTED.

Managed EU tierSelf-hosted
Who operates itprotagx, EU-hostedYou or your client, on their Postgres and object store
Training on dataCMP42 does not train on your dataNothing leaves the environment at all
TrackingNo third-party analytics, fingerprinting or session replayUnder the operator’s control
AvailabilityAlpha from October 2026Image published with Beta in Q1 2027; Design Partners get Alpha access

Clients differ in how much control they need over their data. CMP42 offers the same product two ways: operated by us in the EU, or run on the client’s own infrastructure. Same binary, same models, identical MCP tool surface — so the work you do on the ontology carries over either way.

Self-hosting in detail → · EU data residency →

If you plan to run CMP42 for several clients, raise it on the 15-minute call — we will tell you honestly what the Alpha supports today.

Multi-workspace operation — one agency running several isolated CMP42 workspaces, one per client — is a standard feature from the Team tier upwards, with an Agency-Owner role that has cross-workspace access while each client sees only their own. White-label (running CMP42 under an agency brand with a custom admin-UI domain for clients) is planned for GA. For agencies embedding CMP42 into their own client offerings, see the Commercial Agency Licence below.

// Scenario

A CLIENT ASKS FOR A SALES ASSISTANT.

Illustrative scenario

From mapping session to reviewed output

A fictional agency and a fictional client. The steps show how the concepts fit together; they do not describe a delivered project, and interfaces will change during Alpha.

  1. The agency runs a model-mapping session with the client: which objects matter beyond contact, company and deal — say, distributors and product lines — and which fields the sales team actually uses.
  2. The agency declares those as Models, reviews them with the client like code, and migrates with one command. MCP tools for the new models are generated automatically.
  3. The client’s sales team connects the agent they already use; the agency builds a small custom agent on the MCP SDK for the team’s Slack channel. Both read the same graph.
  4. Writes that matter — notes on key accounts — go through a Process with the client’s sales lead as the approval step.
  5. In the monthly review, the agency walks the client through run history and token cost per process: what the agents did, what was approved, what it cost.
// What it means for your offer

FROM PROMPT WORK TO CONTEXT WORK.

An agency that owns the context layer sells something more durable than a prompt: a documented ontology, a graph that any future agent can read, and processes a client can audit. When the client switches models next year, that work remains.

One caveat, in the spirit of an honest Alpha: the Design Partner Program asks for real usage on real data, not a demo tenant. If you cannot yet bring a client workload, Beta opens in Q1 2027 with a waitlist.

Shape the tool surface your clients will use

Design Partners propose and name one MCP tool that ships to every future customer — and get a monthly co-design call on their roadmap.

→ Apply to be a Design Partner
  • Grounded answers with citations to the client’s own objects.
  • An ontology the client owns, versioned and reviewable.
  • Model choice stays with the client — no lock-in to an AI vendor through us.
  • An audit trail per run, including token cost.
  • EU-managed or self-hosted, depending on the client’s requirements.
// Commercial Agency Licence

FOR AGENCIES EMBEDDING CMP42.

The Design Partner Program (€6,900 one-time) is a single-workspace programme. For agencies embedding CMP42 into work delivered to their own clients — repeated across multiple client deployments — we offer the Commercial Agency Licence. It is deployment-based, priced per client environment, and independent of the Design Partner Program.

When it applies

Every CMP42 deployment an agency delivers to a client runs under the Commercial Agency Licence, from the first one. The licence covers bespoke builds, one graph per client, and products the agency markets under its own name ("Acme CRM powered by CMP42").

Three tiers

TierWhoPer deployment / monthRate-lock
Founding PartnerFirst 3 agencies signing by 20 November 2026€3002 years past GA · plus named-partner obligations
Design Partner (Agency)Agencies signing during Alpha, slots 4–12€5002 years past GA
Post-GA regularAgencies signing after GAPlaceholder €800–1,000 · confirmed at GAStandard terms

Founding Partner obligations

The €300/deployment/month rate for Founding Partners is not a discount — it is a paid exchange. In return, the Founding Partner grants CMP42:

  • Public named-partner rights. Logo on the CMP42 website, mention in launch and roadmap posts.
  • One reference call per quarter. 30 minutes with a qualified prospect at CMP42's request.
  • Case-study rights. Once measurable results exist, CMP42 may co-author a case study with the Founding Partner's review.

What the licence period covers

The Commercial Agency Licence is time-based: during the licence period you run the current CMP42 release with support and updates. Renew it to keep receiving new releases and support.

Common questions

We build a bespoke CRM for one client. Do we need the licence?

Yes. Each client deployment runs under the Commercial Agency Licence; the Founding Partner and Design Partner rates apply from the first one.

What counts as a "deployment"?

One separate CMP42 instance (Managed workspace or self-hosted install) serving one client. Two agents pointing at the same workspace = one deployment. Two workspaces for two clients on the same infrastructure = two deployments.

How does this differ from the €6,900 Design Partner Program?

The Design Partner Program is a single-workspace Alpha programme with founder access, monthly co-design and a lifetime founder rate. It is not per deployment. Agencies embedding CMP42 across multiple clients use the Commercial Agency Licence instead — or in addition, if the agency wants to be a Design Partner for their own agency workspace.

// Questions on this

What people ask here

The same answers as in the CRM FAQ, next to the case they belong to.

MKT-01

Can CMP42 replace marketing automation?

Not entirely, and that is deliberate. Sequences, sending and opt-out management are not part of the Alpha. CMP42 takes the part that comes before them, the part classic tools often reach too late: it checks who may be contacted at all and why, and it rejects a recipient list that breaks the rules.

The work is split like this: the agent proposes segments, content and the next step. CMP42 supplies the context and checks the rules. A person approves. Your existing tool still does the sending.

Prompts and sources for this question

MKT-02

What is the difference between a workflow and a CMP42 Process?

A classic workflow is triggered by an event and runs actions automatically, often out of sight. A Process in CMP42 is a named sequence of steps, some carried out by an agent and some by a person. Every step reads and writes the same graph, and every transition is logged.

What it adds over a Zapier hop:

  • Approval steps (human in the loop): the Process waits until a person agrees. Approval can be given in the Podma Workbench, through an MCP tool, through a signed link by e-mail, or through a Slack or Teams bot.
  • Run history and replay: every run can be traced step by step and rerun against an earlier state of the data.
  • Cost transparency: token usage is visible per Process and per run, in euros as well.

How exactly Processes are declared is being designed by protagx together with the design partners during the Alpha.

Prompts and sources for this question

Decided1
HUB-04

What corresponds to dynamic and static HubSpot lists?

A dynamic list updates itself from criteria. In CMP42 that is a saved view with filters in the Podma Workbench, or a query the agent reruns whenever needed. A static list is a snapshot. Its closest counterpart is a recipient list that has been checked against your rules and approved.

Prompts and sources for this question

Decided1

Decided and on the way. Say which one you need first:

  • Open - you decide1Follow-up sequences
  • Open - you decide1Event-driven processes
  • Open - you decide1Frozen audiences

All 43 questions in the CRM FAQ

¹ Planned for a future release.