More than 700 events Ā· 14m room nights Ā· US$12bn GVA Ā· 49 countries Ā· 180 cities Ā· in the past 12 months

Aviation route development: show where the passengers and destination value will come from.

Two routes sit on the table for the next network review: a new twice-weekly service into a secondary gateway, and an extra daily frequency on a route already close to capacity. Both arrive with a business case. Both rest on the same origin-destination totals and a comparator route flown somewhere else.
Demand vectorised for that specific city pair: origin market, seasonality, purpose, price sensitivity, length of stay. Base, downside, and daily-frequency cases as three explicit, checkable positions, not three guesses. The route sized to the demand that is there, not the comparator's.

A tenth of the world's output and employment depends on the visitor economy

Living Lab’s first economic model was for the Singapore Grand Prix in 2012. In 2025 we became a software platform: government-grade intelligence for the visitor economy

In the last 12 months we have deployed at more than 700 events. They delivered 14 million room nights and over US$12bn in gross value added

What does Living Lab do for an aviation route development team?

Aviation route development starts with demand, not a comparator. Living Lab connects the airline’s network data, the airport’s traffic statistics, and the destination’s accommodation and event figures, so a route is assessed against the demand it would serve and the destination value it carries, not the demand a comparator route happens to show. Passenger forecasting standards are set out by ICAO.

Attributes what a route already delivered for the destination against the case that funded it: visitor spend, hotel nights, GVA, tax, and jobs, per route, on one method. Whether the incentive bought demand or paid for demand that would have flown anyway. Signal137 is the post-launch account, on the same evidence base used to plan the route.

Tests a route’s viability, frequency, or incentive case before the slot is committed. Whether the extra frequency is worth committing before demand has proven it, and what load-factor trigger should release it. Whether public co-funding demonstrably changes the outcome. Demand137 ties incentive funding to destination value delivered, not seats flown.

ProductYour questionYou getWhat it changes
Demand137Is this route viable at launch, and at what frequency?Demand vectorised by origin, timing, purpose, and price sensitivity for that specific city pairThe route sized to the demand that is there, not the comparator route's demand
Demand137When to grow, hold, or withdraw an existing routeCurrent performance against the vectorised demand case, not load factor aloneThe network change timed to the evidence, not the review calendar
Demand137How much destination value does the route deliver?Route demand connected to accommodation, event, and investment signals in the destinationIncentive funding tied to destination value, not passenger volume
Demand137Should we commit airport incentive or public co-funding?A bounded case with a stated counterfactual and downsideFunding committed only where it demonstrably changes the outcome
Demand137Is the extra daily frequency worth committing now?The daily case from month six, subject to a load-factor trigger, net of the added capacity costThe frequency released on a trigger, not a hope
Demand137Can this work for a route with no comparator anywhere?Built up from origin-market and destination-side signals, not borrowed from another city pairNo dependence on another route looking similar enough
Signal137What did the route we supported actually deliver?Attributed destination value against the case that funded itThe renewal negotiated from evidence
Signal137Did the incentive buy anything?The route's result set against the counterfactual of no supportPublic money is not spent on demand the market would have delivered anyway
BothDoes this need airline booking data we cannot share?No. Route demand vectorised from destination-side and market signalsThe airline's data is not a precondition
BothWho holds this, and where?Model, data, and a trained team inside your jurisdictionThe capability survives the change of planner or official

Size the aviation route development case to the demand, not the comparator

Calendar optimisation example

USE CASES

La Sagra

Advancing the Tourism Industry

Show me the evidence

Tell us the question. We'll bring back the answer.

Come and show your working

We turn messy event and tourism data into decisions that help communities grow. Bring curiosity and rigour. We will hand you questions nobody has answered yet.