Why it dies

It dies because it's four products wearing a trenchcoat and calling itself a platform. Triage, chronic scheduling, reconciliation, and a caregiver sheet are four different sales, four different buyers, four different failure modes — and you're shipping all of them to operators whose entire business model is squeezing pennies out of a phlebotomist's petrol. These people didn't skip building a 'brain' because they lacked the vision; they skipped it because a coordinator working from memory costs ₹20k a month and never asks for an API. Your 'no regulatory friction' firewall is the tell: the moment your layer returns 'no visit needed,' you've made a clinical triage decision and dressed it in a coordinator's clothing — a regulator will not admire your architecture diagram. And there's no founder edge anywhere in this — anyone with a health-tech pitch deck and a Gemini key could narrate this exact paragraph, which means the incumbents with the actual patient data and the actual phlebotomists will build the boring version first.

What would save it

Kill three of the four features and become the chronic-scheduling engine for exactly one operator type — a diabetes/dialysis-heavy homecare agency — where 'we turn your one-off visits into predictable recurring revenue' is a painkiller with a rupee figure attached, not a philosophy. Prove one operator will pay for that recurring uplift, get depth into their booking stack so you're not a weekend clone, and only then earn the right to add the caregiver sheet as the retention hook. Ditch the 'decides what happens next' framing entirely — that's the sentence that gets you a regulatory letter, not a Series A.