Forecasting

Where AI can genuinely help budget forecasting and where finance teams still need disciplined modeling, assumptions, and human judgment.

TL;DR for operators EV charging optimization has a small, rude problem: the most important variable is often the one the operator does not know. A plugged-in car may leave in twenty minutes or three hours. That difference determines whether the controller can wait for cheap electricity or must charge immediately like an anxious intern with a deadline. ...

Football is usually explained after the fact. A team “pressed high.” A winger “found space.” A midfield line “lost compactness.” These statements may be accurate, but they arrive with the comforting uselessness of a weather report read after the picnic. The real managerial question is not merely what happened. It is what could have happened if the opponent shifted earlier, if the team protected the half-space, if the attacking line stretched the back four, or if the next pass invited three different futures instead of one. ...

Dashboard work has a familiar little ritual. Someone opens a chart, zooms into the last few points, notices a dip, a rebound, or a suspiciously clean trend line, and then says something that sounds analytical: “Looks like it will continue.” Sometimes that is wisdom. Sometimes it is just a human staring confidently at a squiggle. ...

Data is expensive. Worse, in real scientific and industrial systems, the most useful data is often the data you do not have yet: the failure condition, the rare regime shift, the long-horizon trajectory, the sensor reading after something starts behaving strangely. This is why “just train a larger model” is not always an operating strategy. Sometimes it is only a procurement strategy wearing a lab coat. ...

TL;DR for operators FutureX is less interesting as a leaderboard and more interesting as an operating model for evaluating AI agents that claim to forecast the future. The benchmark runs a live loop: collect future-facing questions from curated web sources, ask agents to predict before the answer exists, wait for resolution, crawl the answer, and score the prior prediction. That matters because most “forecasting” evaluations are either historical backtests with leakage risk or static datasets quietly ageing into trivia. ...

TL;DR for operators Most forecasting teams already have decent numerical forecasters. Their problem is not that ARIMA, ETS, Lag-Llama, Chronos, or internal demand models suddenly forgot how Tuesdays work. The problem is that many important forecast shocks arrive as text: heat-wave notices, maintenance schedules, holiday effects, price caps, promotions, policy changes, store closures, one-off events, and all the other messy little business facts that refuse to fit politely into a clean covariate table. ...

TL;DR for operators Forecasting teams usually ask the same question first: which model should we use? DCATS suggests a more operationally useful question: which related histories should this model learn from? The paper introduces DCATS, a Data-Centric Agent for Time Series, an LLM-agent framework that improves forecasting by selecting auxiliary time series for fine-tuning rather than by designing a new forecasting architecture.1 In the authors’ traffic forecasting study, GPT-4 Turbo reads metadata about nearby or similar California traffic sensors, proposes candidate neighbour sets, lets lightweight forecasting models test those proposals, and then refines the next round using validation error. ...

TL;DR for operators MountainLion is best understood as a crypto research operating system, not a mystical trading lion that eats volatility for breakfast. The paper introduces a multi-modal, multi-agent LLM framework that combines technical analysis, news retrieval, on-chain signals, chart interpretation, price forecasting, GraphRAG-style semantic reasoning, and user feedback into a structured investment-reporting pipeline.1 ...

TL;DR for operators A recent paper, Dependency Network-Based Portfolio Design with Forecasting and VaR Constraints, proposes a portfolio engine that first turns the S&P 500 into a dependency network, then strips that network down to a minimum spanning tree, then selects the five most central stocks, then allocates capital using risk-aware weights, and finally uses ARIMA or neural autoregressive forecasts to decide whether those positions deserve exposure on a given day.1 ...