About
What DemandIntel is for
DemandIntel is not just one screen. It is a Singapore demand-intelligence product made up of a public live hub plus public workspaces built for different decisions, time horizons, and user types.
Public DemandIntel
The public DemandIntel homepage is the fast-answer layer. It is built for quick checks on what is happening in Singapore right now: traffic pressure, airport movement, cruise pressure, event pull, and whether parts of the city feel smooth, busy, or painful.
Flow
Flow is the movement-intelligence workspace. It is built to interpret where pressure is now, where it may shift next, and what traffic, event, weather, and arrival signals are driving that movement.
Hospitality
Hospitality is the forward-planning workspace. It is designed for hotels, serviced apartments, retail, F&B businesses, and revenue-facing teams that need a cleaner read on demand build, calendar watch days, rate pressure, and what might matter commercially over the next several days.
Inbound
Inbound is the same-day incoming build workspace. It is used for faster scenario work around flights, cruise, visitor pressure, and broader arrival-linked demand when a directional estimate is more useful than a static report.
What runs underneath
Across the public hub and the workspaces, DemandIntel combines live feeds, modelled layers, and reference signals. Traffic, flights, cruises, weather, venue pull, calendar pressure, and movement friction are used differently depending on whether the question is “where is movement heading?” or “what demand is building next?”
How to think about the product
Live is for fast awareness. Flow is for near-term movement direction. Hospitality is for forward commercial planning. Inbound is for demand modelling and scenario estimation. They share the same demand engine, but each workspace turns that engine into a different type of answer.
Current stage
This is still an early live product family. The public hub and workspaces are already open, while data coverage, heuristics, and decision language continue to be cleaned up, refined, and expanded. The answers will keep improving as real usage feedback comes in.
Send feedback
If you spot bad data, want a new zone tracked, or think a signal looks off, send a note to [email protected].