Two engineers in Sofia.
From automating our own work to yours.

Philip owns the front half of every engagement: working out which problems are actually worth solving. Most teams know something is slow or painful, but not which process is quietly costing them the most — or which one AI can realistically take off their plate. He sits with the business, maps how the work really flows, and separates the automation that pays for itself from the shiny idea that won't.

From there he designs the solution and makes the case for it — what gets built, what it replaces, and the concrete hours and euros it gives back. He runs sales and delivery on the same thread, so the thing we promise on the first call is the thing that ships, with no hand-off where the original goal gets lost.

Martin owns the build. Before a line of code is written, he turns the agreed goal into a clear specification — what each automation must do, the edge cases it has to survive, and what "working" actually means in numbers. It's the difference between a demo that looks impressive once and a system you can trust on a Monday morning.

He's responsible for quality and security end to end: reviewing the code, hardening how client data is stored and accessed, and testing every workflow against real examples until it produces the same correct outcome every time. If an AI step can drift or fail quietly, his job is to catch it long before it ever reaches your accounts.