Building your own expectation before the result

A result is about to be announced. If you have not written down what you expect it to be, then the moment the number prints you have only two things to judge it against: the company's own headline framing, and the way the price is already moving. Both are the wrong ruler. The headline is chosen to flatter, and the price move is a fact about positioning, not about the business. Without a number of your own, you cannot be right about a result — you can only be surprised by it.

This module is the practical core of Part Nine. The previous two modules established that the price reacts to expectations, not results (106), and what "priced in" actually means (107). The response to both is the same discipline: build your own numeric expectation before the result, from the business's real drivers, and then on results day compare the actual against your number and against the street consensus — not against the headline, and not against the falling or rising candle. The estimate does not need to be precise. It needs to exist, and to be written down before you know the answer.

The reason to commit the number to paper before the result is not tidiness — it is that the human mind rewrites its own expectations the instant it sees the outcome. Once you know revenue came in at ₹538 crore, you will feel you "always thought it would be around there," whatever you actually thought. Hindsight quietly edits the estimate to match the result, so the only defence is an estimate fixed in ink before the result exists. This is grading the decision by the process behind it rather than the result — and a written expectation is what makes the process gradable at all: without it, every result feels like something you saw coming, and you learn nothing.

There is a second reason, which reaches back into Part Eight. You do not build the estimate from thin air; you build it from the leading indicators — the volume run-rate, the order book, the occupancy, the AUM — that moved before the result and are observable now. Guidance-versus-delivery (088) taught that management's own guided numbers are checkable against what arrives; here you add your own independent estimate alongside their guidance, so results day tests both. When the actual lands, you learn three things at once: whether the business did what you thought, whether it did what management promised, and whether it did what the street expected. One number, written down first, unlocks all three comparisons.

The method is deliberately simple, because a simple estimate you actually make beats an elaborate one you never finish. Four steps:

• Build the top line from its two drivers. For a manufacturer, revenue is realisation times volume — so estimate the two separately (last quarter's volume adjusted for the leading demand signals; last quarter's realisation adjusted for known price and input moves) and multiply. Estimating them apart is what lets you later see which driver caused the miss or beat, the subject of Module 111.
• Carry a margin band and the key operating metric alongside. Revenue alone is half a result. Add a margin range from your read of costs, and the one operating metric that matters most for this business — utilisation, occupancy, spread — because the market often reacts more to that metric than to the rupees.
• Make it a range, and name the two or three swing factors. Do not force a single point. Set a low and a high, and write the handful of things that would push the number to one end or the other — an input-cost pass-through, an export price, a plant ramp. Those swing factors are what you will actually read the result for.
• Note guidance and consensus beside your number — but build yours first. Write what management guided and what the street expects after you have formed your own view, so their numbers anchor the comparison without anchoring your estimate. Yours is the independent reading; theirs are the benchmarks.

The output is one line you could say aloud before the result: "I expect revenue of ₹500–545 crore, margin around 18–19%, utilisation near 82%; management guided the low end, the street sits at ₹512 crore; the swing is input-cost pass-through and the new line's ramp." That sentence, written down, is the whole apparatus. Everything on results day is now a comparison against it.

The act of estimating is universal; the building blocks are not. This is the module's inversion: the same worksheet is filled from entirely different drivers depending on the sector, and using the wrong pair builds a confident estimate of the wrong thing. For a manufacturer it is volume times realisation. For a lender there is no volume-times-price line at all — earning power is the average book times the interest spread, then the credit-cost charge subtracted, and growth is gated by capital. For a hotel it is occupancy times room rate; for an IT services firm, billed headcount times realisation per employee, adjusted for utilisation. Reach for units-and-price everywhere and you will estimate a bank's revenue from a line that does not exist.

The discipline is identical in every cell — build a range from the drivers, carry a margin and a key metric, name the swings — but which drivers you multiply is set by how the business actually earns. Learn to fill the right pair for the sector in front of you, and the same worksheet travels anywhere.

A composite mid-cap specialty chemicals maker, Meridian Chemicals illustrative, reports next week. [illustrative] You build the number before it does. Volume has run at roughly 10 million units on the leading demand signals; realisation, after a modest price rise and a richer export mix, sits near ₹520 a unit — so revenue lands around ₹520 crore, and you set a range of ₹500–545 crore to hold the swings. Margin you put at 18–19%, and the operating metric you most care about, plant utilisation, near 82%. The swing factors you write down are three: how much input-cost inflation was passed through, the export price and mix, and the ramp of the new line. Management has guided to the low end, about ₹505 crore; the street consensus sits at ₹512 crore. You say the sentence aloud and write it down.

Results day. Revenue prints ₹538 crore, margin 18.6%, utilisation 83%. Now the three-way read, against a number you fixed in ink:

The actual came in above your mid, above guidance and above consensus — a genuine beat, and because you estimated the drivers apart you can even say why: realisation, not volume, ran to the top of your range, so the export price was the swing that mattered. If the stock falls anyway that day, you now know something precise — the business beat your expectation, so the price move belongs to positioning and what was already priced in, not to the result. That is the good-result-that-gets-sold you meet in Module 109. And had revenue printed ₹498 crore, you would have known before any analyst note that this was a real miss against your own range, not merely a soft headline. The written number is what turns the reaction from a verdict into a separate question.

Your expectation tells you whether the business did what you thought. It does not tell you how the price will react — that turns on what was already priced in and how the actual compares to the buy-side whisper, which can sit well above published consensus. A result can beat your number and the street and still fall, and the estimate's job is precisely to let you see that gap clearly, not to close it.

It cannot rescue a wrong model. If you built revenue from the wrong drivers — units-and-price for a lender, reported revenue for a developer whose real activity is pre-sales — a tidy range is confidently wrong, and being inside it means nothing. The estimate is only as good as the drivers underneath it, which is why the sector build matters more than the arithmetic.

And a single quarter's beat or miss against your number is a data point, not a verdict on the business. A reported quarter is noisy; one beat can be timing pulled forward and one miss a shipment slipped to next quarter. The estimate earns its value across many results, as a running check on whether your reading of the drivers keeps matching what the company delivers — not as a single scorecard on one print.

The first and largest error is having no number at all — walking into a result with nothing of your own, so the headline and the price become the expectation by default. This is the trap the whole module exists to close: with no written estimate you cannot beat a result or be beaten by it, you can only be told how to feel about it by the framing and the tape.

The second is letting hindsight rewrite the estimate. The number was in your head but never on paper, so after the result you remember having expected roughly what arrived, and you never discover that your read of the drivers was off. Only ink defeats this; memory always sides with the outcome.

The third is judging the actual against the headline instead of against your number. The company leads with "record revenue," and without your ₹500–545 crore range to hold it against, "record" sounds like a beat when it may be below what the drivers implied and below the street. The headline is designed to be the ruler; your estimate is there to replace it.

The fourth is outsourcing the estimate to guidance or consensus. Taking management's guided number, or the street's, as your expectation feels efficient but reproduces exactly the number you were trying to test the result against. Guidance and consensus are benchmarks to note beside your view, not substitutes for building it — the independent number is the entire point, because it is the only one that can disagree with the crowd and be right.