Agentic MMM is a marketing mix modeling system that runs its own observe-plan-act-verify loop: the system connects to source data, determines what can be modeled, builds the models, checks its own output against external evidence, and iterates until a measurable stop condition is met. One-shot MMM produces a model in a single pass and leaves a human analyst to find and fix the errors afterward. The distinction is not speed or model quality. The distinction is where verification happens.
Then Cursor and Claude Code arrived, with the ability to run their own code, read their own errors, and iterate until the thing worked. Same underlying model. Completely different experience, because verification moved inside the loop.
AI-powered MMM is sitting exactly where ChatGPT was in 2023.
We keep seeing the same pattern labeled 'AI-powered MMM': hand over a dataset, get back a model, then spend weeks explaining why parts of it are wrong. One-shot MMM: one model, one methodology, no way to check if it's right.
Two cases that could happen in the modeling process:
Both errors are correctable. Both consume a specialist for days. In both cases the human is functioning as the error handler for a system that could have caught its own mistake.
Agentic is not a synonym for "uses an LLM." Agentic describes a specific structure, of observe, plan, act, verify, then loop. This is the same one whether the subject is a coding agent or a modeling agent.
Verification is the entire game. An agent that builds models faster is a convenience. An agent that checks its own model and fixes what it finds is a different category of system.
Model Context Protocol is an open standard that lets an AI agent reach external data sources and tools. MCP is the mechanism that makes observe and act possible at all: through an MCP server, the agent reads source data and calls modeling functions directly, instead of waiting for a human to assemble an extract and paste it into a conversation.
The limit worth naming is that a chat interface is an interface, not a compute environment. Bayesian sampling on a real marketing dataset does not run inside a chat window, and no amount of protocol design changes that. What MCP does is connect the conversation to a platform where the compute actually lives. Intent and results move through the chat. The fitting happens where the hardware is.
That split is why agentic MMM is a platform problem rather than a prompting problem.
Agentic MMM does not make models right. All models are wrong; some are useful. Any vendor claiming their agent produces correct models is selling you something. Verification catches structural and internal-consistency errors. Verification does not catch a badly specified business question, a channel that was never instrumented, or an assumption everyone shares and nobody states.
Agentic MMM does not remove the analyst. Software engineering is the useful comparison: coding agents write a large share of production code, and the engineer remains accountable for what ships. What changed is that engineers stopped spending their days on mechanical error correction and started spending them on judgment. Same shift here. The analyst stops being the person who notices the missing holiday and becomes the person deciding whether the measurement framework answers the question the business is actually asking.
What agentic MMM removes is friction: data collection, cleaning, structural understanding, model construction, and the first several rounds of correction. That friction consumes most of the elapsed time in a modeling engagement and almost none of the expertise.
Four things, and most platforms have none of them.
Against those four requirements:
The category will converge on this. The gap between one-shot and agentic MMM is too large and too visible to survive, in the same way nobody is pasting tracebacks into a chat window anymore.