What MyUPP Is Teaching Me
I started MyUPP on June 6, 2026, with an idea that sounded simple when I said it out loud.
A Universal Provider Passport.
One place where a physician could keep their credentialing information, documents, licenses, and professional history ready to share with hospitals and payers. The dream is to help reduce a process that can take 90 to 180 days down to something much closer to days.
That sentence still makes me excited.
It also makes me want to lie down.
Because once I began building it, I understood very quickly that healthcare software is not a cute little app. It is not a weekend toy. It is a huge, serious, tangled thing with many people involved: providers, hospitals, insurance payers, credentialing specialists, administrators, reviewers, and probably several other people I have not fully appreciated yet.
And I am a 50-year-old non-technical person trying to build it with AI.
So, yes. There have been moments where I thought, “Who exactly do I think I am?”
The first lesson: make the first version smaller
At the beginning, I wanted the whole thing.
Provider portal. Hospital portal. Payer portal. Credentialing specialist portal. Document scanning. Marketing site. Everything connected. Everything polished. Everything secure.
The AI could help me imagine all of it, which was both wonderful and dangerous. It is very easy to feel like you are making progress when you are really just making the idea bigger.
The important shift was choosing a V1.
For MyUPP, that means focusing first on the Provider Passport and the Credentialing Engine. In plain English: help the provider build a complete professional profile, and help the system organize what is needed for credentialing.
That is still a big job. But it is no longer the entire ocean.
If I were talking to someone like me, I would say this: your first version is not your failure to dream big. It is your way of staying in the room long enough to build anything at all.
The second lesson: looks matter, but trust matters more
I spent time thinking about the feeling of the platform. We landed on a “Clinical Trust” look, with deep navy and medical teal.
That might sound like decorating. It is not.
In healthcare, people need to feel that the software is calm, serious, and safe. A physician uploading important documents does not want something that looks like a game. A hospital reviewer does not want cute. They want clear.
This taught me that design is not just making something pretty. It is helping someone feel, “This knows what it is doing.”
And honestly, I need that feeling too.
The third lesson: real software has invisible parts
One of the biggest surprises for me has been how much of an app is not what you see on the screen.
There is the database, which is where the information lives. I am using Supabase for the real backend, which means it is not just pretend data sitting on a page.
There is login, including email and password and Google sign-in.
There is something called RLS, which stands for Row Level Security. I had to learn that this basically means making sure people can only see the records they are allowed to see. In a healthcare project, that is not optional. It is the whole ballgame.
Before this, I thought building an app meant building screens.
Now I understand that screens are only the visible part. The trust is underneath.
The fourth lesson: AI is powerful, but it is not a babysitter
The builder can move shockingly fast. It can create structure, suggest flows, build pages, and connect things I would never know how to connect on my own.
But it can also run ahead of me.
That is when I have to slow down and ask: Do I understand what this part does? Is this really needed now? Am I building the next step, or am I wandering into phase five because it feels exciting?
I have learned that using AI does not remove the need for judgment. If anything, it requires more of it.
The AI can help build the house. But I still have to decide what kind of house this is, who it is for, and which room gets built first.
What I would tell someone like me
If you are older, non-technical, and curious about AI, I would tell you this plainly:
You are not too late.
But you will have to tolerate feeling confused.
You will have to ask simple questions more than once. You will have to accept that some days feel like progress and some days feel like fog. You will probably make the project too big at first. You may need to shrink it without shaming yourself.
Start with the smallest useful version. Learn the words as you need them. Do not pretend to understand what you do not understand. And do not let the size of the full dream keep you from building the first honest piece of it.
MyUPP has already taught me that building with AI is not magic. It is conversation, patience, trimming, trying again, and staying humble.
Small takeaway: big ideas need small doors you can actually walk through.
Keep reading
What This Is Really Costing
The obvious cost is AI credits. The less obvious cost is the attention it takes to keep a giant idea from running away with me.
The Color of Trust
I thought choosing colors would be the easy part. Then I realized this project has to feel trustworthy before anyone clicks a thing.
When It Finally Felt Real
The project was too big, too serious, and honestly a little ridiculous for me to attempt. Then the first real shape appeared.
The Day I Made It Smaller
My healthcare app sounded impressive until I saw how much I was trying to build. The turning point was admitting V1 had to shrink.