CMP42 // PRODUCT // MODELSMOVEMENT 02 OF 03
// Movement 02 · Models · The schema you can shape

YOUR ONTOLOGY.
VERSIONED LIKE CODE.

CMP42 ships with sensible defaults for the CRM primitives — contact, company, deal, task, activity. Then you extend: in TypeScript-shaped YAML, in git, migrated with a single command, validated at write-time. Your ontology is a first-class product artefact, not a hidden Salesforce setting.

// The problem with hidden schemas

THE SCHEMA IS THE PRODUCT.

In most CRMs the data model lives behind three tabs in an admin settings screen, owned by an ops team you never see. Fields accumulate over years. Nobody remembers which ones are still filled in, which pipeline stage replaced which, or why there are four “industry” fields on a company.

Humans cope with that — they skip what they do not understand. Agents do not. To an agent, every declared field is a claim that the field means something, and every empty one is an invitation to guess. A schema nobody owns is a schema an agent will hallucinate into.

CMP42 treats the model as code. It lives in files, in git, next to everything else your team reviews. Changes are diffs. Migrations are one command. And the agents in production are never surprised by a schema that changed underneath them.

// Refused · No 200 fields on a contact

LEAN DEFAULTS.
EXPLICIT EXTENSION.

Defaults are lean. Extension is explicit. If a field is not on your ontology, it is not on your contact. Silence is a feature.

That is not minimalism for its own sake. For an agent, a field that does not exist is an honest answer; a field that exists but is empty looks like missing data it should fill in. Every field you add should be one you are prepared to define, keep populated and let an agent write to.

So CMP42 starts with the five primitives every CRM needs and nothing else. Anything specific to your business — an engagement, a retainer, a playbook, a renewal date — you declare yourself, where your team can see it.

Default primitiveWhat it stands for
contactA person you work with. Knows a company, owns a deal, authored a doc.
companyAn organisation you work with or sell to.
dealAn opportunity moving through the stages you declare.
taskSomething a human or an agent has to do.
activitySomething that happened — a call, a meeting, a note.

The exact default fields per primitive are finalised during the Alpha, together with the Design Partners.

// How Models work

FOUR PROPERTIES OF A MODEL.

01

Declarative model files

Models are declared in TypeScript-shaped YAML and versioned in git. Review an ontology change like a pull request, see who changed what and when, roll back like any other commit.

02

Validated at write-time

Every write is checked against the model before it lands in the graph. Errors are clear and specific, so an agent that sends the wrong value learns what is allowed and corrects itself instead of inventing a workaround.

03

Backwards-compatible migrations

A single command migrates your models. Migrations are backwards-compatible, so the agents and integrations already running in production do not meet a schema surprise.

04

MCP tools per model

Every model type automatically becomes a set of MCP tools — get_contact, list_deals_at_stage, write_note_on_company — that any MCP-compliant client can consume.

// What a model looks like

A FILE, NOT A SETTINGS PAGE.

The example below illustrates the idea for a boutique consultancy that tracks client engagements. It declares one new model with typed fields and named edges into the default primitives, and adds one optional field to the default deal.

One command applies the change and regenerates the tools agents see. If an agent later writes a value the model does not allow, it gets an error it can act on.

The syntax shown is illustrative. The concrete model format ships with the Alpha and is shaped together with the Design Partners.

models/engagement.yamlIllustrative
# A custom model, declared next to your code
model: Engagement
fields:
  title:       string                         # required
  stage:       "scoping" | "active" | "closed"
  started_on:  date?                          # optional
  budget_eur:  number?
edges:
  client:      -> Company                     # engagement is for a company
  lead:        -> Contact                     # who runs it
  playbook:    -> Doc?                        # the framework it follows

# Extend a default primitive — explicitly
extend: Deal
fields:
  renewal_date: date?
Terminal · migrateIllustrative
$ cmp42 migrate
  + model   Engagement              new
  + field   Deal.renewal_date       optional · backwards-compatible
  ✓ tools   get_engagement, list_engagements_at_stage,
            write_note_on_engagement
  ✓ migration applied
Write rejected · agent self-correctsIllustrative
✕ Engagement.stage
  got:       "in progress"
  expected:  "scoping" | "active" | "closed"
→ retry with stage: "active"   ✓ written · v2
// Migrations

NO SCHEMA SURPRISE IN PRODUCTION.

