Property Development Feasibility Software: Why the Committee Approved a Proforma Nobody Can Rebuild

Why development appraisal breaks on spreadsheets and on packaged tools

A land opportunity comes in on Monday with bids due Friday. The development manager copies the last similar appraisal, changes the site area, adjusts the unit mix, updates the build cost rate from a quantity surveyor's email, and produces a residual land value by Wednesday. The investment committee sees version 4. Two weeks later the affordable housing requirement moves from 25 to 35 percent, the scheme drops eleven private units, and the model gets rebuilt. Six months on, someone asks what land value the committee actually approved and against what assumptions, and the honest answer is that the file is called appraisal_final_v7_REVISED and the tab holding the debt calculation has a hardcoded number in it that nobody remembers typing.

The tool landscape is real and each part is competent. Altus ARGUS Developer is the established appraisal engine and has been for a long time. Feasly does cloud-based development cashflow modelling well and solves the version problem better than Excel does. TestFit is genuinely impressive at massing and yield studies, turning a parcel and a set of constraints into a physical scheme fast. What none of them provides is the thing a developer actually needs: one place where the physical scheme, the appraisal, the finance structure, the approval decision, and the live project cost all reference each other and stay reconciled as reality moves.

Problem 1: residual land value is only as good as its conventions, and yours are undocumented

Residual valuation is not complicated arithmetic. It is gross development value, less construction, less professional fees, less finance, less profit requirement, giving what you can pay for the land. The difficulty is that every input carries convention: whether contingency sits on construction only or on the whole cost base, whether finance is calculated on a rolled-up facility or on a monthly balance, whether the profit requirement is on cost or on GDV, whether land acquisition costs and taxes sit inside or outside the residual, whether sales fees are taken off GDV before or after the profit test.

Two analysts using the same inputs and different conventions will produce land values that differ by a margin large enough to lose or win a bid. In a spreadsheet culture those conventions live in whichever file got copied. ARGUS Developer imposes consistency, which is precisely its value, but it imposes its conventions and its structure, and developers with unusual land structures or non-standard product types spend their energy fighting the model rather than using it.

What a custom build does: make the convention explicit, named, and versioned as a house appraisal standard, then apply it identically to every scheme. The appraisal engine computes the residual and shows the derivation line by line with the convention cited. Analysts can still run an alternative convention deliberately, and the output labels it. This sounds like housekeeping and it is the single highest-return decision in the build, because it means two schemes from two teams are actually comparable, and because the committee stops arguing about method and starts arguing about assumptions, which is the argument worth having.

Problem 2: scheme variants and phasing are the analysis, not an afterthought

Real decisions are comparative. Build 180 apartments or 140 apartments plus 24 townhouses. Deliver in one phase or three. Sell the commercial ground floor or hold it. Build to rent the second block. Each variant changes GDV, build cost, programme, sales absorption, finance profile, and the planning risk profile, and they interact: phasing changes peak debt, which changes finance cost, which changes the residual.

What a custom build does: one opportunity, shared assumption set, explicit variants that override only what differs. Change the cost rate once and every variant updates. The comparison view puts residual land value, profit on cost, peak equity, peak debt, and programme side by side, which is exactly the table the committee wants and never quite gets. Phasing is modelled as real timing on the cashflow rather than as an average, because peak equity is what actually constrains a developer's ability to run three schemes at once, and an appraisal that reports profit without reporting peak equity is answering half the question.

This is also where a TestFit-style massing input is genuinely useful rather than decorative. If the physical yield study feeds unit counts and areas directly into the appraisal, the loop from scheme change to land value takes minutes instead of a day, and the team tests ten configurations instead of three.

Problem 3: land payment and profit share structures are where deals actually get made

The headline land price is often the least interesting part of the deal. What matters is a deferred payment on planning consent, an overage clause paying the landowner a share of value above a threshold, a land equalisation arrangement across multiple owners, a subject-to-planning condition with a long stop date, a joint venture where the landowner takes equity instead of cash, or a profit share with a preferred return and a promote.

Generic appraisal models treat land as a payment at day zero, and every one of the structures above then gets approximated with a manual adjustment. That approximation is precisely where value is created and destroyed, because a deferred land payment on consent transforms the finance profile and the equity requirement, and an overage clause can quietly take most of the upside you thought you were bidding for.

What a custom build does: land consideration becomes a structured set of payment events with triggers, some date-based, some milestone-based such as consent or first completion, and some formula-based such as overage above a threshold GDV. Each flows into the cashflow at its trigger, so the model answers what the deal is actually worth rather than what a simplified version is worth. Equity waterfalls with preferred return, catch-up and promote tiers get modelled properly, which matters as soon as you have a capital partner, because that partner will model it properly and you should not be the party with the rougher numbers.

