The origin
Why We
Built This
Straight up — our sales team needed to know what was happening with global events that were shaping our delivery horizon, but we couldn't task someone to spend all day on Reuters, Reddit, CBC, BBC and the rest. We were juggling: getting timing wrong, or spending so much time trying to get it right that we weren't actually doing anything with the information.
The problem wasn't a lack of information. It was the opposite. Everything was available and none of it was organised around the question we actually needed answered:
Does this affect our operations — and if so, when and how much?
A conflict breaks out in a mining region. Somewhere between the wire report and a decision about our supply chain, there are twelve tabs open, three Slack threads, and someone's nephew who "follows geopolitics." By the time we had a clear picture, the window had usually moved.
We looked for something that gave us a clean read — not a newspaper, not a think tank, not a commodity desk report padded to justify a subscription fee. We wanted the version a smart, well-connected colleague would give you if you asked them in the hallway: here's what's happening, here's why it matters to what you're doing, here's what to watch next.
That product didn't exist.
So we built it.
Conflict Watch is what happens when you stop trying to follow the news and start treating geopolitical risk as an operational input — something to be tracked, assessed, and acted on like any other variable that affects your delivery horizon, your margins, or your ability to close.
It's invite‑only because the product only works if the analysis stays tight. We're not trying to brief the whole world. We're trying to give a small number of operators a genuine edge on the decisions that actually matter to them.