DevPartner for real estate developers

Most acquisition decisions in Indian development are made on a spreadsheet nobody can reopen six months later. DevPartner gives an acquisitions team one place to appraise a site, compare structures on the same base, stress the answer and freeze a report the investment committee can actually interrogate.

The problems this is built for

  • Every site is appraised differently. Two analysts, two spreadsheets, two definitions of efficiency and margin — and no way to compare the sites they produced.
  • The committee paper cannot be reopened. The model has moved on; the paper has not.
  • Structures are compared informally. An outright price and an area-share offer are argued about rather than expressed on one implied land cost.
  • Sensitivity is done once, verbally. The committee hears the base case and a reassurance.

The workflow

Acquisition workflow in DevPartner
StageWhat you doWhat you get
IntakeSite facts, planning inputs, product intentA structured opportunity record
CapacityFSI, coverage, efficiency, unit size, parkingBuildable and saleable area, yield, parking demand
CostLine-by-line build-up, not a blended rateA cost base you can defend under challenge
RevenueMix, rate and absorption profileGDV phased over the sales programme
StructureOutright, area share or revenue shareOne comparison on a single cost and revenue base
Cash flowProgramme, drawdown and finance termsPeak funding and finance cost
DecisionYour required return and risk criteriaA traceable verdict with named drivers
ReportFreeze a versionAn immutable document that reopens unchanged

Traceability, not opacity

Every figure in a DevPartner run can be traced back to the input that produced it and the engine version that computed it. Nothing is generated by a language model, and no output appears without an assumption behind it. When a material assumption changes, the run is marked stale rather than silently recalculated underneath a report you have already circulated. The methodology sets this out in full.

Where to start

Take a live site you are already looking at, run it through the free calculators to sanity check the shape, then model it properly in the workspace and freeze a version. If the frozen report tells your committee something the spreadsheet did not, the tool has paid for itself on the first deal.

What to work out next

Frequently asked questions

How is this different from our internal appraisal spreadsheet?
The arithmetic is comparable; the discipline is not. A spreadsheet has no record of which version produced the committee paper, no enforced link between an assumption and the outputs it drives, and no way to tell you that a run is stale because the cost base changed last week. DevPartner records inputs, engine version and outputs per run, and freezes report versions immutably.
Can we appraise several sites and compare them?
Yes. Each opportunity is modelled separately in your workspace, and because every run states its assumptions, you can compare sites knowing whether they were appraised on the same basis — which is usually where cross-site comparisons quietly break down.
Does DevPartner know the planning rules for our city?
No, and it does not pretend to. You enter the planning inputs your consultant or the applicable development control regulation confirms. We would rather be explicit about that than serve a national rules database that is wrong on the street that matters.
Who can see our opportunities?
Only members of your organisation. Records are scoped to your organisation and enforced at the database level, not by hiding buttons in the interface. Documents are private by default.
Can we get a second opinion on a specific deal?
Yes — the expert review add-on is a human review of one opportunity: assumptions challenged, cost base sense-checked, structure compared and the decision stress-tested. It is priced per review and arranged through the contact form.

Take this from a calculator to a decision

A single-page calculator cannot phase a programme, model cash flow, compare structures on one base or freeze a report. DevPartner's deterministic engine does — with every assumption traced back to the value you entered.