Frontline experience
Supporting people directly and understanding the realities, pressures and responsibilities of each shift.
Why I built Castodia
I understood care
before I learned software.
My name is James Lunt. I did not set out to create a software company. I set out to support people — and eventually realised that the tools used by care teams could be better.
James Lunt
Founder, Castodia LTD
Care came first
I was not looking for a career in technology.
Before writing code, designing screens or starting Castodia, I worked in health and social care. My focus was supporting people, learning from them and helping them live the lives they wanted.
Over the years, I progressed through different responsibilities and gained experience of frontline support, leadership, documentation, compliance and the daily challenges faced by care teams.
I saw how excellent support could be strengthened by good systems — and how easily poor systems could introduce frustration, confusion and unnecessary pressure.
Experience behind the platform
Built from more than theory.
Leadership experience
Learning how documentation, communication and systems affect whole teams as well as individual support workers.
Level 5 qualified
A Level 5 Diploma in Leadership for Health and Social Care, supported by continued professional development and further study.
What real shifts taught me
Care rarely happens in calm, convenient conditions.
I have completed documentation during long night shifts, after difficult incidents and while remaining responsible for the wellbeing of the people around me.
I have tried to produce detailed records while another person needed reassurance, support or my immediate attention.
Those experiences taught me that every unnecessary field, hidden option and extra click has a real effect. Software should remove pressure from a shift, not add to it.
The question I kept returning to
“How easy is this for a night support worker to complete at 3am while supporting an unsettled person?”
That question has shaped almost every workflow, form and design decision inside Castodia.
Experience leaves its mark
Every scar taught me something.
Years supporting people whose distress could sometimes result in behaviour that challenged those around them have left me with a few physical scars.
I do not mention them as trophies. They are reminders of moments when someone needed skilled, compassionate support during an extremely difficult time.
They also remind me why systems must work when circumstances are demanding. Staff should be able to record what matters clearly, without the software becoming another obstacle in the moment.
The beginning of Castodia
Eventually, the questions became a platform.
I found myself asking the same questions repeatedly. Rather than waiting for someone else to answer them, I decided to begin building.
01
“Why does this need so many clicks?”
02
“Why is the information staff need so difficult to find?”
03
“Does this help staff provide better care, or merely record it?”
04
“Could this still be completed properly at the end of a difficult shift?”
05
“Will this encourage quality care, with compliance following naturally?”
Why it matters
I did not build Castodia because I wanted to start a software company.
I built it because I believe the people delivering care deserve better tools.
If Castodia can save support workers time, reduce frustration, strengthen handovers and help managers spend more time leading, then every hour spent building it will have been worthwhile.
Better records matter. Better compliance matters. But ultimately, the purpose of both is to help people receive better care.
From me to you
Thank you for taking the time to understand why Castodia exists.
Whether you are exploring the platform for the first time or considering Castodia for your organisation, I hope it makes the working day a little simpler — and leaves more time for what really matters.
People.