| Demand137 | Whether to build a demand-forecasting layer in-house or integrate one | A fair comparison of build cost and time against what a connected signal already adds | The fastest defensible path to a differentiated product |
| Demand137 | What connected context adds beyond our own data | The driver and duration of a demand step-change, and whether supply can meet it | A platform that explains demand before the customer notices it moved |
| Demand137 | How do we explain a demand shift to customers with confidence? | An explainable, attributable method rather than an opaque score | A demand answer customers can act on and justify to their board |
| Demand137 | Can this run as an API or a feed, not a report? | A licensed feed, an API, or a co-developed model built to your specification | Integration into your product, on your timetable |
| Demand137 | What does a proof of concept look like? | One market or signal type, connected once, with what it adds made visible | Your team assesses the value before committing to a wider integration |
| Signal137 | Why did that market move last quarter? | The event, route, or price driver attributed, with the counterfactual stated | The rear-view explanation your customers can quote |
| Signal137 | Which of our customers' campaigns actually moved demand? | Attribution of demand shift to campaign, net of what would have happened anyway | A story your destination customers can defend to a funder |
| Both | Does a partnership strengthen or dilute our own data asset? | Clear terms on ownership, governance, and exclusivity, set before anything moves | Capability added without ceding the asset |
| Both | Are you building a competing consumer-facing platform? | No. Living Lab stays as a data and method layer | The customer-facing product, brand, and relationship remain yours |
| Both | What data do we need to share? | Often none; where aggregated data helps, terms are set out first | Nothing moves until the boundary is agreed |