Demand Insights
Bring the signals that move demand into one place, so a pricing decision is made with context.
Inputs
What data is required?
- Demand signals for a location and period
- Your own booking and fleet history for the same period
Outputs
What does it calculate, display or help you decide?
- Demand context shown alongside your own position
- The source and age of every signal used
Build prompt
Not yet written. This module is proposed and not scheduled. The purpose, inputs, outputs and operating complication above describe what it would do; the build prompt, setup steps, dependencies and tests will be added if it is taken forward.
The part that catches people out
Data freshness and provenance. Demand signals arrive from different places at different speeds. A signal that is a week old is not wrong, but it is not the same as one from this morning, and a view that mixes them without saying so will read as more certain than it is.
Optional RME connection
To be defined. Any supported data connection would require approved interfaces and verified data rights.
Any connection to RateHighway services would require approved interfaces, authorisation, tenant isolation and verified data rights. Nothing about access or availability is approved.
Proposed, not scheduled
There is nothing to build from yet. Start with a module that has a written prompt, or read the playbook to decide whether this one is worth building at all.