MyYOUCare lives in fragments. MyYOU makes it one journey visible to staff and youth.
At Y.O.U., youth's wraparound care is scattered across funder-mandated databases that don't talk. The staff who care and the youth whose care is recorded can't see it as a whole.
We designed MyYOU, a thin coordination layer inside the Microsoft 365 the org already runs. It captures care where staff already talk, and lets the youth see their own journey for the first time.
Watch MyYOU work
Problem
No standardized communication
“I told you Bobby was moving in. But I never actually asked you to set up a key card.”
Funder-locked systems
“Funders give us money, they tell us what to do.”
Youth can't see their own journey
A youth's whole journey runs through Y.O.U. Their housing, their goals, their progress, their people. Every worker can see their slice of it. They can see none of it.
Solution
Meet MyYOU
A thin coordination layer that lives inside the Microsoft 365 Y.O.U. already uses. It captures care where staff already talk, turns it into standardized workflows, and gives the youth one journey they can finally read.
Build vs. buy
A coordination layer, not another database
The obvious fix was a CRM. Two problems: it costs $80K–200K a year, and it makes staff type everything twice, which is how their last internal tool died. Building a coordination layer inside Y.O.U.'s Microsoft tenant instead lands the recurring cost near $20K. A tenth of the CRM.
How it works
Youth
A phone-first portal. React on Azure, with text updates over SMS. Where the youth read their journey.
Staff
Power Apps and a Teams bot. Where workers capture care in the flow of conversation — no new tool.
AI + Automation
Copilot Studio reads a worker's note and pulls out the structure. Power Automate runs the cascade once the worker approves. Zero external API calls.
Data
Dataverse holds the record. Field-level access per role, an audit log, and consent flags on every share.
The hardest call wasn't what to build with AI, it was where to keep it out.
AI never touches the youth. It runs only on the staff side, extracting structure from a note a worker chose to write. Every extraction waits for that worker to approve before anything moves.
What I learned
The reframe was the whole job
We were handed a communication problem. The work was realizing the youth couldn't see their own care. Naming the right gap mattered more than any feature we added.
The hardest AI call was where to keep it out
The youth portal has zero AI on purpose. Deciding where AI shouldn't go was a more serious product decision than deciding where it should.
Design for the person who isn't in the room
The youth never sat in our interviews. Designing for someone absent changed every call we made, from the consent model to who the record is written for.