We built a teammate, not another tool

Hoopi comes out of Knowledge Agents, a product and solutions company in Dallas–Fort Worth, Texas. Before that, most of us spent years inside large transformation programmes — the kind where the recommendation is excellent and the recurring work underneath it never actually changes.

The pattern was always the same. A team would explain their process, we would map it, and somewhere in the middle would sit four hours a week of a smart person opening systems, copying numbers, reconciling disagreements between them and writing the same paragraph in a slightly different way. Nobody wanted that job. Nobody could get rid of it either, because doing it required judgment about which number to trust.

That is the job Hoopi was built for. Not the chat window, not the workflow canvas — the actual cross-system assembly work with judgment in the middle of it. And because that work touches real systems, it has to be governed: scoped access, approval gates, a complete log. Those were not features we added later. They were the reason the thing could be trusted at all.

The bird is a kingfisher. It waits, watches the whole surface, and moves once — precisely. That is roughly the behaviour we are aiming for.