The Family Operating System Doesn’t Exist. That’s the Problem.

We built world-class systems for companies — but left families to run on group chats, memory, and guesswork. So I tried to fix it.

For the last five years of my mother’s life, she had dementia. It's was an extremely challenging time. If you have lived through something like this with someone you love, then you already understand something fundamental that most people miss: the disease is only part of the problem.

It's the logistics of the disease that's the real challenge. The daily, relentless, impossible-to-track logistics. She'd forget her medications, appointments and conversations we all had just minutes before. Not occasionally — regularly every day.

The home health aides we relied on were doing their best, genuinely, but there was no real system. Medications didn't always get logged. Shift changes meant context got lost. Weekly time tracking - nearly impossible.

One aide would note something in a text. Another would write it on a piece of paper. My family would try to piece together what happened in a given day from a thread of messages and handwritten notes that never quite added up. It was brutal.

The care itself becomes a constant stream of logistics that nobody is really equipped to manage. Medications, appointments, shifts, updates, and bills. Who said what. What changed. What got missed. What still needs to happen...

And when there is no real system underneath it, everything starts depending on memory, goodwill, and improvisation. That was our reality. We were not failing her on purpose. We were trying to solve a systems problem with scraps.

Mapping the Problem, and Minding the Gap

That experience stuck with me because I have spent my career building software. I am a builder. I have worked on products at Snowflake, media platforms at SiriusXM, systems inside major investment banks, and AI tools for numerous startups. It's what I like to do. So when I looked at what my family was going through, I reacted the way product people in tech tend to react when they see a broken workflow.

So, I started mapping the problem. Not as an abstract market opportunity or a pitch deck. As a lived failure in plain sight. Because the more I looked at it, the more obvious it became that this was not just about my family.

Doing my research, I started talking to friends, colleagues, and other people in the middle of life’s most compressed decade: building careers, raising children, and trying to care for aging parents at the same time. And the same stories kept coming back:

• “My dad calls me three times a week asking when his next appointment is.”

• “My mom doesn’t want to bother us anyone, so she says nothing until something falls through the cracks.”

• “I have a shared doc, two group chats, a wall calendar, and somehow I still don’t know whether my kid made it to practice.”

I even learned there is a name for this phase of life. Researchers call it the Sandwich Generation: adults simultaneously caring for children and aging parents. Well, it turns out quite literally tens of millions of Americans are living it right now. For many of us Gen Xers, this is our reality, and a lot of the time "reality bites"  - sorry, couldn't help with the pop culture reference.

Pic courtesy of William Hayes.

The more I thought about it, what struck me was not just the stress. It was the tooling gap. Nobody had ever really built anything for this. Sure, we have enterprise software for finance teams, supply chain systems for supply chain professionals, tools for field operations, ad buying, content production, workforce scheduling, and customer service. We have beautifully optimized systems for companies of all shapes and sizes, and functional roles that run the gamut.

But for families trying to coordinate care across generations, we are still using a pile of disconnected consumer tools and hoping for the best. A calendar here. Notes there. Group texts everywhere. Maybe a caregiver app for one narrow use case, or a spreadsheet. Maybe a paper list on the counter.

The Moment It Became a Product

Sometime things happen for a reason. When I got laid off from Snowflake last year, instead of jumping straight into another role, I decided to use the moment differently. I launched Cloverhill AI, my consulting practice focused on helping service businesses use AI more practically, not as a gimmick or a feature layer, but as a real creative and product-building partner.

I turned my attention to deciding what I wanted to build, and I kept returning to the same thought: Why are families still managing some of the most emotionally and logistically complex parts of life with tools that were never designed for the job? This question gnawed at me and would not leave me alone. It haunted me. Because what my family needed was not another shared calendar. We needed infrastructure. We needed something that could hold context across people, across generations, and across the messy reality of how families actually communicate.

And I kept coming back to the multiple calls a day from my mom and her aides — asking about medications, appointments, bills, things she just couldn't hold onto anymore. And us on the other end, trying to answer, trying to track, trying to coordinate — without the right tools to actually do any of it well.

