Nia
Nia, 18. In licensed care, Miami. Six months pregnant. Her case closes in the spring, a few weeks after her due date.
This is an illustrative account. Every detail is invented.
Watch
Full case
Situation
Nia is 18, in licensed care in Miami, six months pregnant, and finishing her senior year. Her case is scheduled to close in the spring, a few weeks after her due date. She has Medicaid through the child welfare plan and no idea whether it follows her out the door, or what she's supposed to have lined up for a newborn.
Why this case matters
This is the aging-out case, and the one with a second person in it. Everything Nia has today comes through being in care. On the day her case closes she becomes a former foster youth, a new mother, and a Medicaid question, all at once. The argument is that the product carries the safety net across that line, from the assessment alone, before anyone has to fill in a form.
The feature she used
The assessment. Nia's profile is almost empty, on purpose. Everything the product knows about her came from one assessment. From that alone: coverage for her baby from the day they're born, Healthy Start, where someone comes to her home from now through the baby's first year, Healthy Families, longer-term support at home, and WIC, starting now, not after the birth. She asked Lexi the question keeping her up: does my Medicaid stop when my case closes? The answer was that it doesn't have to, followed by the part that matters: don't assume it switches over by itself. Confirm it with your caseworker before your case closes.
What changed
Five weeks of Nia checking in with herself, in the Wellbeing space. Not a crisis. Sleep. School. Money. "The baby." A note that says "talked to Ms. R about the spring, felt better after." A few breathing sessions. It's hers, and nobody sees it unless she chooses to share it. Her plan opens on one step: confirm Medicaid to 26 with her caseworker before her case closes.
Said out loud
Nia's case closes a few weeks after her due date. On that day she stops being the state's responsibility and starts being someone's mother. What the product did, from one assessment and no profile, was tell her that her coverage doesn't have to end, that her baby's coverage starts automatically, that a program exists to send someone to her home starting now, and that she should ask about extended care before spring. Four things a caseworker with forty cases might get to. The product got to them the first time she asked.
The federal line
NYTD asks youth at 19 and 21 whether they've had a child. It's on the survey because the federal government already knows what an aging-out pregnancy does to every other outcome it tracks: housing, employment, education. The supports for her are federal and they already exist. Medicaid continues to 26 for former foster youth under the Affordable Care Act. Twelve months of postpartum coverage is a federal option Florida adopted. Home visiting is federally supported. The baby's coverage from day one is federal Medicaid rule. None of it requires a new program. It requires that Nia knows on the day it matters, and that the confirmation happens before her case closes rather than after her coverage lapses. The product's whole job here is the timing.
Honest note
The health assessment doesn't ask whether Nia is in school, so the product can't yet see that extended foster care may fit her, which could be the most consequential support for her. That fix is small and it's next.
How her information is protected
- She owns it. U Navigate is not the state's system of record. Her account is hers. Nothing about her is shared with a caseworker or anyone else unless she chooses to share it.
- The record can't be rewritten. Her Journey Record is append-only. Entries can be added. They cannot be edited or deleted after the fact, by her or by us.
- Every row is locked to her. Database access is enforced row by row. A request for her data returns her data only, even if our own code has a bug.
- What the AI is given, exactly. Lexi knows her first name and her state, so she doesn't have to repeat herself. Her last name, email, phone number, address, date of birth and account identifier are never sent to any AI provider from her account, and an automated test fails our build if that changes. A document she chooses to upload is different, and the next line says how.
- When she uploads a document, the AI reads it. That's how Lexi summarizes a lease or finds a deadline on a form. The document is hers, the summary is hers, and neither is used to train anything.
- No ads. No data sales. Ever.
- What isn't done yet. We don't yet have a Business Associate Agreement or a zero-data-retention commitment from our AI provider. Until we do, we tell agencies that plainly and don't accept HIPAA-covered data.
Engineered by co-founder Shane Cupid.