Selling Before Building: The Real Estate Developer's Project P&L in PMWEB

For a real estate developer, profit is not earned on site. It is created when units are sold, recognised as construction milestones are achieved, and turned into cash only when the escrow account releases funds. A PMO that reports construction cost alone sees half of the developer's P&L.

Part 1 of this series showed how PMWEB holds both sides of the project ledger. This article applies that model to the real estate developer selling villas, apartments and offices, often off-plan, in the UAE and Saudi Arabia.

The developer's question is not only whether the tower will be finished on time and on budget. It is whether the development will still deliver the profit approved in the feasibility study, and whether the cash from buyers will arrive when the contractor needs to be paid.

How a developer earns revenue

• Sales of assets. Revenue comes from Sale and Purchase Agreements (SPAs) for villas, apartments, offices and retail units. The value sold is fixed at signing; the value of unsold inventory depends on future prices. • Milestone-linked payment plans. Buyers pay a booking amount and then instalments that fall due when construction reaches defined stages, for example 20%, 40% and 70% complete, with the balance on handover. • Escrow accounts. In off-plan markets such as Dubai and Saudi Arabia, buyer payments are deposited in a project escrow account and released to the developer against construction progress certified by the project consultant. • Revenue recognition. Under IFRS 15, developers in the region commonly recognise revenue on sold off-plan units over time, in line with construction progress. Each company should confirm its own policy with its auditors. Construction progress therefore drives three lines of the developer's P&L at once: the cost incurred, the revenue recognised, and the cash released from escrow. That is why the developer's PMO, and not only its finance team, must own the project P&L.

The developer's P&L in five lines

The sales system remains the record of each buyer and each SPA. PMWEB does not need to hold 500 individual sales contracts to report the P&L. It needs sold value, unsold inventory, instalments called and collections by project and unit type, refreshed through the integration, next to the cost data it already holds.

Construction milestones: the hinge of the developer P&L

In a developer's P&L, a construction milestone is a financial event. When the consultant certifies that the structure has reached 70% complete, three things should happen: the instalment linked to that stage is called from buyers, revenue on sold units is recognised to that level, and an escrow release request can be raised with the evidence.

PMWEB holds that evidence: the schedule milestone, the contractor's progress invoice certified by the consultant, site progress photos and inspection records. An escrow release request configured as a PMWEB adaptive form, with its own workflow under the Delegation of Authority (DoA), can carry those records to the bank and to the authority.

Where the cost comes from: the PMWEB processes behind the P&L

The cost side of the developer's P&L is Total Development Cost, and it goes well beyond the main construction contract. PMWEB captures each part through a defined process, starting from the budget:

When the budget is the starting point and every record is coded to it, the PMO can compare each cost line with the feasibility study and show exactly where development profit is moving.

A real-time P&L: accruals ahead of the financial close

The finance team closes the development P&L monthly or quarterly. PMWEB accruals add certified progress and work in place since the last close, so the developer sees today's position. For D2000, against the June quarter close:

Between closes, the board can see how far revenue recognition, escrow eligibility and cost have moved, instead of waiting for the next quarter's accounts.

Potential change orders: claims, disputes and the P&L range

A developer's P&L is also exposed to changes that are not yet settled. PMWEB PCOs record them on both sides. On the revenue side, they capture buyer-requested upgrades and SPA variations, and back-charges and delay damages the developer expects to recover from its contractor. On the commitment side, they capture contractor and consultant claims against the developer. For D2000:

Holding both sides in PMWEB lets the PMO report the P&L as a range, not a single number:

The developer's PMO can show the board how much of the feasibility margin depends on claims still open, and decide which to settle before handover.

The dashboard below is built in PMWEB's embedded Power BI reporting. It uses a sample residential tower, with values in AED millions.

Development Project P&L dashboard in PMWEB: D2000, Creek Vista Residences (sample data, AED millions)

• Sales are ahead of construction. 362 of 504 units are sold (72%), while construction is 54% complete. Sold value is 912.4. • Profit is eroding from two directions. Forecast development profit is 268.5, a 21.7% margin against 24.8% in the feasibility study. The construction overrun (18.5) and expected discounts on unsold units (15.5) explain 34.0 of the 41.5 lost. • Buyers are paying late. Instalments called total 456.1 but 410.6 has been collected, leaving 45.5 overdue, mostly on instalments 3 and 4. • Cash is sitting in escrow. 92.4 is held in escrow awaiting the next certified milestone. Released funds (318.2) already exceed the contractor's payments to date (296.0). • The unsold stock is the large units. 66 of the 124 available units are two- and three-bedroom apartments. That is a pricing and marketing decision, and it sits in the P&L as the discount line.

At portfolio level, the same measures roll up across every development, city and country.

Development Portfolio P&L dashboard in PMWEB: seven developments in the UAE and KSA (sample data, AED millions)

• The portfolio is below feasibility. Forecast GDV is 7,981.4 and forecast development profit 1,703.8, a 21.3% margin against a weighted feasibility margin of 23.5%. • One development is building ahead of its sales. The Downtown Office Tower (D2020) is 63% built but only 41% sold, and its margin has fallen from 19.0% to 14.1%. The decision is whether to slow construction, reprice, or hold part of the building for leasing. • 541.9 is held in escrow across the portfolio. It is cash the developer has sold but cannot use until milestones are certified, with 133.6 in Palm Grove Villas (D2010) alone. • Early-stage projects carry the most exposure. Jeddah Waterfront Villas (D2050) is 52% sold at 27% built: sales are healthy, but most of the cost is still to come.

Integration: sales, cost and escrow in one view

Three systems feed the developer's P&L. The sales or CRM system holds units, SPAs, payment plans and buyer collections. The ERP holds the general ledger, payables, finance costs and payments. PMWEB holds the budget, commitments, invoices, timesheets, change orders, progress certification and escrow release requests. PMWEB's REST and SOAP APIs bring sales and collections in, exchange cost transactions and payments with the ERP, and report the development P&L from one database.

Reporting to investors and lenders

Real estate developments are often funded by equity investors, joint-venture partners and funds, alongside bank finance. Investors want to know whether the return they were promised is still on track. A real-time development P&L lets the developer answer with evidence instead of a quarterly narrative. For D2000:

Every external view is drawn from the same approved records the PMO uses, so it is consistent and audit-ready. PMWEB security settings give each party a read-only view of only the projects and measures it is entitled to see, through a role-based login or scheduled report distribution. For a developer raising capital for its next project, a track record of transparent, real-time reporting is itself an advantage.

PMWEB 2026 AI on development P&L data

Action is taken only with the user's approval, and PMWEB AI honours security settings, so sales, finance and project users each see only what their role permits.

What the developer's PMO must put in place

• The feasibility study as the budget. Every cost line in PMWEB traces back to the approved feasibility. • One unit and CBS structure shared by the sales system, PMWEB and the ERP, so sales and cost meet at building and unit-type level. • Milestones treated as financial events, with certification evidence held in PMWEB and escrow requests raised from it. • All cost in one place: commitments, miscellaneous invoices, timesheets and accruals, not only the main contract. • A monthly development P&L review comparing sales pace with construction pace, and margin with feasibility.

Key takeaway

A developer's profit is set by sales, recognised by construction progress and released by escrow. PMWEB connects all three to the full Total Development Cost, so the PMO can show the board whether each development is still delivering its feasibility margin, and when its cash will arrive.

Over to you: does your development P&L link construction milestones to buyer instalments and escrow releases, or are they reported by different teams in different systems?

Next in the series: Part 3, The Government Entity: Cost Against Deliverables.