Why we publish our scorecard weights

title: Why we publish our scorecard weights category: Opinion byline: Larry Bekchyan date: 10 May 2026 summary: Developer rankings in the UAE media are either bought or opaque. We published every weight behind our scorecard not because regulators asked for it, but because a score with hidden weights isn't measurement — it's marketing. readingTime: 5

If you read UAE property media, you've seen developer rankings. Bayut publishes a "Top 10" every quarter. Industry publications run annual lists. The logic is simple: rank developers by some score, publish the winners, give readers a shortcut to decision-making.

The problem is obvious: almost every ranking is either sponsored or opaque.

The sponsored ones are explicit. A publication calls a developer, quotes a "ranking placement fee," and publishes accordingly. It's honest corruption — you know what you're getting.

The opaque ones are worse because they're dressed up as analysis. The publication says they've developed a methodology, weighted by factors like "delivery track record," "investor satisfaction," and "innovation." But the weights are never disclosed. The methodology is proprietary. You're told the answer (Developer X is #1) without being shown the work.

This is how marketing disguises itself as measurement.

When we built EstateForge's Developer Scorecards, the first question was what to do about this. We could go the proprietary route — develop a method, publish rankings, keep the weights secret. It would be more defensible (we couldn't be criticized for specific weight choices), and it would be more commercially appealing (proprietary methodology = competitive advantage).

We didn't.

What a published weight does that a private one doesn't

A weight is a statement. It says: "We believe this factor matters more than that factor, and here's how much more."

When the weight is hidden, the reader has no way to challenge it. The publisher can claim that "investor satisfaction" matters, but if it's weighted at 5% while "marketing spend" (disguised as "brand presence") is weighted at 40%, the reader will never know they've been sold a ranking.

When the weight is published, three things change:

First, it becomes falsifiable. If we say "delivery track record" is 35% of the score and "financial stability" is 25%, and you disagree with those proportions, you can say so. You can run your own scorecard with different weights and publish it. You can challenge us publicly. The number is no longer opinion — it's a claim we've put our reputation on.

Second, it becomes comparable. Other scorecards can use the same factors and different weights, and readers can see exactly where they diverge. Maybe Economist A weights safety of escrow at 40% while we weight it at 20%. The reader sees the difference and can decide whose judgment they trust. Without published weights, all rankings look the same from the outside.

Third, it becomes updatable. If we publish weights and the market changes (new escrow rules, new types of risk, new developer models), we can update the weights and explain exactly what changed and why. "We raised financial stability from 25% to 30% because three major developers defaulted in 2025." That's a learned update. A hidden methodology just changes silently, and you're none the wiser.

The specific weights and why they're what they are

Our Developer Scorecard is a 100-point scale weighted across five dimensions:

Delivery track record (35%)

Have they finished projects on time? This is the biggest weight because nothing else matters if the developer doesn't deliver. We measure:

• % of projects completed on or before announced timeline (not "substantially complete" — fully delivered)
• Average delay (in months) for projects that slipped
• Trend (is delivery improving or deteriorating year over year?)

A developer with 90% on-time delivery in a rising market scores higher than one with 70% delivery. A developer that's improving (85% in 2024, 92% in 2025) scores higher than one that's consistent but sliding.

Financial stability (25%)

Can they afford to finish what they start? We measure:

• Escrow balance relative to committed project value (are reserves adequate?)
• Debt-to-equity ratio in company-level filings (how leveraged are they?)
• Payment history with contractors (do suppliers get paid on time?)

A developer with high leverage and a history of payment disputes scores lower, even if they've delivered in the past. Financial stability is about future risk.

Design and quality (20%)

Do their units and buildings age well? This is subjective, so we outsource it to user surveys (EstateForge subscribers rate completed projects) plus professional review of:

• Finishes and materials (will they look dated in 5 years?)
• Space planning (is the unit thoughtfully laid out?)
• Building systems (HVAC, electrical, plumbing — are they robust or cost-minimized?)

This is the most qualitative dimension, which is why it's weighted lower. We're explicit that it's user + expert opinion, not objective measurement.

Customer experience (12%)

How do they treat buyers post-sale? We measure:

• Complaint volume (relative to project size)
• Response time to defect reports
• Dispute resolution track record (do they fight justified complaints?)

A developer that's slow to fix issues or aggressive in disputes scores lower here, regardless of how nice their finishes are.

Innovation (8%)

Are they doing something materially new in the market? This is the smallest weight because novelty isn't success. But a developer that introduces a new building system (better cooling, passive design, modular units) or a new ownership model (fractional investment, flexible terms) gets credit here. It matters less than delivery, but it's not zero.

Scores and controversy

The scorecards aren't controversial because the weights are hidden. They're controversial because the weights are visible.

A developer that's scored low on our card can't say "your methodology is secret and proprietary." They can only say "we disagree with your weight on financial stability" or "our delivery timeline numbers don't match yours." That's a real, addressable disagreement.

When we published the weights, I expected pushback. A developer rated #3 when they felt they should be #1 could (and did) call and dispute the delivery numbers or argue that design quality should be weighted higher. That's healthy. It means the methodology is being tested.

What we didn't get was silence. What we didn't get was people dismissing the scorecard because we were hiding something. The transparency made it credible in a way that proprietary rankings never are.

An invitation to challenge

If you think our weights are wrong, I want to hear it. If you think delivery timeline should be 25% instead of 35%, or that customer experience matters more than innovation, build your own scorecard with different weights and publish it. Use our data (it's public) or collect your own. Show the work.

The developers who do the work of actually delivering, finishing on time, treating customers well — they win in any reasonable scoring system. The developers that are gaming metrics, hiding defects, or relying on opaque marketing — they only win when scorecards are opaque.

A published weight might invite criticism, but it ends the game of marketing disguised as measurement.