Home care software is one of those categories where the stakes are real, the workflows are complex, and “innovation” only matters if it improves care. In this episode, Jeff sits down with Ken Accardi, founder and CEO of Ankota, to talk about his path from GE Healthcare to building a home care software company—plus what it actually takes to scale a vertical SaaS business in a market shaped by regulation, reimbursement, and human outcomes.
This is a conversation about more than product. It’s about mission, loss, resilience, and building something that matters—while still doing the hard operator work: positioning, go-to-market focus, and sustained execution.
Home care software and the reality of vertical SaaS
Vertical SaaS is often described as “easier” because the niche is defined. In practice, it’s the opposite: the niche is defined, but the edge cases are endless.
Ken shares what it means to serve an ecosystem that includes:
- caregivers and care coordinators,
- agencies trying to stay compliant and staffed,
- patients and families navigating difficult moments,
- and payers with strict requirements.
Scaling home care software means you can’t just build generic CRM features and call it a day. You have to earn trust in the workflow. You have to understand the language, the incentives, and what “success” looks like for each stakeholder.
Medicaid vs private-pay: two markets, different pressures
A key part of the episode is the difference between Medicaid and private-pay dynamics.
The same software may serve both—but the buying process, pricing sensitivity, reporting requirements, and operational urgency can feel like entirely different worlds. That affects:
- your ICP definition,
- your messaging,
- your onboarding and support model,
- and your product roadmap.
For operators, this is where go-to-market discipline shows up. The more clearly you segment the market, the more you can tailor the promise and the proof. And in vertical SaaS, proof often looks like outcomes, not features.
Go-to-market focus: refining the story as you grow
Ken and Jeff discuss the ongoing work of refining go-to-market strategy as the company evolves.
Early on, founders often try to serve too many use cases at once. But scaling home care software usually requires sharper focus:
- a clear wedge (the first job you do better than anyone),
- a repeatable buyer journey,
- and a sales motion that matches the customer’s reality.
That can mean simplifying the story. It can mean saying “no” more often. It can also mean choosing which customers you’re building for right now—so you can deliver reliably and compound trust.
AI in caregiving: where real value is starting to appear
AI is everywhere, but this conversation stays grounded. The question isn’t “how do we add AI?” It’s “where can AI create real value without adding risk or noise?”
In caregiving and care management, AI value often shows up in practical places:
- reducing documentation burden,
- surfacing insights from messy notes,
- helping teams triage and prioritize,
- improving coordination across care plans.
If you’re building home care software, the bar is high: reliability matters, privacy matters, and workflows can’t break. The best AI use cases are the ones that make caregivers’ lives easier and help agencies deliver better outcomes—without requiring a huge behavior change.
Building something that actually matters
The heart of the episode is Ken’s founder journey: the losses, the lessons, and the drive to build something meaningful.
In healthcare, the mission can’t be marketing copy. Customers feel it when the company understands the work—and when it doesn’t. That’s why durability and empathy become strategic advantages, not just personal values.
This episode is a reminder that scaling isn’t only about growth curves. Sometimes it’s about building a company that can carry responsibility—and keep showing up.
Key takeaways
If you’re building in healthcare or vertical SaaS, here are a few takeaways to consider:
- Pick a wedge use case and win it deeply before expanding.
- Segment Medicaid vs private-pay clearly in your messaging and sales motion.
- Treat trust and workflow fit as core product requirements.
- Use AI where it reduces burden and increases clarity—not where it creates novelty.
- Keep returning to the mission, especially when the operator work gets heavy.
Related episodes from Agile Operator If you’re thinking about durability and execution pressure as you build, these two episodes connect well:
- The Discipline of Scale: Specialization, Trust, and the Discipline of Scale https://agile-operator.com/specialization-t…e-of-scale/
- Launching, Leading, and Scaling When the Margin for Error Is Thin https://agile-operator.com/launching-leadin…or-is-thin/
Ken Accardi: www.linkedin.com/in/accardiken/
Ankota: https://www.ankota.com/
Follow Agile Operator: https://agile-operator.com/newsletter/
