When a cost changes with the inputs, should the number or the assumptions lead the UI?

I am working on a small XAUUSD overnight-cost calculator, and the difficult part is not the arithmetic. It is making the result hard to misread.

The cost can change with position direction, volume, account conditions, and holding time. A large result card is easy to scan, but it can make the number look universal when it only applies to the current inputs.

The interface I am testing keeps the selected conditions beside the result and frames it as an estimate, not a decision or market view.

For builders of pricing, health, finance, shipping, or other input-dependent tools: what do you put next to a variable result so people understand its limits without turning the screen into a wall of caveats?

Do you lead with the result, lead with the assumptions, or reveal them in stages?