Occupier Demand Radar

Partner-Led · Occupier-Centric · Conflict-Free

Observed Demand Signals

Median demand/timing of the accounts we've found so far, by sector × city. This is a directional read on where our pipeline is concentrated — not a market index (it reflects what we've detected, not total market demand). Cell = median demand intensity; small number = accounts in that cell. Use it to spot where to hunt, not to size a market.

Becomes a real index only with stable source coverage + 6 months of history + market baselines (per audit §3.2). Today it is a directional pipeline view.

Call these companies

Show:

Validate first

Signals worth checking manually before anyone spends BD time.

Company	Score ▾	D · T · V · W	Priority	City	Owner	Status

Checking connection…

Click a row for evidence, sources and the playbook.

How to use this

Every account gets four scores. Demand (does it need space?), Timing (is it active in 0–6 months?), Value (is it worth senior time?), Winability (can HunTR get in?). Final = 35% D + 30% T + 20% V + 15% W.

Bands. Hot ≥65 — assign an owner within 24h, validate, contact. Warm 52–64 — this week. Watchlist 38–51 — recheck monthly. Below 38 — ignore.

Already-solved rule. A company that just signed space is never Hot, whatever its other scores — it becomes a relationship account, marked SOLVED.

Low-confidence rule. A lead with weak evidence is never Hot or Warm. It appears under Validate First.

Your three duties. ① Every Hot lead has an owner within 24 hours. ② Owners mark each lead: validated / contacted / parked / disqualified. ③ Log every outcome — won, lost, no requirement, already advised — by telling Claude. The system retunes itself from these outcomes.

Where the data comes from. A scheduled run every morning at 8:00 IST sweeps funding news, GCC and India-entry announcements, and public job boards, then rescores everything. A 7:55 audit pass reviews yesterday's decisions and outcomes first. Every fact links to its source; nothing is invented.