YOUR FRAMEWORK.
AS CONTEXT.
Your competitive advantage lives in the framework you keep re-explaining. CMP42 makes that framework the context an agent uses on the next engagement — not a slide you drag into every deck.
THE METHOD LIVES IN PEOPLE.
A boutique sells structured judgement: a diagnostic, a maturity model, a particular way of running a workshop. Yet that structure usually lives in slide masters, in the partners' heads and in a folder of past proposals. Every new engagement starts with someone re-explaining it.
AI has not fixed this — it has made it more visible. When a partner drafts the follow-up after a client call today, it is often Claude with a pasted transcript and a request to "make it sound like me". The draft is fluent. But the agent does not know your framework, the client's history or what was agreed in the last steering meeting, so it fills the gaps with plausible generalities.
The CRM does not help either. It holds contacts and a deal value. The knowledge that actually wins the next engagement sits somewhere else, in a format no agent can reliably read.
METHOD. HISTORY. REVIEW.
Your framework as context
Declare the building blocks of your method as Models — phases, diagnostic dimensions, deliverable types — in git-versioned, TypeScript-shaped YAML. Change the method, migrate with one command.
Every model becomes MCP tools automatically, so an agent can read your framework the same way it reads a contact.
Engagement history in one graph
Clients, stakeholders, engagements, workshops, proposals and meeting notes live in one Context graph with typed edges: a partner authored a document, a contact knows a company, an engagement applies a framework.
Every object is versioned; every answer can cite the objects it came from.
Case notes reviewed by partners
A Process lets an agent draft the case note and a partner review it before it counts. Approval hooks put the human step where you want it.
Each transition is logged, each run is replayable, and each write records whether an agent or a partner produced it — including the token cost of the run.
VERSION YOUR METHOD LIKE CODE.
Your ontology is a first-class product artefact — not a setting behind three tabs, and not a slide master only one partner can edit. The sketch on the right illustrates the idea: an engagement linked to the client, the lead partner, the framework it applies and the documents it produced.
Models are validated at write-time. If an agent tries to file a note against a phase your framework does not have, it gets a clear error and can correct itself, instead of silently inventing a new phase.
The syntax shown is illustrative and will be shaped with the Design Partners during Alpha. How Models work →
# illustrative — the idea, not the final syntax
engagement:
fields:
title: string
phase: enum[diagnose, design, deliver, review]
edges:
for: company # the client
led_by: contact # the lead partner
applies: framework # your method, versioned in git
produced: doc[] # decks, case notes, reports
# generated for agents, in the style of
# get_contact · write_note_on_companyAFTER THE STEERING MEETING.
A case note that knows the engagement
A fictional boutique advising mid-sized manufacturers on operations. The steps show how the concepts fit together — it is not a customer story, and details of the interface will change during Alpha.
- After the steering call, the lead partner asks her agent in Claude Desktop to draft the case note for the client.
- The agent reads the engagement through MCP: the client, the stakeholders on the call, the framework phase the project is in, the last two approved notes and the current proposal — each an object with a URI it can cite.
- It drafts the note in the structure of your framework, assigns each finding to a diagnostic dimension, and lists the source objects it relied on.
- A Process step routes the draft to the partner. She rewrites two sentences and approves. The write is attributed: drafted by the agent, approved by a human.
- Months later, a colleague staffing a similar engagement asks an agent how the framework was applied last time — and gets an answer grounded in approved notes rather than in someone’s memory.
YOUR METHOD STAYS YOURS.
Consultancies are rightly careful about where client knowledge goes. CMP42 is designed so that the framework, the history and the review trail remain under your control — and so that the model you use is your firm's decision, not ours.
Bring your framework to the call
Design Partners can propose and name one MCP tool that ships to every future customer. For a consultancy, that is often a tool shaped around the method itself. Strong applicants describe a real one.
→ Apply to be a Design Partner- The framework is yours — declared in your Models, versioned in your repository.
- Bring the model your firm trusts. CMP42 provides grounded context; your agent produces the insight.
- Managed in the EU or self-hosted. On the managed tier CMP42 does not train on your data; self-hosted, nothing leaves your environment. AVV / DPA on request.
- Every agent write is attributable and can be reviewed by a partner before it counts.
- No new interface to adopt. Your team keeps working in Claude, ChatGPT or Slack.