We didn’t set out to build just another hospital software. We set out to build something proper — something that truly reflects how hospitals move. Not just how jobs are assigned, but how people coordinate, wait, rush, adjust, and care.
We didn’t start from grand theory or buzzwords like “smart hospitals” or “digital transformation.” We started from the floor — from watching how real work happens when patients need to be moved, when jobs stack up, when people disappear from the screen and no one knows why.
And along the way, we found out: it’s hard.
Not hard in the sense of writing code or integrating APIs — though there’s plenty of that. But hard in the sense that logistics in hospitals is alive. It pulses. It stumbles. It feels things. And if a platform wants to help, it can’t just be fast — it has to be thoughtful. It has to understand.
This ebook is a collection of what we’ve learned while building Dispatcher, our real-time hospital logistics platform. It’s about the hard things — the hidden complexities, the decisions you don’t see, the tradeoffs we wrestle with every day. You’ll read about why “real-time” doesn’t always mean real help, why every job is different (and should be treated that way), why data is meaningless without context, and why pressure — not speed — is the real enemy.
But this isn’t just about technology. It’s about design. About people. About care. Every decision we’ve made — from how we structure databases to how we show an emoji — reflects a deeper belief: logistics is not just infrastructure. It’s interaction.
If you’re curious why hospital logistics still feels behind, or if you’ve tried and failed to digitize it yourself, or if you’re building tools that aim to support people under pressure — we wrote this for you.
Because building something proper — something that works — is hard.
But it’s also how we move things forward.