Two Sets of Data,Two Ways to Buy AI
Page one is the rule, the question, how to sort the work and what to do. The rest is the evidence and the vocabulary for the conversation with your CIO.
The rule
Where little changes, there is little continuing adaptation to pay for. Where the underlying conditions change, someone has to own keeping the forecast useful, and the contract should say who.
Before the vendor conversation, ask: what changes in this workload, and who is responsible for keeping the result useful?
Stable work
Your team builds and owns it.
Changing work
Someone owns keeping performance current. By default, buy that responsibility from a vendor. Your own team is the alternative.
These are defaults. Test them against performance, lifecycle cost and capability.
The question
How should a company buy AI for analytical and forecasting work? Spending is climbing even as the cost of comparable model capabilities falls: enterprise large language model (LLM) spending tripled over the 12 months to the end of 2025, according to data McKinsey cites. Contracts have not kept pace. In a survey of 202 senior enterprise leaders, 65% of buyers still pay for services on FTE (full-time equivalent) terms: the price follows the headcount assigned, even as AI takes on more of the work. A CEO approving AI spend meets two kinds of contract, one priced by headcount and one by subscription or usage, and needs a way to tell which fits which workload.
How to sort the work
Start by sorting analytical AI workloads by how fast their inputs, definitions and predictive relationships change. This paper covers analytical and forecasting work, not every use of AI, such as drafting, coding assistants or image generation.
Most organizations have both kinds of analytical work. One looks back at a defined record: historical data and the analytics built on it. The other predicts outcomes whose inputs or relationships keep changing, driven by market inputs: sales, demand forecasting, and similar. These are workload categories, not permanent labels for datasets.
| Stable, historical work | Market-driven, changing work | |
|---|---|---|
| The question | What happened, and why? | What is likely to happen next? |
| What it is | Reproducible analytical pipeline or validated model, revisited when records, definitions, questions or performance change | Forecasting model supplied with fresh inputs and monitored for changing performance |
| Default | Your team builds and owns it | A vendor takes responsibility for keeping performance current |
| Alternative | Buy a service when its performance and lifecycle cost justify it | Your own team monitors, recalibrates and retrains it |
| Staffing parallel | Permanent employees: long-term, predictable demand | Contractors: unpredictable, immediate, short-term needs, usually at higher rates |
What to do
- List your analytical AI workloads. Mark each one by whether its inputs, definitions or predictive relationships change. Historical claims work whose coding rules or payer terms change needs revalidation. Put it in the changing column when those changes alter the analysis.
- For the stable ones, start with a reproducible analytical pipeline your team controls. Add a model only where the question requires one. Revisit the work when records, definitions, questions or performance change.
- For the market-driven ones, decide who is responsible for keeping performance current, a vendor or your own team, and name an owner for watching its accuracy.
- Match the pricing to what you are buying: people (FTE) when you need continuing human capacity, access (subscription), usage (consumption), or a managed result. Decide separately where it runs: on-premises or cloud. Finance sets the accounting from the arrangement.
Where each leader meets it
| Leader | Industry | Stable: built and owned, revisited when needed | Dynamic: performance kept current |
|---|---|---|---|
| CEO | Healthcare | Five-year view of which service lines and payers made or lost money | Patient volume outlook behind the guidance to the board |
| CEO | Retail | Five-year view of which categories and stores made or lost money | Next-quarter demand outlook behind the guidance to the board |
| CFO | Healthcare | Historical cost-of-care and claims analysis | Rolling revenue and cash forecast tied to patient volume |
| CFO | Retail | Historical margin analysis by item and store | Rolling revenue and cash forecast tied to sales |
| COO | Healthcare | Historical length-of-stay and throughput analysis | Staffing plan driven by the emergency department volume forecast |
| COO | Retail | Historical supplier delivery and shrink analysis | Inventory and replenishment plan driven by the item demand forecast |
Why the split holds
A demand forecasting model learns patterns from past data, and those patterns can stop holding when consumer behavior shifts. A model that is off on demand throws off inventory planning, and the error carries through the supply chain. A January 2026 preprint describes scheduled retraining every three to six months as common practice in supply chain forecasting.
For historical and semi-static data, established methods often do a great job, and some questions need no model at all, only calculations and attribution. Where a model is needed, a 2022 benchmark across 45 tabular datasets found tree-based models such as XGBoost state of the art on medium-sized data, about 10,000 samples in the authors' benchmark. That supports testing established methods first. It says nothing about how often to refresh. Old model weights do not by themselves establish a security vulnerability, and accuracy drift is a different problem from security. But attacks can target the model itself, through poisoning, evasion or model extraction, so the model and the software around it need an owner and controls.
Infrastructure and staffing follow the same logic. Steady, high-utilization workloads can favor owned capacity, while variable or lower-volume workloads can favor consumption-based cloud pricing. Ongoing, predictable demand goes to core headcount, and contingent labor meets temporary needs. Internal ownership usually means people on payroll and capacity you control, whether on-premises or in your own cloud account. Those are implementation choices, not consequences of the rule. Token spending can build capability, run internal work or serve customers. Finance decides what qualifies for capitalization and, when costs are expensed, whether they belong in cost of goods sold. The accounting follows the use, the arrangement and the applicable standards, not the tier.
Some say FTE pricing makes no sense in an AI-led world. In my view that is not quite the case. Buyers expect FTE-based pricing to shrink sharply, and shrinking is not gone. Headcount is a poor unit when AI takes on more of the work. It can still fit when you need continuing human capacity.
Words worth recognizing
- Analytical pipeline
- Reproducible calculations and attribution, using SQL, statistics or BI (business intelligence) tools, that answer a retrospective question without a learned model.
- scikit-learn
- A general-purpose machine-learning library for building and evaluating models.
- XGBoost and LightGBM
- Gradient boosting for structured, tabular data.
- statsmodels and Prophet
- Classical statistical forecasting. Prophet, from Facebook, handles seasonality and holiday effects and is now maintained mainly for fixes.
- skforecast
- Turns any scikit-learn-compatible model into a forecaster, with backtesting built in.
- Chronos (Amazon) and TimesFM (Google)
- Pretrained forecasting models that can forecast a supplied series without task-specific training on it.
- Language models as forecasters
- The TimesFM authors found time-series-only models beat them at lower cost. A 2025 study found text models competitive in some cases, so test on your own data.
Who sells general-purpose language models, as of October 2026
Model names turn over quickly: OpenAI released GPT-6 Sol and Luna on September 22 and GPT-6.1 Sol a week later. Having the newest general-purpose model is not the same as keeping a business forecast current. Many buyers access these models as a service rather than owning the weights. This is a dated list of families, not a catalog or a forecast-buying guide. Language models, time-series models and statistical tools are different categories, so test which one performs the task, and ask your CIO which version is current.
| Company | Model family | How you get it |
|---|---|---|
| OpenAI | GPT | Service; also open-weight gpt-oss models |
| Gemini | Service; also open-weight Gemma | |
| Anthropic | Claude | Service |
| Meta | Muse (earlier Llama) | Service and open weights |
| Mistral AI | Mistral | Service and open-weight models |
| xAI | Grok | Service |
| Alibaba | Qwen | Cloud service and open weights |
| DeepSeek | DeepSeek | API and open weights |
| Nvidia | Nemotron | Open-weight models; also supplies GPU infrastructure |
Questions that start the conversation
- CEO to CIOWhich of our AI workloads run on market-driven data, and which on historical data? For the historical ones, did we build the analysis once, or do we pay a recurring fee for something that does not change?
- CIO to the teamDoes each task need machine learning, or would a reproducible analytical pipeline do it? Where we use models, which tools do we use: scikit-learn, XGBoost, LightGBM, statsmodels or Prophet? What is the retraining interval on each market-driven model, who decides, and who owns watching its accuracy? Who owns the model and the software around it, and its controls?
- CFO to CIOWhat exactly are we buying: people, software access, usage or a managed result? What does the lifecycle cost include?
- COO with the CEO and CIOWhich operations depend on a model that can go stale, and what happens to them when it does?
How it looks in two industries
Retail
Historical store and product margin analysis asks which items and locations made or lost money. The question is retrospective, so start with a reproducible analytical pipeline your team controls, and add a model only where the question requires one. Revisit it when records, definitions or questions change.
The demand forecast for each item is different. Promotions, consumer preferences and supply disruptions keep shifting demand patterns, so someone must own keeping its performance current and watching its accuracy. A vendor can take that on as a service, billed for what you use, or your own team can monitor and retrain it.
Healthcare
Historical claims and cost-of-care analysis works the same way: a controlled, reproducible analysis, revisited when coding rules or payer terms change the question.
The emergency department volume forecast behind staffing is different. In a study of four hospital sites, mean absolute percentage error, averaged across four forecasting methods, was 3.88% in the 23 months before COVID-19, rose to 15.21% during the authors' 25-month pandemic study period, and fell to 6.45% in the following 14 months, still above where it started. The methods were Excel's exponential-smoothing function and Holt-Winters, not the newest AI model. A disruption weakened a forecast that had worked. The forecast can be built or bought. Someone on your team has to own detecting that and responding.
A note on this paper
This is a decision framework, built from stated assumptions and the evidence I could find. It is not a tested result. The citations support its parts, not the whole. Two assumptions carry it: stable work offers less reason to pay for continuing adaptation, and changing work creates a maintenance burden a service can take on. The staffing parallel is an analogy, not evidence for the rule. If I have misstated something, or you know a case where the rule breaks, please tell me at nandeep@svaglabs.com. I would rather correct it than leave it standing.
Citations
The question. Enterprise LLM spending: McKinsey, "Is that AI agent worth it? Agentic economics and the modern operating model". FTE-based pricing share, a finding about enterprise services: Firstsource, research report.
Why the split holds. Model drift and inventory planning: TDWI, "Concept Drift: When the World Changes and Your AI Doesn't Know"; element61, "Concept Drift: What Is It and How To Address It?". Scheduled retraining: Alam, Rahman and Sadeqa, "DriftGuard," January 2026 preprint. Tree-based models on tabular data: Grinsztajn, Oyallon and Varoquaux, NeurIPS 2022. Attacks on models themselves, which is all this source supports and it does not address model age: NIST AI 100-2 E2025, "Adversarial Machine Learning: A Taxonomy and Terminology of Attacks and Mitigations". Owned versus consumption-based capacity: Deloitte, "AI tokenomics: A CFO's guide to governing the AI P&L"; Deloitte, "The future of enterprise IT: tokenomics insights for the CTO". Token spending by use (capability, internal operations, customer delivery), a management framework and not accounting criteria: BCG, "Return on AI: How CFOs and CIOs Can Manage the Token Meter"; BCG, "How CEOs Can Optimize AI Token Costs". Core versus contingent workforce: Programmed, "Workforce Segmentation"; Draup, "Contingent Workforce".
Words worth recognizing. skforecast on PyPI; Handbook AI, "Demand forecasting methods and implementation in Python"; Prophet repository and package page; Ansari et al., "Chronos"; Das et al., "A decoder-only foundation model for time-series forecasting"; "Zero Shot Time Series Forecasting: Do Time Series FMs Outperform Cross Modal FMs?", NeurIPS 2025 workshop.
Who sells the models. OpenAI: "GPT-6 Astra: A new generation of intelligence," which lists the September 22 and September 29 updates. Google: "The latest AI news we announced in September 2026"; innfactory. Anthropic: The New Stack, "Anthropic launches Haiku 5.5 at a much lower price". Meta: Wikipedia, "Llama (language model)"; innfactory; gradually.ai. Mistral: Wikipedia; BenchLM. xAI: AI Toolbox. Alibaba and DeepSeek: Wikipedia, "Qwen"; Wikipedia, "DeepSeek (chatbot)"; Slash Digital. Nvidia: Layer3 Labs.
How it looks in two industries. Retail demand drift: DriftGuard, above. Emergency department forecasting: Napoli et al., "The Accuracy of Predictive Analytics in Forecasting Emergency Department Volume Before and After Onset of COVID-19," Western Journal of Emergency Medicine, December 2023.