| Demand137 | Whether to launch, grow, hold, or withdraw a route | Demand vectorised by origin, timing, purpose, and price sensitivity, not a single total | You back the routes the underlying demand can support |
| Demand137 | How to price or target an airport incentive | The destination value the route creates: visitor spend, hotel demand, investment signal | Incentive budget goes to routes that pay back to the destination, not only to the airline |
| Demand137 | How exposed is the network to one hub, one source market, or one shock? | A concentration and resilience view across the route network | You diversify before a disruption forces the point |
| Demand137 | How do sustainable aviation fuel cost and transition risk change the case? | Forward transition scenarios layered onto route viability | Transition risk is priced now, not at the next renewal |
| Demand137 | What happens if we do nothing? | Base, downside, and supported scenarios with a stated counterfactual | The cost of waiting is priced, so acting and not acting compare on the same terms |
| Signal137 | What did the route we supported actually deliver? | Attributed destination value: room nights, GVA, tax, and jobs, per route | You report to the board against the case that funded the route |
| Signal137 | Which routes create destination value, and which only fill seats? | Every route ranked on destination return, on one method | You renew the routes that pay back and let the others lapse |
| Signal137 | Can I have the answer before the slot decision, not after it? | Reports on demand: any route, season, or market, in minutes | Evidence arrives while the decision is still open |
| Both | Can this work when the airline's booking data is commercially sensitive? | Route demand vectorised from destination-side and market signals | The airline's own data is not a precondition |
| Both | Who holds this, and where? | Model, data, and a trained team inside your jurisdiction | The capability survives the change of official or consultant |