INNOVATION& | Better Strategic Decisions Under Uncertainty

INNOVATION& | Better Strategic Decisions Under Uncertainty

The AI Model Is Ready When the Next Dollar Has to Prove Itself

Yetvart Artinyan's avatar
Yetvart Artinyan
Jun 25, 2026
∙ Paid

Improving a model is almost always possible. Knowing when to stop is not.

AI research and model learning are not my field of expertise. I am looking at this from an innovator’s perspective: where uncertainty becomes investment, where technical progress turns into resource commitment, and where teams need to decide what is worth improving, testing, scaling, or stopping.

That asymmetry is where most AI investment decisions go wrong. The team asks how good the model can get. The room debates benchmarks, latency, safety scores, and data coverage. Nobody asks whether closing any of those gaps would change the decision they are actually trying to make.

The shift from “how good?” to “good enough for what?” is where AI stops being an engineering problem and becomes a capital allocation problem under uncertainty. Most teams have not made that shift.

INNOVATION& | Better Strategic Decisions Under Uncertainty is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.

The model is not trained on data. It is trained on usable data.

Raw data is not training material. It is exposure until it earns the right to be called input.

Before a dataset can help a model, it has to be acquired, licensed, cleaned, filtered, deduplicated, structured, mixed, and tested. Some of it gets cut because it is low quality. Some because it creates legal risk. Some because it teaches patterns the provider does not want in the product.

Sambasivan et al. studied 53 AI practitioners across high-stakes domains including healthcare and conservation and found that data quality failures caused compounding downstream failures they called “data cascades.” [1] The AI community’s tendency to prioritize model work over data work was the root cause. Most practitioners had assumed the problem was somewhere else in the system.

A foundation model learns from predicting structure in language, not from labeled examples. A domain model needs expert annotation. A safety layer needs adversarial inputs. An enterprise deployment needs evaluation sets that reflect actual customer workflows, not benchmark tasks nobody’s users encounter.

The economic unit is not “the model.” It is the whole system required to make a model usable in a specific market, with specific buyers, in a specific risk environment.

User's avatar

Continue reading this post for free, courtesy of Yetvart Artinyan.

Or purchase a paid subscription.
© 2026 Yetvart Artinyan · Privacy ∙ Terms ∙ Collection notice
Start your SubstackGet the app
Substack is the home for great culture