What We Learned From 5 Senior Living Leaders Before Building a Single Feature

There's a tempting shortcut in building software: assume you understand the problem, sketch a solution, and start shipping. We chose a different path.

Before Caily's product team wrote a single line of code for our B2B platform, we built an advisory board. Not a token advisory board — a working one. We convened a group of people who have spent their careers inside senior living communities: executive directors, directors of nursing, care operators, healthcare consultants, and home care providers. We met with them multiple times, across structured sessions that ran from product discovery to sales and marketing. We asked hard questions and, more importantly, we listened.

What follows is what we learned. Not a sanitized summary — the real stuff, the kind that only comes from structured conversations with people who have nothing to gain from telling you what you want to hear.

Why an Advisory Board, Not Just User Interviews

We could have done a handful of one-off calls. We didn't. We structured this as an ongoing board because we knew that senior living is a world with layers — the person who feels the pain of a broken communication system isn't always the same person who approves the budget to fix it, and neither of them is the same person who decides whether staff actually adopts a new tool.

We needed all of those perspectives in the room, talking to each other, not just to us.

Our board brought together voices spanning memory care, assisted living, skilled nursing, PACE programs, consulting, and home care. Some operated single-site communities; others had multi-site or regional experience. Together, they gave us something no survey could: a ground-level view of how communication actually works — and breaks down — inside senior living facilities every day.

Lesson 1: The HIPAA Problem Is Hiding in Plain Sight

One of the first things our advisory board surfaced was something nearly everyone in the room recognized immediately but rarely talked about out loud: staff across senior living communities are routinely communicating over personal cell phones and group texts — and that's a HIPAA problem.

We heard from multiple operators that their facilities use informal group text threads for internal staff communication. Shift updates, scheduling changes, care notes, resident information — all moving through personal phones with no audit trail, no compliance controls, and no security.

The reason isn't recklessness. It's practicality. The tools that exist — Teams, email, EHR messaging — require staff to be at a desk, logged in, and navigating a system that wasn't built for fast-moving floor work. Group texts are immediate. They work. So staff use them.

The problem is that when something goes wrong, and in senior care something always eventually goes wrong, there's no defensible record. As one advisor put it, if it isn't in writing in a compliant system, it effectively didn't happen. That's a liability exposure every single facility we spoke with was living with.

This insight became foundational for Caily. HIPAA-compliant communication isn't a nice-to-have feature. For our buyers, simply being able to say "this is HIPAA-compliant" checks a critical box that opens the door to every conversation that follows.

Lesson 2: Existing EHR Systems Are Not the Answer

Every facility our advisory board members represented used an EHR or EMAR system. PointClickCare appeared most frequently, with MatrixCare also mentioned for certain care settings. These systems are the backbone of clinical documentation in senior living.

They are also, almost universally, described as clunky, overwhelming, and difficult to use consistently.

We heard about dashboards with too much information, systems requiring multiple logins, complex interfaces that demand significant cognitive load from staff who are already stretched thin. One advisor described the experience of checking their EHR for updates as high-effort compared to the one-button simplicity staff need on the floor.

The result? EHR systems capture what's legally required, and not much more. The rich, relational, anecdotal information that families actually want — what their loved one ate at lunch, how they seemed during morning care, whether they participated in the afternoon activity — isn't being captured in any systematic way. It lives in caregiver memory, on sticky notes, or in informal conversations that never make it into a record.

This told us something important about where Caily fits. We're not here to replace EHR systems — that would be the wrong battle. We're here to capture the layer of communication that falls through the cracks between the clinical record and the family's inbox.

Lesson 3: The Family Communication Gap Is a System Problem, Not a People Problem

When we asked our advisory board to describe how families get information about their loved ones, the picture that emerged was surprisingly labor-intensive and fragile.

Coordinators spending one to three hours a day fielding family calls. Nighttime teams spending one to two hours on family follow-up. Phone tag. Messages left on answering machines. Staff communicating with families while managing a full floor of residents — so the weight of family updates falls on nurses and directors who are already managing the most complex parts of the day.

