Channel partner sites quote prices that no developer has published, and they quote each other. Here is a way to check whether a circulating price range is plausible, using arithmetic on figures the developer itself has disclosed. We ran it on Embassy Astra and the range held up. On some projects it will not.

Why you need a check at all

Most project prices you read were never published by the developer. Builders keep pricing in the sales channel because a stale published price becomes a liability, so the figures circulating online come from somewhere else.

Usually that somewhere is one early channel partner page, which other pages then copy. Within weeks the same number appears on twenty sites and starts to look like consensus.

It might be accurate. It might be a launch-phase figure that has since moved, or an optimistic estimate that was never real. There is no way to tell from repetition, because repetition is not corroboration.

What you want is a number from a different kind of source entirely — one with a different incentive attached to it. For listed developers, that source exists and it is free.

Investor disclosures are written for people who will hold the company to them. That makes them a genuinely independent cross-check on what the sales channel is saying.

The arithmetic, on a real example

Embassy announced a programme of six North Bengaluru residential launches valued at around ₹10,300 Cr in total. Within that, it put one project — Astra, to be named Sky Terraces — at about ₹2,540 Cr estimated revenue across 600-plus residences.

The implied average lands inside the circulating range, a little above its floor. That is exactly where you would expect an average to fall in a mix weighted toward smaller configurations.

So the range passes. It is consistent with what the developer itself expects to earn, which is a much stronger statement than twenty websites agreeing.

How to read the result properly

The check tells you one thing and it is important not to stretch it further than that.

What it tells you: whether the overall price range is consistent with the developer’s own revenue expectation. That is a plausibility test on the range as a whole.

What it does not tell you: the price of any individual configuration. An average across 600 mixed units says nothing about what a specific 3 BHK on the fourteenth floor costs.

There are also real reasons the two figures can diverge legitimately. Revenue guidance may include commercial or retail components. It may be stated at expected realisation rather than launch pricing, which is usually higher. Unit counts may be approximate at announcement.

So treat a close match as reassurance and a large gap as a question rather than a verdict. If the implied average comes out well below the quoted range, ask the sales team to explain the difference. Their answer is informative either way.

What you should never do is use the implied average as a negotiating price. It is not an offer and it was never intended as one.

Where to find the inputs

All of this is public and takes about twenty minutes once you know where to look.

1. Company press releases on the developer’s own site. Launch announcements often carry revenue and unit figures.
2. Quarterly results and investor presentations, for listed developers. These carry project pipelines with values.
3. Stock exchange filings, which are public and dated.
4. Analyst call transcripts, where management is asked direct questions about pricing and absorption.
5. Annual reports, for the longer view on what the company has actually realised against guidance.

The last one is quietly the most useful. A developer that has consistently realised close to its guidance is a developer whose numbers you can lean on. One that routinely falls short is telling you something about how it forecasts.

None of this requires financial expertise. You are looking for two numbers and dividing them.

The limits, and when this will not work

Be clear about where the method runs out, because it does not apply everywhere.

Unlisted developers generally publish nothing comparable. For a private builder with no investor obligations, there is no independent figure to check against, and you are back to the RERA filing and the sanctioned plan as your only hard sources.

Mixed-use projects muddy the arithmetic, because revenue guidance may fold in retail, office or plotted components that are not in the residential unit count.

Multi-phase projects can state revenue for a whole scheme while the unit count you have is for one phase. Match the scope of both figures or the answer means nothing.

And where the developer has simply not disclosed either figure, the method is unavailable. That is not a red flag — most developers do not disclose — it just means you rely on the documents instead.

Which is the right default anyway. This check is a useful extra when it is available, not a substitute for reading the filing.

One extension worth knowing about. The same arithmetic run across a developer’s whole announced pipeline tells you about the segment it is targeting overall — a programme of six projects at ₹10,300 Cr is a different business from six projects at ₹3,000 Cr.

That matters when you are judging whether a developer is used to building at your price point. A company moving upmarket for the first time is a different risk from one that has delivered there repeatedly.

Revenue guidance is an estimate by the company and may include components outside the residential unit count; treat the implied average as a plausibility check rather than a price. Figures above are drawn from published project information and are indicative. Where sources conflicted we have stated both positions rather than picking one. Verify any registration yourself on the Karnataka RERA portal before paying a booking amount.