Home/Services/Home care software
Home Care Software Development
Off-the-shelf home care platforms handle the basics. What they don't handle is your agency — your payer mix, your scheduling rules, the report your state wants every month.
What we build
Scheduling and caregiver matching
Match caregivers to visits by qualifications, client preferences, availability, language, and drive time.
Caregiver mobile app
Check-in and check-out, task lists, care notes, and offline capture that syncs when the signal returns.
EVV
Build visit verification into your platform and submit to your state's aggregator. How EVV integration works.
Care plans and assessments
ADL and IADL assessments, care plan templates, and revision history.
Billing, payroll, and authorization tracking
Track authorized units against delivered units, flag expirations, and feed clean data to payroll.
Family portal
Let families see visit history, care notes, and schedules without calling the office.
Compliance reporting
Pull the records an auditor asks for, without a week of spreadsheet work.
Integrations
EHR, payroll, billing, and state aggregators.
The parts of home care that are genuinely difficult
Most home care software demos look the same. The differences show up in production.
- Matching the right caregiver — qualifications, gender and language preferences, client history, drive time, and a narrow availability window
- Covering call-outs before the shift starts, which is a daily fire drill at most agencies
- Overtime and travel-time rules that change at the state line
- Authorization tracking: what's authorized, what's been used, what expires next month
- Billing across Medicaid waivers, private pay, insurance, and VA benefits on the same client roster
- Keeping visit records clean enough to survive an audit two years later
If your current system handles all of that without a spreadsheet, you probably don't need us. If it doesn't, that's usually why agencies call.
Built for PHI from the first commit
Home care software touches protected health information, so HIPAA applies from the first line of code. We sign a BAA before we touch any data, and we build the audit trails, access controls, and encryption into the foundation rather than bolting them on later.
If you bill Medicaid, EVV is a separate requirement with its own state-by-state rules.
Straight answer on experience
Our care systems are built and running with operators in China. We're early in the US market, and we'd rather say so up front than have you find out later. What carries over is the operating logic; what we'd learn from you is your state's specific rules.
Three ways to work with us
Build from scratch
You have an operating model and no system that fits it. We design and build the platform.
Extend what you have
You're on an off-the-shelf system that's mostly right. We build the missing piece and connect it.
Add a team to yours
You're a healthtech company with a roadmap and not enough engineers. We join your process and your repo.
What we build with
- Vue and React on the front end
- Java on the backend
- MySQL and PostgreSQL for data
- React Native for cross-platform mobile, with native modules where location and offline sync demand it
- AWS, Azure, or GCP, deployed on HIPAA-eligible services under a signed BAA
- REST, FHIR, HL7, and SFTP file exchange for integrations
How a build runs
- Discovery — we map your workflows, payer mix, and reporting obligations before proposing anything
- Scoping — a written scope with milestones, not an open-ended hourly block
- Build — two-week increments, with something you can click on from the first one
- Launch — with the compliance and reporting pieces already in place
- Support — ongoing, or a clean handoff to your team with documentation
Time zones. Our team works on UTC+8. European mornings overlap with our afternoons, and US East Coast mornings fall in our evening. Both are scheduled deliberately. We run async by default — written specs, walkthrough videos, a shared chat channel.
Systems we've built
We can't show you client logos. Most of our work so far has been for care operators in China, and those clients haven't agreed to be named.
- A home care operations platform covering scheduling, caregiver mobile check-in, billing, and family communication, used by 300+ caregivers across 6+ locations
- A senior living operations system covering care plans, staffing, and compliance reporting
If seeing it matters — and for a first engagement it should — we'll walk you through the actual product on a call. Screens, workflows, and the parts we'd build differently now.
Common questions
Can you work with our existing platform?
Often, yes. Send us what you're running and we'll tell you honestly whether extending it costs less than replacing it. We'd rather tell you it isn't worth the money than sell you a rebuild you don't need.
Do you sign an NDA and a BAA?
Yes to both, before any work starts.
Who owns the code?
You do. Full IP assignment on delivery.
How long does a build take?
A focused module usually runs 6–10 weeks. A full platform is a 6–12 month engagement. You get a written estimate with milestones after discovery, before you commit to anything.
What happens after launch?
Either an ongoing support agreement or a documented handoff to your internal team. Your choice, agreed in the contract rather than negotiated later.
Have you worked with US home care agencies before?
No. Our care systems are built and running with operators in China. What carries over is the operating logic — scheduling constraints, authorization tracking, visit verification, caregiver adoption — and the engineering around it. What doesn't carry over is your state's specific rules, and we'd rather learn those from your team than pretend we already know them.
Tell us what your current system can't do.
That's usually the whole conversation.