Prediction Solves the Wrong Problem for Most Business Decisions
A pricing change, a new message, or a product decision rarely fails because a model predicted the wrong number. It fails because the team had no way to state what the model didn't know, and no way to diagnose the miss after the fact.
Prediction and inference answer different questions
Data science spent much of the last decade over-emphasizing prediction-focused machine learning. Algorithms like deep nets and random forests are strong at extracting non-linear patterns from large data sets. That is not the problem.
The problem is that most business questions are not prediction problems. They are causal inference problems: what would happen if we changed the price, the message, or the product, an effect identified by randomized experimental design, not by model structure or priors alone. A model can be excellent at pattern-matching a training set and still have nothing to say about an action the business hasn't taken yet.
Domain knowledge is not optional context, it's model input
A team deciding on price, positioning, or a product change usually already knows something: which variables plausibly relate to which outcomes, what range a parameter should fall into, which segments behave differently. Prediction-focused ML has no slot for that knowledge. It has to relearn structure from data alone, which is part of why it needs so much data to begin with.
An inference-based approach takes the opposite path. It encodes what the team already knows into the structure of the model, then estimates the parts that are uncertain, rather than treating every relationship as equally unknown.
| Prediction-only ML | Inference built for the decision | |
|---|---|---|
| Output | A point estimate or classification | An estimate with an explicit range of plausible values |
| Domain knowledge | Must be relearned from data | Encoded directly into model structure |
| Data requirement | High, to compensate for no prior structure | Lower, because structure is supplied, not learned |
| What ships to leadership | A number | A number and how much to trust it |
Where this already works
A widely cited example is epidemiological forecasting during COVID-19, where researchers modeled the effect of interventions on disease spread and produced explicit uncertainty bounds rather than a single predicted curve (Flaxman et al., Nature). The value wasn't a sharper point prediction. It was a model that encoded epidemiological structure and reported a posterior interval conditional on that structure, in a situation where the data alone were noisy and incomplete; those NPI-effect estimates later proved highly sensitive to model structure and priors, with weak separate identification of individual interventions.
The same shape appears in any setting where the team has strong priors about structure and comparatively sparse or noisy data: polling, planetary detection from telescope signal, and Subconscious's own domain of testing a marketing or product action before it ships.
Where Subconscious applies this to go-to-market decisions
Subconscious's causal action testing builds a structured, discrete-choice-style comparison across pricing, messaging, and product actions, rather than asking a generic model to pattern-match past behavior. The team states the actions under consideration, and the experiment is built to estimate the causal effect of choosing one action over another.
That output is explicit uncertainty framed qualitatively around the estimate. It is not a claim that every study design produces a formal confidence interval; the strength of the uncertainty statement depends on the specific study configuration.
What this does and doesn't replace
Two boundaries keep this framing honest. First, a structured causal experiment is not the same thing as recruited real-human research. Subconscious can test or validate studies with real human participants, and a team can move from a simulated experiment to real-human validation without changing the underlying causal question. Even so, the simulated result and the human-validated result are distinct claims, not interchangeable ones.
Second, audience-graph reach, a person-level graph of the market, is not the same as a recruitable research panel. Scale in the graph describes how broadly a market can be represented; it does not by itself validate any single study's estimate.
The practical difference for a leadership review
When a pricing or positioning decision goes to leadership, the question that actually gets asked is rarely "what does the model predict." It's closer to "how sure are we, and what would change our mind." A model built for inference is built to answer that question directly. A model built only for prediction has to be reverse-engineered into an answer it was never structured to give, usually after the decision has shipped and something has gone wrong.
Before committing budget to an irreversible go-to-market call, it's worth checking whether the model behind it was built to state its own uncertainty, or only to produce a number. See how Subconscious tests actions before they ship.