Beyond the Stage: How Done Robotics Uses Slush to Build the Future
At Slush, the stage is where ideas get attention. It is where you say, in a few minutes, what you believe the future should look like.
For Done Robotics, that message is simple: hospitals should not run on manual logistics.
Today, a significant part of hospital resources is still spent on moving beds, transporting goods, and handling internal flows. Some estimates suggest that up to 30% of hospital budgets are tied to inefficient logistics, while staff shortages and rising patient volumes continue to increase pressure on daily operations.
At the same time, around 10% of patients are affected by hospital-acquired infections, adding both human and financial cost to already strained systems.
These are not future problems. They are current operational realities.
The stage helps communicate that clearly. It forces a simple question: what if these problems were handled differently?
But for decision-makers, the real value starts when the conversation moves beyond the pitch.
Because the challenge is not understanding the potential of robotics. It is understanding how it works in practice. How it fits into existing workflows, how it behaves in complex environments, and how quickly it can start creating value without adding new friction.
This is where discussions at Slush become useful. They move quickly from vision to operations. From what the robot does to how it performs during peak hours, how it interacts with staff, and how responsibility is handled in real situations.
In many of these conversations, a pattern emerges. The biggest barrier is rarely the technology itself. It is uncertainty around implementation.
Hospitals are careful for a reason. Introducing a new system affects multiple stakeholders, from clinical staff to operations and management. Even small disruptions can have consequences, which makes predictability and reliability more important than technical features.
That is also why Done Robotics is built around a different approach. Not just delivering robots, but delivering them as a service.
Instead of a one-time investment, hospitals get a continuously managed system where robots are monitored, updated, and integrated over time. In practice, many decision-makers see this as a way to reduce risk. It shifts the focus from owning technology to ensuring outcomes.
The same thinking applies to how the robots are designed. They are not built for isolated environments, but for shared spaces. Moving alongside patients, visitors, and staff, they need to be predictable, safe, and non-disruptive. This is where “robots for people” becomes more than a concept. It becomes a requirement for adoption.
What Slush makes clear is how quickly ideas are tested when they meet reality. A strong vision is important, but it is the operational details that determine whether something moves forward.
For Done Robotics, the stage is where the conversation starts. The real work begins immediately after, when discussions turn into pilots, and pilots into everyday use.
Because in the end, the value of robotics is not defined by how it sounds in a pitch.
It is defined by how it performs in a hospital corridor.