We also heard something that reframed how we think about this problem: caregivers often carry the weight of knowing so much about a resident's day but have no simple, compliant way to share it. In a regulated environment, there's an unspoken sense that family communication belongs to the nurse or the director — not because caregivers don't care, but because the tools and guardrails to do it safely aren't there. That gap creates a bottleneck that runs straight to the most senior person in the building.

The solution our advisors described wasn't more communication channels. It was lowering the barrier to communication so that the people closest to the resident — the CNAs, the care aides — could share real-time updates without fear, without friction, and without putting their facility at risk.

That's the problem Caily was built to solve.

Lesson 4: "Super Easy" Is Not a Nice-To-Have. It Is the Product.

Across every session, one phrase came up again and again when our advisors described what any successful technology integration in senior living must be: super easy.

This is not a design preference. It is a survival requirement.

Senior living staff are stretched. Ratios are tight. Turnover is high. Any tool that adds steps to an already full shift — even marginally — won't make it into the daily workflow. Our advisors were direct: they had seen vendors come in promising simplicity and deliver complexity. That pattern had made everyone skeptical.

The implication for Caily's product strategy was significant. Features we were excited about — engagement analytics, calendar integrations, detailed activity feeds — were evaluated not by whether they were useful in theory, but by whether they would be used in practice by a care aide on the floor between tasks.

Our advisors helped us draw a sharp line between what belonged in the Minimum Viable Product and what would become "alert fatigue" — a term they used deliberately. The core need, they told us, was HIPAA-compliant messaging with photos. Everything else was gravy until that worked, was adopted, and built trust with staff.

That discipline — ruthlessly protecting simplicity — is one of the most valuable things our advisory board gave us.

Lesson 5: The Buyer, the Approver, and the User Are Three Different People

Perhaps the most operationally important thing we learned from our advisory board was about the buying and adoption dynamic inside senior living communities.

Technology decisions don't follow a simple path. Our advisors estimated that roughly 60–70% of new software or systems are pushed down from a corporate or regional level after leadership research. The remaining 30–40% are pushed up from site-level staff who build a case for a solution. Either way, the decision involves multiple stakeholders with different priorities.

But here's where it gets complicated: even when a system is approved from the top, site-level clinical leaders — particularly Directors of Nursing — have significant influence and, effectively, veto power. If a DON isn't bought in, if the tool adds burden to their team or creates compliance concerns they haven't been reassured about, it won't get used. Full stop. We heard this explicitly: failure to secure buy-in from clinical leadership has killed many technology rollouts that looked successful on paper.

For a technology like Caily, this meant we had to think carefully about who we were selling to versus who we were building for. The executive director might approve the budget. The DON might approve the implementation. The care aide has to actually open the app every morning.

All three matter. All three need different things from us. Our advisory board helped us see that clearly before we built anything — and that visibility is shaping our go-to-market strategy, our onboarding design, and how we think about success metrics.

What Structured Research Makes Possible

None of what we learned above would have come from a one-time survey or a couple of introductory calls. It came from structured, recurring conversations with people who trusted us enough to be honest — and from building the kind of advisory relationship where they could tell us when we were wrong.

We learned that our original assumptions about feature priority needed to be reordered. We learned that pricing per resident, not per staff member, is what makes intuitive sense to buyers. We learned that implementation fees are expected and actually signal commitment from the buyer. We learned that the sales cycle involves research, demos, board approval, and a management company review — and that this process typically plays out over weeks, with budget cycles closing between August and October.

We also learned where to show up. Our advisors pointed us clearly to LeadingAge, to regional state associations, to intimate local events and informal "huddles" where trust is built person-to-person — because that's where decisions in this industry are actually made.

Caily was built on this foundation. Not on assumptions. Not on what we thought senior living needed. On what the people living and working inside it told us, directly and honestly, before we built a single feature.

That's the only way we know how to build something worth using. Learn more: www.Caily.com.