We spent years rebuilding the same scripts. So we stopped.
Founded in Prague in 2023, Pointee grew from direct experience with how financial operations teams interact with legacy systems. Our founders spent years watching banks and insurers attempt automation projects that failed because the process layer was never mapped first.
The automation projects that kept failing
Banks and insurers spend significant budgets on automation, and a large share of those projects either stall or get quietly decommissioned. The pattern is consistent: automation was built before the process was understood. Scripts broke when a field moved, a system was upgraded, or a rarely-used workflow variation surfaced. The people who knew how those processes actually worked were the operators. Nobody asked them first.
Pointee was built to invert this. Discovery and mapping before automation. Every process documented and signed off by the team that runs it. Automation built on what actually happens, not what the procedure manual says should happen.
The people building Pointee
Petra spent her early career in operations consulting at a large Central European financial services group, where she led process improvement projects across retail banking and property insurance. She saw the same automation failures repeat across different clients and came away convinced that the discovery layer was the missing piece. She founded Pointee in 2023 with the goal of making that layer a structured, auditable product rather than an afterthought.
Martin previously built automation tooling for a large enterprise software team, where he worked on process capture and workflow infrastructure for internal operations. He brought that experience to Pointee to design the observation engine from the ground up. His focus is building a UI-layer automation system that is resilient enough for the messy, version-inconsistent environments that financial operations teams actually work in.
Karolina came to Pointee from an operations analytics background, where she worked with financial institutions to identify workflow bottlenecks and document back-office processes for regulatory audits. She leads the process engineering practice at Pointee, working directly with clients to turn discovery outputs into accurate, actionable process maps before any automation is built.
How we work
Document before automating
Every process is mapped and reviewed with the operations team before Pointee builds any automation. This is not a phase you can skip to save time. It is the reason the automation holds.
The operators know the process
The people who run these processes every day know more about them than any procedure document. Our discovery phase is designed to surface what they actually do, not what the manual says they should do.
Automation should not require infrastructure changes
Banks and insurers move slowly for good reasons. Automation that requires API integrations or system changes creates dependencies, delays, and vendor negotiations. We built Pointee to work without any of that.
Exceptions are not failures
Every process has edge cases. When Pointee hits one, it routes the exception to the right person with full context rather than failing silently. The goal is not to eliminate human judgment. It is to apply it in the right places.