SHAPE THE CONTEXT LAYER.
NAME AN MCP TOOL.
The CMP42 Design Partner Program takes twelve companies into six months of Alpha starting October 2026. You get direct access to the founder, a monthly co-design call, priority feature requests, and the right to propose and name one MCP tool that ships to every future customer. We ask for real usage and honest feedback.
TWELVE SLOTS. A REAL ALPHA.
Twelve is deliberate: few enough that every partner gets the founder's attention, enough to cover consultancies, product-led B2B teams, agencies and teams leaving HubSpot. When the twelve slots are filled — or applications close in December 2026 — the next entry point is the Beta waitlist in Q1 2027.
What you get
- Direct-Slack access to the founder throughout the six months. No support tier, no ticket queue.
- Monthly co-design call — one hour, on your roadmap. What you need, in what order, at what depth.
- Priority feature requests. Anything you flag as blocking gets a named next-release slot.
- Name one MCP tool. Propose a tool that fits your workflow. If it fits the platform, we build it and ship it with your naming, to every future customer. What MCP tools are →
- Full Alpha access to the hosted platform, the self-hosted image, and every model / process API surface.
- Lifetime founder rate — whatever we charge at GA, you keep the Design Partner rate as long as you stay.
- Public case study — optional. If you agree, we co-write it. If not, we quietly acknowledge you and never name you without permission.
What we ask
- Real usage. Actual data on our platform, not a demo tenant. If you cannot get authorisation to run a real workload, defer to Beta.
- Weekly feedback loop — a short async note or a 30-min call. Whatever fits your week. Silence for a month is fine; a whole quarter is not.
- Honest defect reports. Alpha ships weekly and things will break. You tell us fast, we fix fast.
- Realistic evaluation. You judge us against the tools you use today, not against SaaS-listing marketing pages.
- Design conversations under NDA — what we build together in the monthly call is not a public specification until we ship it.
- Nothing else. We do not ask for testimonials, referrals, or logos. Those are gifts, not requirements.
FOUR STEPS.
FIFTEEN DAYS.
- 01
Send the form
Twelve fields, no marketing pipeline. Just what you do, why you want CMP42 in it, and what your first named MCP tool would be.
- 02
Fifteen-minute call
We book a 15-minute call within a week. No slide deck, no pitch. We ask three questions, you ask three, and we decide together whether the fit is real.
- 03
Onboarding week
If we both say yes, you get access within seven days. A one-hour onboarding, a shared Slack channel, and a first-model mapping session.
- 04
Alpha, six months
Weekly release cadence, monthly co-design call, priority backlog. At month six we jointly decide: continue at Design Partner rate, or migrate to GA.
APPLY TO BE ONE OF THE FIRST TWELVE.
Send the form and we book the 15-minute call within a week. Your application goes straight to the founder's inbox — no marketing pipeline, no list. If you would rather write freeform, email hello@protagx.com with subject CMP42 Design Partner Application.
FREQUENTLY ASKED.
Is €6,900 the price forever?
€6,900 net is a one-time fee for the six-month Alpha. From month seven Design Partners continue on the lifetime founder rate — €149 net per workspace per month, invoiced annually, on the Managed tier — for as long as the contract runs without interruption. At GA we will publish standard pricing; you will not be moved onto it unless you choose to.
What if we cannot commit to real usage in Alpha?
Then defer to Beta. We prefer a small, honest Alpha over a broad, quiet one. Beta opens Q1 2027 with a waitlist.
Do you self-host?
Yes. Same binary, same models. Runs on your Postgres and object store. The MCP tool surface is identical. We publish the self-hosted image in Beta.
What data leaves our environment?
On the managed EU tier — none, except what you explicitly send to an agent you connect. CMP42 does not train on your data. There are no third-party analytics, no fingerprinting, no session replay. On self-hosted, nothing leaves your environment at all.
Which AI clients does it work with?
Anything MCP-compliant: Claude Desktop, Claude Code, Cursor, Cline, and any custom agent using the MCP SDK. For non-MCP clients we expose REST + GraphQL. The auth model and audit trail are the same across surfaces.
What about compliance?
GDPR-native by construction. AVV / DPA on request. The managed tier runs on Hetzner in the EU (Falkenstein and Nuremberg data centres). SOC 2 Type II is scheduled for GA in Q3 2027; the Alpha runs on the same internal controls but is not yet externally audited.
How is this different from a Notion + Claude workflow?
Notion is documents. CMP42 is typed objects with typed edges. An agent asking "who at Aspen owns Q4 renewal" walks a graph and cites source objects. Notion answers as chat.
What if we drop out of Alpha?
Your slot returns to the pool. Your data is exported to you in a standard format and deleted from our side within 30 days. Your MCP tool remains in the product with your acknowledgement.