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

Demand in the visitor economy is set by the calendar, the routes, the rooms, and what people are searching for and saying in each origin market. Living Lab reads all of it on one spine and shows what will arrive, by market and by cause.

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 planner or product team gets

One model of everything that moves demand: every event on the calendar, every route in and its seat capacity by week, hotel supply and rate, paydays and holidays in each origin market, weather, competitor dates, and the search interest and social sentiment there. Signal137 shows what drove last season’s demand, market by market. Demand137 shows what will drive next season’s, with the access ceiling as the cap and the interval stated.

What drove last season’s demand and by how much: which events, routes, campaigns, and origin markets moved arrivals, room nights, and spend, attributed with synthetic controls rather than assumed. After the window passes, Living Lab checks the forecast against what happened and reports the error. Every number marked observed, derived, or inferred. The client sees when the model was last retrained.

Demand by origin market, timing, purpose, and price sensitivity, months ahead, with the interval stated. The access ceiling for the destination: seats on the routes, rooms in the peak week, the last mile. Which markets are growing and which are contracting, and what a route, event, or campaign would do to each. Baselines from a naive model and a foundation model, blended by consensus. A refusal, with the reason, when the inputs cannot support an answer.

ProductYour questionYou getWhat it changes
Demand137Where to add capacity, a route, or room supply firstDemand broken down by origin, timing, and purpose, not a single totalInvestment sequenced against where demand is forming
Demand137When to move on price, promotion, or schedulingA forecast that updates as source-market and booking-window signals shiftThe adjustment made inside the decision window
Demand137How to defend a demand assumption inside a business caseA vectorised forecast with a stated confidence range, not a single-line projectionDemand assumptions a finance committee can stress-test
Demand137What would change this forecast?The specific factor behind each vector named: a capacity cut, a rival host, a competing venueA forecast that names what would move it
Demand137How far ahead is this reliable?The horizon stated explicitly for the market and signals availableThe decision is scoped to the horizon the evidence supports
Demand137What happens when a shock hits?The affected vectors flagged and re-run, not the whole forecast quietly abandonedThe forecast survives the shock because it names which part was hit
Signal137Was last year's forecast right, and where was it wrong?The forecast checked against what landed, vector by vectorThe discrepancy reported, not backfilled
Signal137Which of the streams we forecast actually arrived?Origin, stay, and purpose attributed against the forecastThe next forecast starts from what the last one got right and wrong
BothWhat data do you need from us?Much of it built from public, licensed, and third-party signals; yours sharpens specific vectorsNothing moves until it is scoped
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

Demand is up. What is driving it, and how do we build on it?

Living Lab decomposes the total into named drivers. Growth that rests on one event is fragile. Growth across several origins is structural. Each calls for a different intervention.

Which origin markets are growing, and which are about to change, so we move first?

Forward signals by origin: search trends, booking curves, flight capacity, and visa or currency changes. A destination that sees the disruption before the numbers drop can respond in time.

Can we position fleet, inventory, and staff where demand will be next week, not where it was last week?

Demand vectors by place, date, and expected duration. Events, flight arrivals, and hotel clusters geotagged and timed. The operational signal arrives days or weeks ahead of the demand.

How accurate was our last forecast, and how much better will the next one be?

Every forecast is checked against the outcome. The discrepancy is reported by stream, origin, and driver. The model gets better because the errors are named, not averaged away.

A new route is launching. How much demand does it bring, and how do we make the most of it?

The route is connected to origin market demand, accommodation capacity, and event calendar. The demand impact is modelled before the route flies, and attributed after it does.

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.