An Expected Return Is a Forecast, Not a Promise

A forecast that says “+18% expected return” looks precise. The future is not.

That tension is unavoidable in financial products. People need a usable output, but a usable output can become misleading when it is presented without the assumptions, uncertainty, and evidence behind it.

At Artul, an expected-return estimate is a model’s central forecast over a defined period. It is not a guaranteed destination, a price target carved in stone, or a promise that the stock will move in a straight line.

Expected does not mean inevitable

Imagine a range of possible outcomes rather than one number. Some outcomes are positive, some negative, and many cluster around the center. The expected return is a way to summarize that distribution into a decision-friendly estimate.

The realized return can land far from the estimate. New information can arrive. Market conditions can change. An otherwise correct reading of the quarter can be overwhelmed by valuation, rates, regulation, geopolitical events, or a company-specific surprise.

A forecast is valuable because it can be tested, not because it sounds certain.

Why show a number at all?

A purely qualitative label such as “strong quarter” avoids false precision, but it creates a different problem: it is difficult to compare and difficult to score.

A numeric estimate forces the model to express magnitude. Two companies can both receive a positive opinion while having very different expected upside. The number also creates accountability. After the forecast horizon passes, the estimate can be compared with what happened.

The right response to uncertainty is not to hide the number. It is to pair the number with a time horizon, confidence level, and evidence.

Confidence is not the same as upside

Expected return and confidence answer different questions.

Expected return describes the model’s estimated move. Confidence describes the strength and consistency of the evidence supporting the forecast. A company can have a high expected return with modest confidence if the upside case is large but the signals disagree. Another can have a smaller expected return with higher confidence because the call, release, and financials align closely.

Confidence should not be read as “the probability this stock goes up.” It is a model-quality signal, not a literal win rate for one future observation.

Evidence matters more than decimal places

Forecasts often appear more sophisticated when they include extra precision. A target of 17.83% looks scientific. Unless the model can support that degree of accuracy, the decimals are decoration.

We prefer an output that can be traced back to observable markers: demand, guidance, margin behavior, cash generation, management specificity, evasion, stress, and consistency across documents. Those markers give a user something to inspect and challenge.

If the expected return is positive but guidance weakened and margins deteriorated, the user should be able to see why the remaining evidence outweighed those risks. If that explanation is not available, the number asks for trust it has not earned.

How a forecast becomes useful

An expected-return estimate is most useful in four ways:

• Comparison: Rank opportunities using the same horizon and methodology.
• Prioritization: Decide which calls and financials deserve deeper human review.
• Monitoring: Identify the markers that would strengthen or invalidate the view.
• Accountability: Record the forecast before the outcome and score it afterward.

It is least useful when treated as a substitute for portfolio construction. Position size, liquidity, valuation, diversification, taxes, and individual risk tolerance sit outside a single earnings forecast.

What should change the forecast?

A credible forecast has failure conditions. If demand was classified as accelerating, what future evidence would show that classification was wrong? If management said margin pressure was temporary, when should recovery become visible? If guidance was raised, which operating assumptions support it?

Writing those conditions down prevents the forecast from becoming a story that changes after the fact. It also helps separate normal price volatility from evidence that the underlying thesis has weakened.

Publish first, evaluate later

One of the cleanest ways to build trust is to timestamp a forecast before the outcome is known. The record should include the company, opinion, expected return, horizon, confidence, and the evidence available at the time.

After the horizon passes, show the result. Do not highlight only the wins. A forecasting product becomes useful when users can see where it works, where it fails, and whether performance changes across market conditions.

The honest way to read an Artul result

Start with the opinion. Use the expected return to understand magnitude. Use confidence to judge how strongly the evidence aligns. Then inspect the biomarkers and decide whether the underlying explanation makes sense.

The final number is the end of the model’s calculation, but it should be the beginning of the user’s judgment.