The seven mistakes first-time developers make

1. Absorption assumed from the target, not the market

The most expensive first-time error is an absorption assumption derived from what the project needs rather than what the catchment has shown. A promoter needs to sell 180 units in 24 months to make the numbers work, so the plan assumes 7.5 units a month — without checking whether comparable inventory in that catchment has ever cleared at that rate.

The error is invisible for a year. By month fourteen the gap is undeniable, finance cost has accumulated, and the response is usually discounting — which converts a timing problem into a margin problem.

The discipline is to build absorption from observed velocity of genuinely comparable inventory, stress it downward meaningfully, and check whether the project still works. If it only works at the optimistic rate, it does not work.

2. Sales treated as a phase that follows construction

Experienced developers involve sales thinking before design. First-time developers frequently complete design and approvals and then ask how to sell it.

By that point the most consequential sales decisions have already been made by people who were not thinking about sales: configuration mix, carpet areas, efficiency, amenity allocation, parking ratio. These cannot be changed, and they largely determine what the project can charge and how quickly it clears.

The remedy is sequencing. Positioning and product strategy belong before the architect is briefed, not after the plans are sanctioned.

3. Maximising saleable area instead of matching demand

A first-time developer with an FSI entitlement instinctively maximises it, on the reasonable-sounding logic that more saleable area is more revenue.

It is only more revenue if it sells. Building 40 units where the catchment absorbs 20 of that configuration per year produces two years of carry on the surplus, and usually a discount to clear it. Building configurations the market does not want in order to consume entitlement is the same error in a different form.

Entitlement is an option, not an obligation. Sometimes the highest-value scheme uses less than the maximum permissible area.

4. Approval timelines budgeted optimistically

Approval processes in Mumbai take longer than first-time developers expect, and the cost of the delay is not only time — it is finance cost on land already acquired, and a launch window that may shift into a worse market.

The practical discipline is to budget approval timelines from what the relevant authority is currently taking on comparable applications, not from the statutory timeline or from an optimistic adviser's estimate, and to build a contingency on top of that. Where the project only works on the fastest plausible approval path, the plan is fragile.

5. No phasing discipline

First-time developers with multi-building projects frequently launch everything at once, because it seems more ambitious and the construction team prefers a single mobilisation.

This maximises peak funding exposure and floods the project's own catchment. It also forfeits the ability to price later phases on evidence. For a first-time developer — who by definition has no track record to reassure the market — phasing has an additional benefit: completing a first phase on time creates the credibility that makes the second phase sell.

6. RERA treated as a registration formality

RERA is not a filing; it is an ongoing set of obligations — quarterly updates, escrow discipline, disclosure accuracy, and constraints on what marketing may claim. First-time developers frequently register and then fail on the continuing obligations, which is visible to any buyer or channel partner who looks and creates avoidable exposure.

The specific trap is marketing. Advertising a project requiring registration before registering it, or publishing renders showing unapproved amenities, or quoting areas without carpet disclosure, are common and easily evidenced breaches. They also damage conversion, because a buyer who discovers a discrepancy stops trusting everything else.

7. Advisers and contractors appointed on price

The final recurring error is selecting the cheapest option for roles where capability determines the outcome: the contractor, the architect, the liaison consultant, the solicitor.

On a first project, these appointments carry more weight than on a tenth, because the developer has no internal capability to compensate for a weak adviser. A cheap contractor who delays by eight months costs far more than the saving. A solicitor who misses a title issue can cost the project.

The corollary is also true: a first-time developer should be willing to pay for capability precisely because they cannot yet supply it themselves.