Care platform or smart home platform? How to choose without regretting it

At some point in specifying technology for an assisted living scheme, someone will ask whether to buy a care platform or build on a smart home platform. It is presented as a technical question. It is really a question about who carries the risk, who can maintain it, and what happens in five years.

Both answers are defensible. Choosing badly is expensive in a way that is not obvious for about two years.

What each one actually is

A care technology platform

Purpose-built for care settings: nurse call, fall detection, activity monitoring, staff workflow, reporting for regulators. Sold with installation, support and maintenance, usually as a multi-year contract with a per-apartment or per-resident fee.

What you are buying: accountability. Someone else's responsibility for it working, a support line, a product designed around care workflows and regulatory expectations, and often certification against relevant standards.

What it costs: considerably more, in ongoing fees rather than hardware. Less flexibility, slower change, and frequently proprietary hardware you cannot source elsewhere. And genuine lock-in: leaving means replacing everything.

A smart home platform

General-purpose hubs, standard protocol sensors, automations you configure. Very low hardware cost, no per-resident fee, enormous device choice, and complete control.

What you are buying: flexibility and low cost. You can change anything, add any sensor, and integrate with building systems that a closed platform will not touch.

What it costs: you own the risk. There is no support line that understands care. Nothing is certified for anything. And the whole thing depends on somebody in your organisation understanding it — which is fine until that person leaves.

The questions that actually decide it

Who will maintain this in three years?

The single most important question, and the one least often asked. If the answer is a named role with time allocated and documented procedures, a self-built system is viable. If the answer is “the maintenance chap is quite good with computers”, buy a supported platform. Care organisations have high turnover, and a system only one person understands is a system with a resignation-shaped failure mode.

What does your regulator expect?

Inspection regimes increasingly ask about assistive technology: what is used, on what basis, how consent is handled, how it is maintained and tested. A care platform usually arrives with documentation shaped for that conversation. With a self-built system you write it yourself, which is entirely possible but is real work that should be costed.

How many apartments?

Per-resident fees scale linearly while your own effort does not. Below roughly twenty apartments, platform fees are often modest and the support genuinely worth it. Above a hundred, the same fees fund a serious internal capability. In the middle it is a judgement call.

What already exists?

Many buildings have a nurse call system, an access control system and building management, all from different suppliers, none talking to each other. The realistic question is frequently not which platform to buy but what will integrate with what you are stuck with. Ask suppliers specifically and get the answer in writing, because “open” and “integrates” are used very loosely in this market.

The hybrid that most schemes end up with

In practice the sensible answer is usually layered, and it is worth designing that deliberately rather than arriving at it by accident.

• Certified, supported equipment for anything safety-critical: nurse call, fire, carbon monoxide. Non-negotiable.
• A care platform or a monitoring service for out-of-hours response, if you do not have twenty-four-hour on-site staff. You are buying trained operators and an audit trail, which is hard to replicate.
• Standard smart home technology for everything else: environmental monitoring, leak detection, lighting, heating control, communal areas, energy. This is where cost savings are large and risk is low, because nothing here is life-critical.

That split puts the money where the accountability needs to be and keeps the flexibility where flexibility is useful.

The cost comparison people get wrong

Platform fees are visible and hardware is cheap, which makes the self-built route look dramatically less expensive. Over five years the gap is usually narrower than it first appears, because three costs sit on the self-built side and rarely appear in the spreadsheet.

Staff time. Configuration, tuning, testing, documentation and the quarterly reviews. An hour a month across forty apartments is not much; an hour a week is a real cost that has to come from somewhere.

Replacement and obsolescence. Consumer devices have shorter support lives than commercial equipment. Budget for replacing a proportion of sensors every few years, and for the occasional product being discontinued.

The bus factor. If the one person who understands it leaves, the cost is either a consultant at short notice or a rebuild. That is a real risk with a real price, and it is the one most often left out.

None of this makes the platform route automatically better. It means the honest comparison is total cost of ownership over five years including staff time, not hardware against subscription.

Questions to put to any supplier, in writing

• Does anything still work with no internet connection? Ask specifically which functions. Some platforms lose almost everything.
• What happens if we stop paying? Does the hardware continue working in a reduced form, or become inert? This is the difference between a subscription and a hostage situation.
• Can we export our data, in what format? Including historical records, which you may need for an incident investigation years later.
• Is the hardware proprietary? If a sensor is discontinued, can it be replaced with a standard equivalent or only with theirs?
• Where is data stored, and under whose control? For EU providers, whether it leaves the EU is a compliance question, not a preference.
• What certifications does it hold, for which functions specifically? “Designed for care” is marketing; a standard number is a fact.
• What is the support response time overnight, and is it contractual?
• Who else runs this at our scale? Then call them without the supplier present.

Avoiding the two classic mistakes

Buying the demo. Everything demonstrates well. Ask to see a system that has been running for three years in a building like yours, and talk to the staff who use it at night rather than the manager who bought it.

Underestimating the process cost. Whichever route you take, the checklists, reviews, testing and documentation described in move-in and move-out administration still have to be done by someone. Budget the time explicitly. A cheap platform with no process is worse than an expensive one with process, and the difference does not show up until an inspection or an incident.

A defensible procurement path

1. Write down what you need it to do, in terms of outcomes, before talking to any supplier.
2. Separate the safety-critical from the rest and accept that the first part will be bought, certified and supported.
3. Name who will own the system internally, with time allocated. If you cannot, buy more support.
4. Pilot in one wing with two shortlisted options if you can, for a season rather than a fortnight.
5. Get the ten questions above answered in writing before signing anything.
6. Plan the exit at the start — data export, hardware ownership, notice periods. Contracts are much easier to negotiate before you depend on them.

The best outcome is usually unspectacular: certified kit where lives depend on it, ordinary standards-based technology everywhere else, and one person whose job includes keeping it honest.