About
An Irish software business focused on operational technology.
KO Technologies builds software for the operational side of physical services — the part of a business where the work happens on a deadline, across several teams, with little tolerance for things getting lost in the handover.
Origin
Where KitchenOps came from.
KitchenOps was not designed from a distance. It came out of direct experience working inside school meal catering operations — seeing the day run from the kitchen outwards, and seeing where it consistently broke down.
The pattern was the same every time. Preparation work being done manually, from raw exports, early in the morning. Coordination between the kitchen, packing, dispatch and delivery held together by phone calls, printouts and memory. And almost no visibility across those steps: a change in the kitchen did not reach dispatch until someone noticed, and nobody could say with confidence what had actually been delivered.
KitchenOps is the response to that. It takes the day's meal data and turns it into operational output that every team works from — the same picture, in the order the day actually runs: production, packing, dispatch, delivery.
There is no larger story than that. It is a product built by someone who has done the work, for the people still doing it.
Founded by
Nicolas Scarnatto
Founder of KO Technologies, working directly with the operations teams who use KitchenOps.
Based in
Cork, Ireland
An Irish software business, working with school meal providers in the Irish market.
Product
KitchenOps
Operational software for school meal providers, currently preparing for live pilot deployment.
How we work
Four things we hold ourselves to.
Build for the workflow, not the demo
Features are judged by whether they survive a real service window: early start, fixed delivery times, several teams working at once.
Say what the product does
No invented customers, no usage numbers we cannot stand behind, and no claims about a stage the product has not reached.
Treat data as a responsibility
School meal data involves children. It is processed with a data-minimisation approach and is not used for anything beyond producing the operation's own documents.
Stay narrow
One sector and one workflow, done properly, is worth more than a broad platform that fits nobody's actual day.
Talk to the person who builds it.
Enquiries reach the founder directly. If you run school meal operations, we would rather hear about your workflow than pitch ours.