Objection 01 Someone already gives away a family app
Quiltt ships a free-forever tier including a mobile app for residents, families and staff, unlimited users, no card, no contract. That is the most serious competitive fact here and deserves a straight answer.
Worse, the market leader gives its family portal away entirely. PointClickCare states plainly that Connected Care Center is "available to communities using PointClickCare's Senior Living EHR at no additional cost." You cannot win this category on the words "we have a family portal."
The answer, and it is the strongest fact in this memo: look at what those free products actually are. PointClickCare's is web only — there is no app — it is invitation-gated by staff, it has no photos, and it explicitly excludes narrative care notes, offering structured clinical fields instead. Quiltt's free tier gives families a calendar and a login while gating photos behind $499 a month. Both are portals a daughter must remember to visit, not something that arrives on her phone.
The proof that this is insufficient is that a market has formed on top of the free product. Family CareSpace and InTouchLink sell paid family apps through PointClickCare's own marketplace — customers paying for family visibility that they already receive for free. When people buy something they have been given, the given thing is not the thing they wanted.
Objection 02 The operator will not buy surveillance of themselves
This is the objection an industry insider raised, and it is the sharpest one: "Your biggest obstacle will not be family adoption; it will be facility adoption. Even if the app is free, getting care homes to consistently use another platform will be extremely difficult." A facility has no incentive to buy a tool whose value to the family is verification. It is why every product in this category is sold as wellness, engagement and efficiency, and never as accountability.
The evidence backs him. Across nine companies checked — Papa, Sensi.AI, LifeLoop, SafelyYou, CarePredict, Nobi, Butlr, K4Connect, Cubigo — not one charges families directly. The buyer is always the operator, the agency, or the health plan. The family is permanently the user and never the customer, which is exactly why the family tier is where investment goes to die.
The answer is the segment itself. In a four-bed home the person doing the logging is the owner, and is also the person the daughter rings on a Sunday. There is no principal and no agent, so there is nothing to be caught doing. The adversarial dynamic that kills this product at ninety beds simply does not exist at four, where a daily note is the operator's own marketing — the thing that keeps a family recommending them and their beds full. This is not a smaller version of the enterprise sale. It is a different sale, and the only one where the incentives point the same way.
Objection 03 A free tier does not reduce the legal obligation by one line
This one is settled, and worth stating flatly because the hope is so tempting. The federal definition of a business associate turns entirely on function — whether you create, receive, maintain or transmit protected health information on a covered provider's behalf. There is no payment, price or contract term anywhere in it. A free product that stores resident notes is a business associate on identical terms to a $500-a-month one, and the government's own cloud guidance says the obligations apply "regardless of whether it has executed a BAA."
The answer: the escape route is real but narrow. A home is a covered entity only if it transmits health information electronically for a billing-type transaction, so a purely private-pay home may sit outside HIPAA — legitimately, not as a loophole. But it flips the instant one Medicaid-waiver resident arrives or one electronic eligibility check runs, retroactively, for data already held. The right move is to sign the agreement anyway: it costs nothing at AWS, Google Cloud or Azure, and you cannot become a business associate by accident if you have already agreed to behave like one.
Objection 04 Free in healthcare has a body count — and a modern version
Practice Fusion gave away a free electronic health record, reached enormous scale, monetised it through sponsored clinical alerts, and paid a $145 million settlement. Free distribution was not the crime; the monetisation design was.
The 2026 version is sharper and lands directly on free tiers. The FTC's Health Breach Notification Rule was amended in 2024 so that a "breach of security" now expressly includes an unauthorised disclosure, not merely an intrusion. An analytics SDK or advertising pixel that leaks resident data is a reportable federal breach with no hacker involved — at roughly $53,000 per violation, per day. And a free tier is precisely the product somebody instruments for growth analytics.
The answer: two rules, both absolute. Never take money from a third party in exchange for influencing what a caregiver sees or does. And keep every analytics, attribution and advertising SDK away from anything touching a resident. Charge instead for organisational scale — multi-site, FHIR export, population reporting, SLAs, admin controls. That is the entire difference between the Vercel analogy and the Practice Fusion one.
Objection 05 A standing family feed is not a permitted disclosure
The rule allowing disclosure to family involved in someone's care is scoped to information "directly relevant to such person's involvement," and it is built around a contemporaneous act of professional judgement. An automated daily feed is not scoped by a person — it is scoped by a cron job, and you cannot exercise professional judgement at 3am via webhook. Photographs make it worse: a full-face image is itself an identifier, so photos cannot be de-identified by stripping names.
This is not theoretical. Cadia Healthcare paid $182,000 in 2025 for using residents' photos and health information without proper authorisations across five facilities. Holy Redeemer paid $35,581 for disclosing a full record when the authorisation covered a single test — which is the exact failure mode of an over-broad family feed.
The answer, and it is cheap: build a signed authorisation into admission that names each recipient, states what they receive, carries an expiry, and can be revoked in-app with access dying instantly. That is a few days of engineering, and it does more than paper over the problem — the minimum-necessary standard does not apply to disclosures made under an authorisation, so it removes the scope question rather than arguing it. For residents with dementia it is mandatory rather than optional: "next of kin" confers no legal authority, and the operator needs a way to suppress a viewer without filing a support ticket, because family members are also the most common elder abusers.