An agent in production has learned the shape of your data: which tools exist, which fields they take, which values are valid. Change that shape carelessly and the agent does not throw an error you can see — it quietly starts doing the wrong thing.

That is why CMP42 migrations are backwards-compatible. Adding a model, an optional field or a new edge extends what agents can do without breaking what they already do. Identities are content-addressable and stay stable across schema evolution, so references held by an agent or an integration survive a migration.

Because models live in git, the history of your ontology is the history of your repository: every change reviewed, attributable and reversible.

// From model to tools

EVERY MODEL BECOMES TOOLS.

You never hand-write an MCP server for your CRM. When a model is migrated, CMP42 generates the matching tools — for the defaults and for everything you declare yourself. Add Engagement and your agent can ask for engagements, filter them by stage and write notes on them, with inputs typed by the model you wrote.

The same operations are available through REST and GraphQL for clients that do not speak MCP, with the same auth and the same audit trail. See the MCP tool surface →

// Questions on this

What people ask here

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

BAS-04

How are contact, company, lead, deal and activity represented in CMP42?

CMP42 ships with lean standard Models: contact, company, deal, task and activity. They match the basic terms of the glossary. The difference is in the connections: relationships are typed edges. A contact knows a company, owns a deal, authored a document.

In CMP42 a lead is a stage in a contact’s lifecycle, not a separate record that has to be “converted” later. Seven fixed lifecycle stages, the same for every tenant, are planned for the next version: captured, in_qualification, qualified, opportunity, customer, disqualified and transient. Every record is versioned, and every field can be addressed by URI.

Prompts and sources for this question

Decided1
SAL-03

What is the difference between an MQL and an SQL, and how do you model it?

An MQL has shown interest that marketing considers relevant. An SQL has been confirmed by sales as a real sales opportunity. Classic CRMs usually compute the transition with a points score that nobody can explain afterwards.

CMP42 deliberately ships no built-in score and no ready-made MQL. Instead it stores every buying signal as a record of its own, with type, source system and time. What counts as buying intent is set in your Model. When sales asks “Why this lead?”, the agent answers with the specific signals behind it, dated and with their source, rather than with a number.

Prompts and sources for this question

Decided1
SAL-04

How does a sales funnel differ from a sales pipeline?

The funnel is a model: it describes how many people reach each step on the way from first contact to purchase. The pipeline is concrete: it holds the real deals and their current stage.

In CMP42 the deal stages are declared in your Model, and tools such as list_deals_at_stage are generated from them. If an agent sends a stage that does not exist, it gets a clear error and corrects itself instead of inventing a stage. You build the funnel by having the agent count and compare the contacts’ lifecycle stages.

Prompts and sources for this question

Decided1
MKT-04

How do the customer journey and the customer lifecycle differ?

The customer journey describes everything a customer experiences across all touchpoints. The customer lifecycle describes the phases of the relationship, from acquisition to retention.

In CMP42 the journey appears as a sequence of events and signals in the graph, each with its source and time. The lifecycle is a stage on the contact; the plan is for every change of stage to state its reason. An agent can then answer both questions: “What has this customer been through?” and “Where do they stand right now?”

Prompts and sources for this question

Decided1
MKT-06

How does an agent find cross-selling and upselling opportunities?

Cross-selling sells complementary products, upselling a higher-value solution. CMP42 does not deliver ready-made recommendations for either. But the agent can read what it needs for a good recommendation: closed deals and projects, the people involved and their roles, notes on needs and budget.

An example prompt: “Which existing customers bought product A in the last 12 months but never discussed product B? Justify each suggestion.” Before anyone is contacted, the same question applies as everywhere else: may this person be contacted on this channel?

Prompts and sources for this question

Decided1
DAT-01

What are CRM objects, properties and associations called in CMP42?

The concepts stay; the implementation becomes stricter and readable for agents:

Glossary term Classic CRM CMP42
CRM object contacts, companies, deals, custom objects Model, declared in a file, versioned in Git
Property / field a field on a settings page typed field in the Model, validated on write
Association a link, often without meaning typed edge with a meaning (knows, owns, authored) and a validity period
Activity / note an entry on a timeline versioned record with an author (person or agent)

Prompts and sources for this question

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

  • Open - you decide1Funnel metrics over MCP
  • Open - you decide1Customer journey timeline
  • Open - you decide1Products and line items on deals
  • Open - you decide1Frozen audiences

All 43 questions in the CRM FAQ

¹ Planned for a future release.