What to actually ask when you're choosing resident technology for a retirement village

If you run a retirement village, you are almost certainly being pitched a resident app right now. There is no shortage of checklists telling you what to compare: events, messaging, maintenance requests, family updates, adoption rates. Most of those questions are sensible. But there is one question that does more than any other to decide whether the investment pays off, and it rarely makes the list.

We worked through this exercise for ourselves while building Lumin, and got it wrong a few times before we got it right. Here are the questions we wish we had asked first, shared in case they are useful.

Start with who you need to reach, not what you want it to do

A resident app, however well designed, reaches the residents who are willing and able to use a smartphone. In most villages, a meaningful share are not. And that group is rarely random. It tends to skew towards the residents whose needs are growing, the ones who would benefit most from staying connected and visible to staff and family.

Industry experience suggests app-only platforms struggle to reach close to 45% of residents. Before you compare features, ask a vendor how their technology reaches the people who will never open an app. If the honest answer is that it doesn't, you are buying a tool for the half of your community that needs it least.

Adoption is the real metric, not feature count

It is easy to be impressed by a long feature list. Far harder, and far more useful, is real adoption data. A platform that does twenty things but sits unused has cost you money and goodwill.

What drives adoption is less about the technology than vendors tend to admit, and more about onboarding and framing. The figures worth asking for look like this. In a recent survey of 30 residents at The Sterling, a retirement village in Christchurch, New Zealand, with tenure ranging from new arrivals to more than ten years, 93% reported using Lumin daily or regularly, 87% used it for events and village news, and 83% said they felt more connected to their community.

What matters most is who that includes. The adoption held even among residents who started out nervous about technology. One had never owned a computer and was, in her own words, terrified at first, and now uses it comfortably every day. The phrase residents kept returning to was that the more you use it, the more you use it. For an operator, that reframes the task: adoption is not a technology problem to solve once, it is an onboarding question to support well. Ask any vendor for adoption figures from villages that look like yours, broken down by tenure and confidence, not a national average or a pilot of early enthusiasts.

One platform, or several stitched together?

Many operators end up with one vendor for emergency duress, another for resident communication, and a third for smart-home features such as doorbells and lighting. Each works. But you now carry three contracts, three support lines, three sets of training, and the quiet cost of making them talk to each other, which they usually don't.

It is worth asking whether the capability you need can sit on a single platform. The question is not which product has the most features. It is what the total cost of ownership and the operational load on your team look like across three years, not three months.

Don't overlook what's changing under your feet

The amended Retirement Villages Acts in Victoria and New South Wales are reshaping condition-reporting and maintenance obligations. Whatever technology you choose now should make those obligations lighter, not add another disconnected system for staff to maintain.

This is worth raising early with any vendor. Lumin Compliance, for example, grew directly out of operators telling us that condition reports, maintenance records, and e-signature workflows were eating staff time they did not have. Ask how a platform handles the paperwork your team already dreads, because that is where day-to-day value either shows up or doesn't.

Buy for the next 24 months, not just today

Voice, AI, and passive wellbeing insight are moving from nice-to-have towards baseline expectation. The right question for a vendor is not only what the product does today, but whether the platform underneath it can carry those capabilities as they arrive, without asking you to rip everything out and start again.

Technology in this sector dates quickly. The operators who choose well buy a foundation, not a feature set.

What we learned

We did not arrive at any of this cleanly. We built Lumin across all three columns - emergency duress, resident communication, and smart home - from a single managed device, because we kept hitting the same reach ceiling ourselves and kept watching good apps miss the residents who needed them most. The questions above are the ones that cost us the most to learn. We are sharing them because the sector does better when operators buy well.

Five questions for your next vendor meeting

If you take nothing else with you, take these:

1. How does this reach the residents who will never use an app?
2. What is your real adoption rate in villages like mine?
3. Can this sit on one platform, or am I stitching several together?
4. How does this help with my changing obligations under the Retirement Villages Act?
5. Will the platform carry voice, AI, and wellbeing insight as they become standard?