Tools
Compare developers
Two or three developers side by side on what we can actually stand behind: our reading of finish relative to price band, the payment-plan structure that recurs across their projects we cover, and one line from our delivery commentary. We publish no delivery statistics, because none of these developers has given us figures we can audit.
Estimates only, not advice — figures currently in force; confirm with your advisor.
Loading the comparison
The working
How this is worked out
The table sets three developers beside each other in the order you chose and leaves the reading to you — there is no score, no ordering by result and no colour for “better”. Each row comes from something we can point at: our own assessment of finish, the payment-plan structure that actually recurs across the projects we cover, and the first line of our written commentary on that developer.
What each row measures
- Quality tier. Our assessment of finish and specification relative to price band. A judgement, not a statistic.
- Typical payment plan. Derived from the developer’s projects we cover: the structure that recurs most — 60/40, 80/20, a monthly plan — with how many carry it and how many run post-handover. The structure that recurs across their projects we cover. The schedule itself is issued per unit.
- Delivery note. The first sentence of our delivery notes for that developer; the full notes are on its page.
What this tool does not publish
Delivery statistics. Projects delivered, the share handed over on time, average delay, units handed over — a comparison on those numbers is only worth reading if the numbers can be audited, and none of the developers on this site has given us figures that survive checking. A developer’s own marketing count is a claim, not evidence, and putting it in a column would lend it a precision it has not earned. Where a developer publishes a figure worth knowing, it is quoted and attributed in the prose on that developer’s page instead. The day we hold auditable figures, the columns come back with the date they were checked.
What the table cannot tell you
How a specific project is going. The record describes how a developer has behaved across many projects; the tower you are considering has its own contractor, programme and infrastructure on the critical path. Ask us about the one you have in mind and we will tell you what we know, including what we cannot verify.
Next step
Want us to look at this with you?
A reputation tells you how a developer has tended to behave; it does not tell you how a specific project is going. Ask us about the one you are considering and we will tell you what we know, including what we cannot verify.