Problem 4: the appraisal and the live project stop talking on day one of construction

The appraisal justified the land purchase. Then the project moves into cost management, and cost is tracked in a different system with a different cost breakdown structure, usually the contractor's or the quantity surveyor's. Sales are tracked by the sales team in a CRM (Customer Relationship Management). Finance drawdowns sit with the finance director.

What a custom build does: keep the approved appraisal as the baseline and map live cost commitments and sales to the same structure. Then the report is one line: appraised profit on cost 18.4 percent, current forecast 15.9 percent, driven by these three variances. Sales absorption feeds back into the cashflow, so a slower sales rate shows up as extra finance cost immediately rather than at year end. This is the single feature that converts feasibility software from a bidding tool into a management system, and it is the reason a build usually pays for itself faster than the pipeline analytics do.

Problem 5: sensitivity is presented as a table nobody uses

Every appraisal ends with a sensitivity grid, sale price against build cost, and every committee glances at it. The grid is nearly useless because it varies two inputs while holding the rest static, and because it says nothing about which assumptions are actually uncertain in this scheme.

What a custom build does: run the sensitivity across every input with a defined range and rank by impact on residual land value and on equity return, then express the answer as break-even thresholds a human can hold in their head. Sale price can fall 9 percent before profit on cost drops below the hurdle. Absorption can slip to four sales a month before the facility term is breached. Where you have enough historic schemes, calibrate the input ranges from your own delivery record rather than from a guess, because a developer who consistently comes in 6 percent over budget should be running sensitivity around 6 percent, not around zero.

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, the honest shape is as follows. A first release covering the appraisal engine with your house conventions, residual land value, scheme variants, phasing, monthly cashflow with debt drawdown and interest, and a locked committee output runs $70,000 to $160,000 and ships in 12 to 18 weeks. A full platform adding structured land consideration and overage, equity waterfalls and joint venture splits, ranked sensitivity, live cost and sales tracking against the approved baseline, and pipeline and portfolio reporting runs $180,000 to $450,000 phased over 6 to 12 months.

What drives price up in this category: the number of product types, because build to rent, build to sell, student, senior living and commercial have genuinely different revenue and valuation mechanics and each is real scope. Multiple jurisdictions, since affordable housing obligations, planning contributions, land taxes and sales tax treatment are local and cannot be generalised. Joint venture and fund structures, where the waterfall logic can be as complex as the appraisal itself. Integration with cost management and accounting systems, which is what makes the live tracking work and is usually the fiddliest interface. And your own convention debt, meaning the weeks it takes to get your senior people to agree one house standard, which is a real cost and is not a software problem.

Build versus buy, and when buying is right

Buy if you run fewer than about 10 appraisals a year, or if you build one product type in one market with conventional land purchases. ARGUS Developer is a defensible industry standard and lenders and valuers know it, which has real value when you are raising debt. Feasly is a reasonable answer if your main pain is version control and collaboration rather than structural modelling gaps. And TestFit is worth buying regardless of what else you do, because massing and yield studies are a genuinely different problem and it solves that one well.

Build when several of these hold. Your land deals routinely involve deferred payments, overage, equalisation or landowner equity, and your current model approximates all of them. You compare scheme variants constantly and cannot trust that two appraisals used the same conventions. You have capital partners whose waterfall you need to model exactly. You want the appraisal to remain the baseline through delivery rather than being archived at land completion. Or you operate in multiple jurisdictions with different obligation regimes and are maintaining several spreadsheet dialects as a result.

Our position: the tipping point is deal structure complexity, not volume. A developer doing eight highly structured land deals a year has a stronger case than one doing forty clean freehold purchases, because the value of the build is in expressing what the spreadsheet is approximating.

How to choose a developer for feasibility software

Ask them to explain residual land value back to you before they quote, including where finance and profit interact. If they cannot articulate why profit on cost and profit on GDV give different answers and which your business uses, they will build a calculator with your terminology on it and none of your logic inside it.

Ask how they would model an overage clause paying the landowner 30 percent of GDV above a threshold, and a deferred land payment triggered by consent. The answer should be a structured payment event with a trigger, not a manual line in the cashflow.

Ask who owns the code and get it in writing before kickoff. You should own the repository, the infrastructure accounts, and the right to hire anyone else to continue. At Digital Heroes the client owns the code from the first commit. Your appraisal conventions are your underwriting discipline written down, and that belongs to you rather than to a vendor.