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

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

Every destination has a ceiling: the rooms, the routes, the transport, and the tolerance of the people who live there. Living Lab shows where the ceiling is and when demand will meet it, and what to do about it, on the same numbers.

In the last 12 months our OECD and UN SDG aligned model has been deployed at more than 700 events, 49 nations and 180 cities. They delivered 14 million room nights and over US$12bn in gross value added

What a destination planner gets

One model of the destination’s capacity and the demand pressing on it: every route and its seat capacity, every hotel market and its rate, the event calendar, the last mile, and the search interest and sentiment in each origin market. Signal137 shows what the last peak revealed about where capacity bound. Demand137 shows when and where the next peak will bind, with the intervention window flagged. The public body acts before the market and the residents do.

What the last peak revealed: where rate compression appeared, which districts and weeks bound first, where visitors were displaced to the neighbouring city, and what residents said about it. Which events and markets drove the pressure. Attributed, so the constraint is named. Season over season, on one method.

When and where the next peak will bind, by district and by week. The access ceiling stated: seats, rooms, transport, and the last mile. Whether held-back capacity should be released now or kept for the peak. What a levy, a licence cap, or a date move would do to the pressure calendar. Every number marked observed, derived, or inferred.

ProductYour questionYou getWhat it changes
Demand137Whether to release additional capacity, and whenThe gap between forecast demand and available capacity, by date and zone, not an annual averageThe release timed to the specific pressure window, not the planning calendar
Demand137Whether to intervene on price or accessModelled price sensitivity and displacement under the forecast scenario, with a stated rangeIntervention aimed at the dates and locations where it changes the outcome
Demand137Can current capacity absorb a peak without lasting local damage?Demand tested against an explicit operational and social threshold, not a headline visitor totalMitigation triggers set before the peak
Demand137Does this tell us the exact price to set?A price and displacement range under each scenario, not a single tariffThe price remains the operator's, city's, or venue's decision, made on evidence
Demand137How far ahead does this need to run?Long enough to act before the market reacts: weeks for a hotel or event, longer for a transport or access changeThe horizon set to the decision, not a default
Demand137Can it factor in a specific event or seasonal calendar?Event dates, school holidays, and known peaks as standard inputs beside the demand vectorThe calendar is in the model, not beside it
Signal137What did the last peak do to rate, resale, and rents?Rate compression, resale activity, and rent movement attributed to the peakThe next peak is planned on what the last one did
Signal137Did the intervention we made change the outcome?The result set against the counterfactual of no interventionThe next intervention is sized on evidence
BothDoes this account for residents, not only commercial pressure?The same calendar built against a social or congestion threshold, not only a commercial ceilingThe community's question answered on the same evidence as the operator's
BothWho holds this, and where?Model, data, and a trained team inside your jurisdictionThe capability survives the change of official or consultant

Five questions this answers

How do we spread demand across the calendar so the destination grows all year, not just in peak weeks?

Living Lab models demand by date and zone against the destination's capacity profile. The destination tests event scheduling, pricing interventions, and supply release before committing to them.

Where does the destination reach capacity first, and how do we raise the ceiling?

Each constraint is mapped separately. One zone may run out of hotel rooms while another has availability. That needs a different intervention from a citywide transport limit.

What did the pricing intervention we ran last peak achieve, and how do we improve it?

Attribution compares what happened with and without the intervention, on the same method used to plan it. The committee sees whether the action changed the outcome.

Can we set capacity triggers in advance so growth is planned rather than reactive?

Demand137 sets thresholds per zone and date. When a trigger is crossed, the pre-agreed response activates.

How do we protect resident quality of life and grow visitor revenue at the same time?

Resident displacement is modelled alongside visitor spend. The destination sees where growth and liveability support each other, and where one comes at the cost of the other.

Calendar optimisation example

USE CASES

La Sagra

The same event, moved from August to May, grows the country

Most destinations run near capacity for part of the year and well below it for the rest. A visitor added in the peak displaces one already there. A visitor added in the shoulder fills an empty room and is served by staff who would otherwise be idle. Almost no destination runs the calculation before fixing a date.

Read More »

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.