One of the easiest ways to overestimate a development project's potential revenue is to use property asking prices as if they represent achievable sales values. An apartment listing shows what a seller hopes to receive, not necessarily what a buyer is willing to pay. The difference may appear small when reviewing individual properties, but across an entire development, relying on unachieved asking prices can materially inflate gross development value and make an otherwise marginal project look profitable.
This is particularly important during early-stage feasibility analysis, when developers are collecting market evidence and trying to establish realistic revenue assumptions. Online listings, agent appraisals, advertised rents, and completed transactions all provide different types of information. Treating them as equally reliable can create problems that flow directly into the financial model, residual land value, and acquisition decision.
The issue isn't that asking prices have no value. They can help identify market expectations and competing supply, but they shouldn't automatically become the numbers used to justify a development investment.
Asking Prices and Achieved Prices Tell Different Stories
An asking price represents the amount a seller is seeking, while an achieved price reflects the amount agreed in an actual transaction. That distinction matters because negotiations, market conditions, property condition, incentives, financing arrangements, and the urgency of the seller can all influence the outcome.
Consider a proposed apartment development where nearby properties are advertised at $350 per square foot. Using that figure across the proposed unit mix might produce an attractive revenue forecast, particularly if the development contains a large number of apartments. However, if comparable completed transactions are closer to $315 per square foot, the original assumption may overstate achievable revenue considerably.
RICS guidance on development-property valuation recognizes asking prices as a source of market information, but distinguishes them from stronger transactional evidence. The weight given to different evidence depends on its relevance, reliability, and the transparency of the market.
How Inflated Revenue Assumptions Affect Development Feasibility
Revenue assumptions influence almost every major output in a development feasibility model. When achievable sales prices are overstated, gross development value increases, which can make projected profit, development margin, IRR, and residual land value appear stronger than the underlying market evidence supports.
Imagine a residential project with 100 apartments and an average expected selling price of $300,000 per unit. The resulting gross sales revenue would be $30 million. If the actual achievable price is closer to $280,000, revenue falls to $28 million, creating a $2 million difference before considering any additional costs or financing implications.
That difference can change the acquisition decision. A developer might believe the site supports a higher land price because the model assumes stronger revenue, even though the market may not support the original sales forecast. Homes England's financial viability guidance similarly emphasizes that a development appraisal is only as reliable as the assumptions and inputs used to calculate revenue, costs, finance, land value, and developer profit.
Use Comparable Transactions to Establish Revenue Assumptions
A stronger approach is to build revenue assumptions around completed transactions from genuinely comparable properties. Developers should examine recent sales, location, property type, unit size, specification, floor level, amenities, and the buyer segment being targeted before deciding which evidence belongs in the base case.
The comparison also needs to account for differences between the existing properties and the proposed development. A newly constructed apartment with better amenities may justify a premium over an older building, but that premium should be supported by market evidence rather than simply added because the proposed project is newer.
RICS guidance recommends analyzing development-property transactions using appropriate common units of comparison while considering the factors that influence individual property values. It also recognizes that simple price-per-unit or price-per-area comparisons can overlook important differences between properties.
Asking Prices Still Have a Role in Market Research
Ignoring asking prices completely would also be a mistake. They provide useful information about competing supply, seller expectations, current market positioning, and the pricing developers may encounter when bringing their own units to market.
The important distinction is how that information is used. Asking prices can help establish an upper reference point or identify a potential pricing trend, while completed transactions provide stronger evidence of what buyers have actually paid. Where transaction evidence is limited, agent feedback and current listings can contribute to the analysis, but their limitations should be clearly reflected in the assumptions.
Build Conservative, Base, and Optimistic Revenue Scenarios
Rather than relying on one selling-price assumption, developers should test a range of achievable revenue outcomes. A conservative scenario might use adjusted transaction evidence from competing developments, the base case could reflect the most representative comparable sales, and an optimistic scenario could consider whether the proposed product genuinely supports a premium.
This approach makes the financial implications easier to understand. If the project only meets its required return under the optimistic scenario, the acquisition carries more revenue risk than a single base-case IRR might suggest. Sensitivity analysis is particularly important because residual land value can change significantly when completed development values or construction costs move.
How AI and Feasibility Software Can Help
Reviewing dozens of listings and completed transactions manually can take considerable time, particularly when a development includes multiple unit types or targets several buyer segments. AI-assisted research can help organize market evidence, compare property characteristics, identify pricing patterns, and connect revenue assumptions to the financial model.
Platforms such as Deepblocks connect site analysis, development potential, feasibility studies, and financial projections, while Aprao supports development pro formas, residual land value calculations, and scenario analysis. Feasibilitypro.AI combines market research with editable Excel feasibility models and scenario testing, allowing analysts to examine how changes in sales assumptions affect project returns.
The technology can reduce the time spent collecting and organizing information, but it doesn't remove the need to verify the evidence. Analysts still need to distinguish asking prices from completed transactions, check whether properties are genuinely comparable, and decide whether any assumed premium is commercially defensible.
What Developers Should Check Before Accepting a Revenue Assumption
Before using a selling price in a feasibility model, developers should understand where the number came from, when the evidence was collected, and whether it reflects an actual transaction or an advertised price. They should also check whether the comparison uses consistent measurement standards, particularly when properties are marketed using different combinations of carpet area, built-up area, or gross floor area.
Other important considerations include unit mix, floor level, specification, incentives, sales absorption, and the competitive pipeline. EstateMaster and Northspyre are also worth considering when assessing broader development appraisal and financial-management workflows, although their specific capabilities should be evaluated against the team's revenue-analysis requirements rather than assumed to be identical.
The Revenue Assumption Should Reflect the Market, Not the Advertisement
An asking price can tell you what a seller wants, but it doesn't establish what your development will achieve. Building a feasibility model around advertised prices without checking transaction evidence can inflate gross development value, distort residual land value, and create unrealistic expectations about project returns.
Developers should use asking prices as supporting market intelligence, not as automatic revenue inputs. The stronger approach is to establish achievable prices from relevant transactions, make adjustments for genuine product differences, and test the financial model against alternative revenue scenarios.
The objective isn't to find the highest price the market is advertising. It's to establish a selling price the development can realistically achieve and still deliver the return the investment requires.
Top comments (0)