Start with the label beside the percentage
A stock forecast shows a five-year gain of 60%. Another shows an annualized return of 10%. Which is higher?
You cannot compare the two numbers directly. A 10% annual compound rate produces a five-year gain of about 61.1%, so these forecasts are close on a common scale. The larger printed percentage does not identify the stronger forecast.
AI stock research tools add another complication. A platform may average the annualized returns of several opinions, average their ending values, or combine their quarterly paths. Those operations can produce different answers from the same underlying forecasts. The word "average" needs a definition.
In an original iPulse AI Batch 7 scoring snapshot, Apple's stored five-year price-only gain averaged across forecast voices was 17.60%. The stored mean annualized price-only return was 3.12%. Compounding 3.12% for five years gives approximately 16.60%, rather than 17.60%. Neither number should silently replace the other.
This article explains how to make a comparable forecast worksheet: identify the return basis, convert the horizon, preserve the aggregation method and keep the forecast separate from the outcome. The Apple values are archived research scenarios, not a current recommendation or a record of money earned.
What CAGR converts, and what it cannot tell you
CAGR means compound annual growth rate. For one starting value and one ending value, it expresses the constant annual rate that would connect them over the stated period.
For a horizon of Y years and a cumulative gain G expressed as a decimal, the annual equivalent is:
CAGR = (1 + G)^(1 / Y) - 1
To convert an annual compound rate r back into a cumulative gain:
Cumulative gain = (1 + r)^Y - 1
A hypothetical starting value of 100 growing to 160 over five years has a CAGR of about 9.86%. A constant 10% annual rate grows 100 to about 161.05 over the same period. Multiplying the annual rate by five would give 50%, which misses compounding.
Use decimals inside these equations. A 60% gain becomes 0.60, not 60. Convert the result back to a percentage for display. Keep more precision during calculation than you show in a table.
CAGR smooths the journey between two endpoints. It does not say that the asset rises by that amount every year. A forecast could fall sharply, recover, then reach the same final value as a steadier path. The annual equivalent would match even though the experience, liquidity demands and drawdown risk differ.
Nor does an annual equivalent identify the probability that the forecast occurs. A five-year scenario is a conditional projection. Expressing it as 9.86% per year does not turn it into a deposit rate or a guaranteed return.
Averaging and compounding answer different questions
Consider two hypothetical, equally weighted forecast voices. One projects 0% annual price growth for five years. The other projects 20% annual price growth for five years. Both start from an index value of 100.
The first ends at 100. The second ends at about 248.83. Their average ending value is 174.42, equivalent to a cumulative gain of 74.42%.
Their average annual rate is 10%. If you compound that average rate for five years, the ending value is 161.05, a cumulative gain of 61.05%.
The difference is 13.37 percentage points of cumulative gain. It arises from the order of operations, without any change to the opinions or their weights. Compounding is nonlinear: averaging the inputs before applying the formula generally does not give the same result as applying the formula to each input and then averaging the outputs.
The annual equivalent of the average ending value is approximately 11.77%. That is a third number with a precise meaning. It is the constant annual rate connecting 100 to 174.42, rather than the arithmetic mean of the two voices' annual rates.
Each summary answers a question:
| Summary | Question it answers | Hypothetical result |
|---|---|---|
| Mean of the two annual rates | What is the arithmetic average of their annualized opinions? | 10.00% per year |
| Mean of the two ending gains | What is their average cumulative price projection at year five? | 74.42% over five years |
| Annual equivalent of that mean ending gain | What constant rate connects the shared start to the mean endpoint? | 11.77% per year |
These voices are alternative projections, not two independent investments. Their average is not automatically a probability-weighted expected return. Equal weights are a modeling choice. The calculation also does not establish which voice is more credible.
A research tool should make the chosen summary clear. When the reader needs to reconstruct a displayed endpoint, the annual equivalent of that endpoint is useful. When the reader is studying differences among individual opinions, their annualized returns remain useful diagnostics. Preserve both definitions instead of asking one percentage to perform both jobs.
What the original Batch 7 records show
For this explanation, we queried the governed original Batch 7 quantitative scoring records on 2 October 2026. We selected all active equity rows in the equal-voice mode at the one-year and five-year horizons. We did not filter by bullishness, ranking, return magnitude or the size of an arithmetic difference.
The extract contained 766 unique records: 383 equities at each horizon. The one-year rows used four quarterly steps, and the five-year rows used 20. All four return fields used in the comparison were populated. The snapshot was dated 20 September, used a reference close dated 18 September, and was scored on 21 September 2026.
Apple was chosen as a familiar worked example, rather than because it had the largest difference. Its archived values were:
| Stored return summary | One-year horizon | Five-year horizon |
|---|---|---|
| Mean annualized price-only return | -0.38% | 3.12% |
| Mean cumulative price-only return | -0.38% | 17.60% |
| Dividend-inclusive annual equivalent used in the scoring summary | -0.04% | 3.66% |
| Dividend-inclusive cumulative return | -0.04% | 19.70% |
There are two separate comparisons here. First, the five-year mean annualized price-only value does not reconstruct the mean cumulative price-only value. The annual equivalent of a 17.60% cumulative gain is approximately 3.30%, while the stored mean annualized price-only diagnostic is 3.12%.
Second, the dividend-inclusive cumulative projection is higher than the price-only projection. The difference between 19.70% and 17.60% is 2.10 percentage points over the horizon. That is a modeled dividend contribution under the snapshot's assumptions, not a verified dividend payment or a separately earned yield.
Across all 383 five-year equity records, the stored mean cumulative price-only gain exceeded the gain obtained by compounding the stored mean annualized price-only rate for five years. The difference exceeded one percentage point in 289 records, about 75.5% of the cohort. At the one-year horizon, the two price-only fields matched in the stored data, as the conversion becomes linear over one year.
This is a demonstration of differing summaries, not a test of predictive accuracy. The input values were rounded for storage. The calculation uses those stored values and the stated five-year horizon, rather than rebuilding every raw quarterly path. It does not establish forecast calibration, representative market coverage or the quality of each underlying thesis.
Original Batch 7 equal-voice price-only diagnostics, queried 2 October 2026. Difference equals stored five-year gain minus compounding the stored mean annualized rate for five years. Bars count records in separate difference bands. Rounded forecasts, not observed returns.
Source: iPulse AI · As of 2026-10-02
Original analytical figure from governed iPulse AI scoring records. Exact extraction and calculation retained in the editorial evidence package. Forecasts, not outcomes.
The snapshot also matters. These original quantitative scoring diagnostics are separate from the Engine V7 synthesizer-weighted consensus path. The Batch 7 release explanation describes that distinction. Today's recalculated leaderboard or synthesized narrative can differ from this archived example. A historical record should retain its own date and calculation context.
Keep price return and total return on separate lines
Price return describes the change in the asset's price. Total return also accounts for income under the chosen treatment of dividends or other distributions. A comparison must identify whether that income is reinvested, retained as cash, estimated or already observed.
Imagine one tool shows a price-only forecast and another shows a dividend-inclusive forecast. Converting both to annual rates fixes the horizon mismatch but leaves the income mismatch. The second number may look stronger because it includes something the first deliberately excludes.
For an equity comparison, write down the dividend assumption and whether taxes, fees and currency conversion are included. If the tool cannot support those adjustments, keep that limitation visible. A modeled historical dividend yield is not a promise that a company will maintain its payout.
An income-inclusive forecast also needs a consistent reference price and date. A scenario generated from an older price can imply a different remaining return after the market moves. A newly calculated remaining return does not necessarily mean the research thesis was rewritten.
Use the original snapshot to evaluate what was forecast at generation. Use a clearly dated update to examine the remaining scenario from a later price. Mixing the two can make a static opinion appear to have anticipated information that arrived afterward.
Build a comparison worksheet before comparing ratings
Start with two tools or two forecast views for the same equity. Capture the values below before choosing which looks more attractive.
| Field | What to record | What a mismatch changes |
|---|---|---|
| Reference point | Starting price, currency and price date | The base from which upside is calculated |
| Evidence cutoff | Last included source date and forecast generation date | Which facts the forecast could have used |
| Horizon | End date or duration, with step frequency | The time allowed for the scenario |
| Return basis | Price-only or income-inclusive, with reinvestment assumptions | What the percentage includes |
| Aggregation | Individual voice, mean endpoint, mean CAGR or weighted path | The meaning of the summary |
| Uncertainty | Alternative cases, dispersion, watchpoints and limitations | What a headline leaves unresolved |
| Evaluation record | Original forecast and later observations | Whether a performance claim is testable |
Convert cumulative returns to annual equivalents only after matching the return basis and horizon. Label the converted column "annual equivalent of displayed endpoint." That wording avoids silently presenting it as the tool's original mean CAGR.
If a view reports an average, inspect its formula or methodology. Ask whether weights apply to individual endpoints, annual rates or each quarterly step. Weighted quarterly returns compounded into a path are a different construction from weighted terminal gains. A weight can also express an editorial assessment rather than a calibrated probability.
Then read the substantive case. What operating assumption drives the forecast? What valuation assumption turns that business outcome into an asset price? Which source supports it, and what observable development would weaken it? Comparable arithmetic makes the next question clearer; it cannot answer the investment question alone.
The iPulse AI Consensus Score methodology explains why a ranking score has its own scale and calculation. A score is not a return percentage. Converting a forecast to CAGR does not convert a score into one, and a high score does not establish suitability for a particular investor.
A forecast becomes performance evidence only after observation
A table of projected gains is not a track record. A useful evaluation preserves the original forecast, its reference date and horizon, then compares it with later observations under a disclosed method.
That method needs rules for dividends, corporate actions, missing observations and the comparison benchmark. A claim about a simulated portfolio additionally needs selection rules, weights, rebalance timing, costs and a clear separation between information available then and information known later.
Even a directionally correct call can have a poor path or an inaccurate magnitude. A return arithmetic check is therefore an early interpretation check, not a substitute for outcome evaluation. The Forecast Library introduction describes why preserving dated forecast records matters for that later comparison.
Independent source checking matters too. The joint SEC, NASAA and FINRA investor article on AI-generated investment information, published 25 January 2024, warns that AI output can be inaccurate, outdated or fabricated even when inputs appear credible. It recommends verifying underlying sources. The arithmetic in this article addresses one narrower problem: understanding exactly what a displayed number claims to measure.
Use the percentage to ask a better question
When you open an AI stock forecast, write one sentence before interpreting the number: "This is a [return basis] projection from [reference date] to [horizon], summarized by [aggregation method]."
If you cannot complete that sentence, the percentage is missing context. If you can, convert it onto a comparable scale, inspect the path and assumptions, then preserve the dated record for later evaluation.
For a practical first exercise, open a familiar asset in the iPulse AI asset directory. Compare its individual forecasts with the consensus view and identify the return basis and horizon. The useful result is a forecast you can explain and question, with its uncertainty intact.
