Foresee · Travel demand · internal product · 2026
A demand dashboard that tells a travel network where the crowds go next
Event data is only useful if someone can act on it. Foresee turns a warehouse of upcoming events into a map, a forecast and an API — so operations, marketing and the other internal tools all read the same signal.
5 views
views over one shared demand signal — overview, events, forecast, anomalies, map
A travel network's workload is driven by things it doesn't control: festivals, matches, conferences, concerts. That information exists — it sits in an events warehouse — but a warehouse is not a decision. Nobody outside the data team could look at next month and say where the pressure would land.
Every question about upcoming demand turned into a SQL request. Answers came back as one-off spreadsheets that were stale by the time anyone read them, and each internal tool that wanted the same signal ended up reinventing its own query — so no two answers ever quite matched.
Built a read-only intelligence dashboard over the events warehouse: overview KPIs, an events explorer, a forward-looking forecast, anomaly detection, and a map that puts demand where it actually happens.
Put the API layer underneath the UI rather than beside it. The pages call the same documented endpoints any other internal tool can, so there is exactly one definition of each number.
Added authentication and a self-serve API key manager: teams create their own keys, see the secret once, and revoke it when they're done. Keys are stored hashed; the dashboard itself sits behind single sign-on.
Shipped it as an ordinary web app on managed hosting, so it stays current without anyone babysitting a reporting pipeline.
Events warehouse
demand that hasn't happened yet
Query layer
one definition per metric, written once
Documented API
10 endpoints, authenticated, self-serve keys
The UI is just another client
pages call the same endpoints anyone else can
- overview
- events
- forecast
- anomalies
- map
- other internal tools
5 views
overview, events, forecast, anomalies and map — one shared read of demand
10 endpoints
a documented API, so other internal tools consume the same numbers
self-serve
teams issue and revoke their own API keys; nothing is open by default
- Next.js
- Postgres
- Recharts
- Leaflet
- Clerk
- Vercel
More on what we do for
B2B SaaS