About bimpowr
We work alongside the people who understand the task, teaching them to use AI and turning existing company tools and knowledge into intelligent systems they can inspect, use, and improve.
Why we started
We saw how repetitive checks, fragmented documentation, and manual data work could consume attention that should go to professional judgment.
Many AI tools offered automation without enough visibility into their steps, sources, or assumptions. We wanted workflows that people could question and control.
bimpowr exists to make existing knowledge searchable, connect it to bounded tasks, and teach teams how to verify the result.
People behind bimpowr
Service provider
Hi, I'm Aleksandar, one of the people behind bimpowr. I have a background in construction engineering and BIM, and much of my work now involves automation and AI. I often see companies spend heavily on AI systems that their own people cannot understand, adapt or use well. With bimpowr, I want to take a different approach: solve real problems and help the people doing the work become better at using AI themselves.
Engineering collaborator
I'm Leonid, and I work on the engineering side of bimpowr. I came to software from construction with a degree in civil engineering, then worked in computational design at Ramboll, where I built automation tools for Revit, Civil 3D, and Tekla for the engineers working alongside me. Since then, I've worked as a senior software engineer and technical lead in construction software, developing public APIs and model and document integrations. I build software and AI agents that run reliably in production.
What brought me to bimpowr is the belief that professional judgment belongs inside the workflow, not outside it. The person responsible can inspect the agent's work, question the result, and decide what happens next.