From idea to product

Take a Murska Sobota civil engineering contractor running seventy machines across sites in Pomurje. Foremen report breakdowns on Viber, by email or over coffee in the site cabin, mechanics receive printed lists from a spreadsheet, and the only person who knows when each excavator is due for servicing goes on leave in two months. The managing director says, “We need an app.” Perhaps. Perhaps a well-built list in Microsoft 365 and a clear rule about who logs what would do. So our opening move is questions, not code. Where does information go missing? How long does it currently take from breakdown to mechanic? What would have to change for you to call the spend worthwhile? Only with answers and a baseline figure in hand do we propose the leanest release that already fixes the pain, give it to a handful of real users and grow it according to what the numbers show. Each phase carries its own quote and its own deliverable, which you keep. It all runs over video calls and shared screens; nobody needs to visit a site when phone clips and a chat with the people doing the job tell us what we need.