The more I sat with it, the more I couldn't let it go. What we needed was something that could hold the family together without demanding that the family reorganize itself to use it. Part of the reason nothing exists to solve for this tough use case is historically, stitching together disparate requirements and activities into one coherent product, solution or service would have been exceedingly difficult if not impossible. It was my hunch that recent advances in AI could potentially change the equation.

Right then I knew this was the vision: AI as family infrastructure, not family surveillance. Less noise, less cognitive drag, and not another dashboard. A coordination layer. As a product guy, I knew this felt like a product worth building for me and my family. So I got to work.

AI as Family Infrastructure

Building this solution, which I called Kindora, taught me is that the hard part is not the technology. This is the strange part of this moment. The technology is increasingly accessible. A solo builder can now do things that required a real team not long ago. AI-assisted development has changed the economics of building in a profound way.

But that does not make the product easy. Because the real challenge is not technical. It is behavioral. The issue is families are not companies. There is no org chart. No top-down mandate. No admin pushing adoption. And no quarterly planning cycle where everyone agrees to use the same system because leadership said so.

You have to design for ambiguity, inconsistency, emotion, fatigue, and resistance. You have to make something intuitive enough for the most overloaded person in the system and simple enough for the least technical one.

Every decision I have made on Kindora keeps coming back to the same question:

• Would my mom have been able to benefit from this?

• Would her aide have actually used it?

• Would my wife and I rely on it ourselves?

That is the bar. And it is a much higher bar than most software ever has to clear. But it is what it is.

Rethinking Simplicity

This experience forced me to rethink simplicity. Simple does not mean stripped down. Simple means every action earns its place. Every notification matters. Every workflow reduces friction instead of adding another place to check. Every feature lowers anxiety rather than multiplying it.

As I built the solution. I learned to let things go. I'm not kidding when I say I have thrown away plenty of ideas that were interesting but not useful enough. And I have focused on gathering user testing. My wife and I use it ourselves. That is the test. If it does not improve our daily coordination, it has no business asking another family to trust it.

Wanted: Beta Testers

At this point, I have been building and rebuilding Kindora for more than eight months, and I am happy with where it's going. Now is the point where I think it is ready for others to use, which is why I am writing this. I am looking for beta testers. Not abstract user personas. Not theoretical feedback. Real families, and real caregivers

Specifically, I want to hear from you if you're in one of these situations: Let's say you're managing your parents' health appointments, prescriptions, or logistics from a distance. You've got kids at home and aging parents you're also responsible for. You're the default person in your family who holds all the information, and you're tired of being the only one who holds all the information.

If you're reading this and nodding, I want to work with you directly. Not just to put the app in your hands, but to talk through your actual situation and build something that fits it. Early beta testers will have direct access to me. Their feedback will shape what Kindora becomes.

Right now Kindora works on any device — phone, tablet, or desktop — no app store required. Something you can actually put in the hands of every family member, including the ones who won't download anything new unless it's dead simple.

This isn't a waitlist form that leads nowhere. I'm genuinely building this with people, not for them. I've spent most of my career building products for other people's visions — platforms, analytics tools, AI systems for companies. All good work. Work I'm proud of.

But Kindora is the one I'm building because I couldn't find it anywhere else. And I use it daily. Because my family spent five years piecing together my mom's care from text threads and handwritten notes and the goodwill of aides who were doing their best without the right system under them.

Because 23 million people are doing the same impossible math every week, holding two generations of family together with group texts and sticky notes and sheer willpower. Because someone should build the thing that helps them. Might as well be me.

Mike Vincenzino

If you're in, reach out. Drop a comment, reply to this, or email me directly at mvicenzino@gmail.com. You can also find me at www.mvicenzino.com. Tell me about your family situation — the messier the better. That's exactly the kind of thing I need to hear.

The people holding everything together deserve better tools. Let's build them.