The problem
The Integrations team connected motor insurance products to national authority systems. When something failed, engineers often had to collect context from logs, Grafana, Swagger, APIs, and Postman before they could understand the case.
The process worked, but it depended on specialist knowledge and consumed too much of the team's time.
What I built
I built the first version of Heimdall with React and TypeScript. It brought work queues, policy context, integration events, comments, decisions, and recovery actions into one interface.
For the Dutch RoyData workflow, Heimdall compared possible no-claims profiles and showed why the system suggested a match. It also supported manual decisions, safety checks, suspension, recovery, and dead-letter queue handling.
For RDW certificate cases, it translated difficult XML responses into understandable errors and warnings. When Heimdall could not complete an action, it linked to the existing tool with the relevant context already filled in.
How it grew
I first released Heimdall alongside the Netherlands launch in January 2023. Engineers used it first. Product colleagues and customer-service agents followed, and the engineering team started contributing to it.
The resulting capability recovered an estimated 50% of the team's operational capacity. This was a team estimate, not an instrumented measurement.
Heimdall also made integration knowledge visible when a senior engineer left. The important part was not the interface alone. The product gave the team a shared place to understand how the system behaved in production.