About Pulse Context
A small team building the operation layer for the Data-to-AI Value Chain.
Pulse Context exists because the AI capability that matters most, the one that serves a place in its own language, with its own cultural context, is the one most often left out of the value chain. We build the missing layer.
The people
behind Pulse.
Matt Hamilton and Katie Roberts
We started with a simple gap: what a place knows about itself is not always what AI can see. A correction on the radio, a local event, a small business that never makes it into the big datasets.
Pulse is our work to connect that knowledge to the systems people are already using, without losing the source.
Caribbean roots.
Global reach.
Pulse started in Barbados, where the live-signal problem is hardest: FM stations, constant code-switching between English and Bajan, small markets. What we learned there is now the platform.
The team’s roots are in the Caribbean; the platform’s reach is global.
Ecosystem thinking,
not tech-first.
Partners over pipelines. Source provenance as a first-class concern. Evaluation against real local signals. Deployment as the point, not the afterthought.
We start with the people and institutions a system needs to serve, then connect the work across the value chain. A useful answer is not enough on its own. The source must be checkable, the local context must hold, and the system must keep learning from use.
A note on
the framework.
Pulse is built on the Data-to-AI Value Chain, the framework introduced in UNDP’s Introducing the Data to AI Value Chain (2026), co-published with Current AI.
We use it because it is the most useful map of the problem we have seen, and because the team behind it has been doing this work longer than we have.
See the framework in practiceBring your context.
Let’s see what a connected value chain could make possible.