CMP42 // USE CASES // OVERVIEWTHE FIRST TWELVE
// Use cases · The first twelve

SAME DATA.
GROUNDED AGENTS.

CMP42 is built for teams whose workflow already moved to AI — and whose CRM did not. Four kinds of teams are the first we are building with. What they share: agents that read a real graph before they write a word.

// Where the workflow already moved

THE DATABASE STAYED PUT.

A year ago, a sales manager checked the pipeline by opening the CRM. Today the honest answer is often: "I ask my agent to summarise it, and if the summary looks off, I open the CRM." A partner in a consulting practice drafts the follow-up note in Claude, with a pasted transcript and a request to make it sound like them.

The workflow has changed. The database has not. Most teams we speak to have either wired their CRM into an agent through Zapier and a lot of Python — with inconsistent results, because the schema was never built for agent reading — or given up and paste transcripts into ChatGPT. CMP42 is built for the teams who want neither.

// How teams use CMP42

THREE PATTERNS, ONE GRAPH.

The four segments look different on the surface. Underneath, they use CMP42 in the same three ways.

Pattern 01

Grounded agents

An agent that answers from typed objects and cites its sources. Connect Claude Desktop, Claude Code, Cursor, Cline or your own agent built on the MCP SDK: it reads the Context graph through MCP tools instead of guessing from a paste.

Ask "who at Aspen owns the Q4 renewal?" and the agent walks named edges — contact owns deal — and points to the objects it read.

Pattern 02

Drafts from real history

Before an agent drafts the renewal note or the client follow-up, it reads the account: who owns the deal, which documents were authored, what the last notes said.

A Process can hold the draft for a human to approve, and every write records whether a human or an agent produced it.

Pattern 03

Frameworks as context

The playbook your team keeps re-explaining becomes objects in the graph, linked to the engagements and accounts where it was applied.

Declared in Models and versioned like code, it gives the next agent your method as a starting point — not a blank prompt.

// What every use case relies on

SMALL PARTS. DELIBERATELY.

None of the use cases needs a special edition. They run on the same three movements — Context, Models, Processes — and the same tool surface. What differs is the ontology each team declares and the processes it chooses to make observable.

That is intentional. A CRM small enough to hold in your head is one you can explain to your agents, your auditors and your next hire. Why we built it this way →

  • Context — people, content and knowledge as one graph with typed edges, versioned and attributable. Context →
  • Models — your ontology in git-versioned, TypeScript-shaped YAML, validated at write-time. Models →
  • Processes — human-plus-agent workflows with approval hooks, run history and replay. Processes →
  • MCP tools generated per model, with REST + GraphQL parity for everything else. MCP tools →
  • Your hosting choice — managed by us in the EU, or self-hosted on your Postgres and object store. Self-hosting →
// Growth

GROWTH FROM THE SAME DATA.

Most teams do not have a data problem. They have a reading problem. The contacts, deals, call notes and proposals already exist — scattered across a CRM, a drive and a wiki, readable by the humans who remember where things are, and by agents only as pasted text.

In CMP42, growth does not come from collecting more. It comes from the same data becoming usable by more readers. Once an account is a typed object with named edges to the people, documents and notes around it, every agent you connect can work with it — the one drafting follow-ups today, and the one your engineers build next quarter.

Why the effect compounds

Loop 01 · Read

Every agent reads the same graph

Connecting a new MCP client does not mean a new export, a new sync or a new prompt template. It reads the context that is already there — with the same auth and the same audit trail.

Loop 02 · Write back

Every approved note becomes context

Notes an agent writes back are versioned and attributed. Once approved, they are part of the graph the next run reads — so the second renewal note starts from more than the first did.

Loop 03 · Extend

Every model adds tools

When you declare a new model, CMP42 generates MCP tools for it. Extending your ontology extends what agents can do, without a separate integration project. Defaults stay lean; extension stays explicit.

We publish no growth figures. CMP42 is in Alpha. Any percentage on this page would be invented — and invented numbers are exactly what we are building against. Measured outcomes will come from Design Partner case studies, as described below.

// Real results

RESULTS, PUBLISHED WHEN THEY ARE REAL.

The landing page talks about real results. Here is what that means today: there are none to publish yet, because Alpha begins in October 2026. We would rather show you an empty shelf than a fabricated testimonial.

The first Design Partner case studies are planned for Q4 2026, alongside the stabilisation of the MCP tool surface. They are optional for partners: if a partner agrees, we co-write the case study together; if not, we acknowledge them quietly and never name them without permission. We do not ask for testimonials, referrals or logos.

