When It Finally Felt Real

When I started MyUPP on 2026-06-06, I knew enough to know I was in over my head.

That is not false modesty. I am a 50-year-old non-technical person trying to build a national physician credentialing platform with AI. The kind of thing that, in the real world, involves hospitals, payers, credentialing specialists, physicians, documents, trust, compliance, security, and a lot of people in conference rooms using acronyms.

And there I was, sitting with an AI app builder, trying to make something called a Universal Provider Passport.

The idea was simple to say and enormous to build: reduce physician credentialing from 90 to 180 days down to days. A provider should be able to keep one trusted passport of their information and reuse it across hospitals and payers instead of starting over every time.

Simple sentence. Massive mountain.

At first, the project felt like fog. Every time I looked at it, it got bigger. Provider portal. Hospital portal. Payer portal. Credentialing specialist portal. Documents. Verification. Login. Permissions. Data. A real database. Eventually document reading, maybe even a public marketing site.

I remember thinking, this may be the moment I discover the limit of this whole AI building thing. Not because the AI was useless, but because I didn’t know how to think small enough.

That was the first breakthrough.

Not a screen. Not a button. Not some dramatic moment where music played and everything worked.

The breakthrough was scope.

I had to stop trying to build the whole future of physician credentialing in one pass. I had to pick a V1, which is a fancy way of saying: the first usable version, not the final dream.

For MyUPP, that became Provider Passport + Credentialing Engine.

That decision changed everything.

Suddenly, the project had a spine. The provider needed a place to manage their professional identity. The system needed a way to organize and support credentialing activity. The other portals still mattered, but they didn’t all have to be fully alive on day one.

That sounds obvious now. It was not obvious to me then.

My natural instinct is to keep adding. If the idea is good, I want the whole idea represented. But software, I am learning, punishes that kind of enthusiasm. It wants choices. It wants edges. It wants you to say, “Not yet,” even when you really want to say, “And also this.”

The second breakthrough was visual.

We landed on what I started thinking of as a “Clinical Trust” feel: deep navy and medical teal. That may sound like a small design choice, but it made the thing feel less like a toy.

For healthcare, the look matters. It can’t feel flashy. It can’t feel casual. It has to feel calm, organized, and serious without being cold.

Once that visual direction appeared, I could imagine a physician actually signing in. I could imagine a hospital user not immediately closing the page. That was the first time MyUPP felt like it belonged in the world it was trying to serve.

Then came the more intimidating pieces: a real Supabase backend, email and password login, Google login, and something called RLS.

RLS stands for Row Level Security. In plain English, it means people should only see the information they are allowed to see. In a project like this, that is not a nice extra. It is the whole ballgame.

I did not suddenly understand all the technical details. I still had moments where I stared at the screen and wondered if I had accidentally built a very attractive filing cabinet with no locks.

But when the app started having real sign-in, real data structure, and the beginnings of proper separation between users, something shifted in me.

It was no longer just a mockup.

It was no longer just me describing an idea to the AI.

It was becoming a real system.

That was both thrilling and terrifying.

Because when something starts feeling real, the excuses get thinner. You can’t hide behind “this is just an experiment” quite as easily. You start seeing all the responsibility attached to the idea. Especially in healthcare, where trust is not decoration. It is the product.

I still do not know if I can build the full version of MyUPP. I know the scope is huge. I know there are later phases like document OCR, where the app could read uploaded documents, and a marketing landing page to explain the platform to the world.

But I also know this: the project stopped being a blob.

It has a first version. It has a look. It has a real backend. It has login. It has the beginnings of rules around who sees what.

For a non-technical builder, that is a pretty big click.

Small takeaway: Sometimes the breakthrough is not building more. It is finally deciding what comes first.