It is two in the morning. The on-call manager's phone rings. A young person has not come back to the property and the property cannot reach them. The manager opens the system to start a missing pack. The system asks for the YP's name, address, recent photo, last known location, support worker's mobile, current GP, allergies, medication, appearance description, behavioural triggers, and the police log reference if one has been opened. The system needs all of these to produce the document the police are about to ask for.
In a system built by software people for care providers, those fields are spread across eight tabs of the YP's record. The on-call manager hunts through tabs. The 2am call to the police gets delayed. The young person is still missing.
In a system built by a provider, the missing pack is one click on the YP's record and the document assembles itself. The fields the police are going to ask for are pre-populated. The photo is current because there is a workflow for keeping photos current that the system enforces. The 2am call to the police happens at 2:01am with the right document already in front of the manager.
This is the difference. The same fields, the same data, the same software platform underneath. But the second one was built by someone who has been the on-call manager at 2am.
The pattern repeats across every workflow in the platform. The Help Now button on the TIFA YP app sits in fixed bottom navigation on every screen because young people in distress will not navigate menus. The 999 routing is one tap, with category-aware briefing for the dispatcher built in, because the on-call team has had to manage the conversation while the YP is on the line. The daily check-in is ten seconds and earns ten points because keyworkers know what gets used and what gets ignored. The mood data flows directly into the Placement Health Score because the on-call team needs to know which YP is heading toward a hard week before the hard week arrives, not after.
None of these are clever software design choices. They are operator instincts, embedded in software. The clever part is that we built it ourselves.
Most software vendors in this category build software for care providers. The product manager has read about the sector. The user researcher has run focus groups. The CTO has talked to a couple of registered managers. The result is a tool that broadly resembles what providers need, but every shortcut is a shortcut a software person would have taken, not a provider would have taken.
We built TIFA Connect inside TIFA Life. The team running TIFA Life uses it every day. Every feature exists because we needed it. Every workflow exists because the previous workflow was not working in the operation. There are no focus groups. There is no product manager translating between sectors. The translation step is gone.
This is not a complete advantage. There are things we get wrong that a more disciplined product process might catch. There are providers whose operational reality differs from ours and TIFA Connect needs to flex to fit them, not the other way around. We are conscious of both.
But the trade is real. A platform built inside the operation, by people on call at 2am, is structurally different from a platform built for the operation by people who have read about it. The structural difference shows up at every interaction with the product.
We did not set out to build this software. We set out to run a service. The software is what we built when we could not find software that fit the service. We are now offering it to other providers because the alternative is that they end up where we started, building from scratch. We have done that work. They do not need to.
If you are evaluating supported accommodation software, ask the vendor a simple question. When was the last time someone on your engineering team was on call at 2am with a missing young person? If the answer is "never", you are not buying our category of product.
Michael Border is the founder and Managing Director of TIFA Life Ltd. To talk about TIFA Connect, book a 30-minute demo or email michael@tifa.co.uk.