Where results come from

Now
Design Partner Program open. Twelve slots, applications close December 2026.
Oct 2026
Alpha begins with the first Design Partners. Weekly release cadence, real usage on real data.
Q4 2026
First case studies published. MCP tool surface stabilises.
Q1 2027
Beta opens to a broader waitlist. Self-hosted image published.
H1 2027
General availability. Published pricing takes effect.

Be one of the first case studies

If one of the four use cases describes the mess on your desk, come and Alpha it with us. The application starts with a 15-minute call.

→ Apply to be a Design Partner
// Questions on this

What people ask here

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

BAS-01

What is a CRM, and what changes when AI becomes the interface?

A CRM (customer relationship management system) keeps track of contacts, companies, sales opportunities and every interaction with them. Classic CRMs such as HubSpot, Salesforce or Pipedrive are built for people who open forms, fill in fields and drag deals across a pipeline.

Many teams now ask their AI assistant about the pipeline first and only open the CRM when the answer looks odd. When the agent reads a data model that was designed for clicks, it is quick to invent fields or stages. CMP42 turns this around: the data model is built for agents, and the interface is the AI your team already works with.

Prompts and sources for this question

STA-01

Which teams is CMP42 meant for first?

For teams whose way of working has already moved to AI while their CRM has not. Four groups are in focus:

  • Boutique consultancies: your own framework becomes context the agent uses in the next engagement, instead of a slide copied into every deck.
  • Product-led B2B teams: agents draft renewal and follow-up notes from the real customer history.
  • Agencies with AI ambitions: you build agents for your clients that work on their real accounts instead of hallucinating.
  • Teams leaving HubSpot: you want lean data and a real API, not the next platform.

Prompts and sources for this question

Decided1
STA-02

How do we get started in practice?

  1. Inventory: which objects, fields and relationships does your team really use?
  2. First Model: map the standard objects and declare only what survives the inventory.
  3. Import: CSV for contacts, companies, deals and notes; the rest with support in the design-partner programme.
  4. Connect Claude: add the API token to the MCP configuration of Claude Desktop or Claude Code.
  5. Set up one Process with approval: renewal notes that a person approves, for example.
  6. Expand: every new Model brings new tools, without an integration project of its own.

Prompts and sources for this question

STA-03

Which questions can I ask Claude once CMP42 is connected?

Goal Example prompt for Claude What happens behind the scenes
Clarify ownership “Who at Aspen owns the Q4 renewal?” Claude follows the edge contact owns deal and names the records it read
Pipeline overview “List all deals in the renewal stage and flag the ones at risk.” list_deals_at_stage, then get_context per deal
Meeting preparation “Prepare me for the call with company X: open deals, latest notes, contact people.” reads company, deals, notes and documents
Follow-up “Summarise the call and save the note on the company.” write_note, versioned and attributed to the agent
Prioritisation “Which three accounts are worth a call this week, and why?” reads the signal records; answers with date and source per signal
Resolve a contradiction “Which lifecycle stage applies to company Y?” both source records with origin and timestamp
Compliance “Which projects hold Art. 9 data, and under which DPA?” filter on the project record

Tool names are examples from the product description; the details may still change during the Alpha.

Prompts and sources for this question

STA-04

What is the design-partner programme?

Twelve companies take part in the Alpha for six months, starting in October 2026. They get direct Slack access to the founder, a monthly co-design session, prioritised feature requests and the right to propose and name one MCP tool that ships to every future customer. In return protagx expects real use with real data and honest feedback; no testimonials, referrals or logos are asked for.

The price is a one-time EUR 6,900 net for the six months. From the seventh month, design partners can continue at the permanent founder rate of EUR 149 net per workspace per month, billed annually. Applying starts with a 15-minute call; applications close in December 2026.

Prompts and sources for this question

STA-05

What does the roadmap look like?

Period Milestone
October 2026 Alpha with the first design partners, weekly releases
Q4 2026 First case studies, stabilised MCP tool surface
Q1 2027 Beta with a waiting list, self-hosting image, HubSpot connector with OAuth
H1 2027 General availability (GA), published standard pricing
Q3 2027 SOC 2 Type II planned

protagx takes questions this FAQ does not answer at hello@protagx.com.

Prompts and sources for this question

Decided1

All 43 questions in the CRM FAQ

¹ Planned for a future release.