The Color of Trust

When I started MyUPP on 2026-06-06, I knew the idea was too big for my skill level.

A Universal Provider Passport is not a little hobby app. The dream is to help cut physician credentialing from something like 90 to 180 days down to days. That means doctors, hospitals, payers, and credentialing specialists all touching the same system in different ways.

For a 50-year-old non-technical person building with AI, that is a very bold sentence to type.

There were plenty of technical decisions I did not fully understand at first. Logins. A real database. Different portals. Security rules that decide who can see what. But the design decision I obsessed over more than I expected was much simpler on the surface:

What should this thing feel like?

Not what should it look like in a trendy way. Not what color would make it pop. I kept coming back to one phrase: Clinical Trust.

That became the visual direction. Deep navy. Medical teal. Clean screens. Serious, but not cold. Modern, but not flashy.

I probably spent too much time thinking about it. There were moments when I caught myself staring at the screen, wondering if I was avoiding harder work by fussing over color. Maybe I was, a little.

But I also knew this was not a recipe app or a travel planner. MyUPP is about physician credentials. Licenses. Documents. Verification. Hospitals making decisions. Providers trying not to get buried in repeated paperwork.

If the first impression feels flimsy, the whole idea feels flimsy.

That mattered to me because I am not coming at this as someone with a long software background. I cannot lean on a fancy title. I cannot say, trust me, I have built ten systems like this before. I have to earn trust in smaller ways.

The screen has to say, this is organized.

The colors have to say, this is calm.

The layout has to say, someone thought about the person using it.

At the beginning, the project wanted to become everything at once. Provider portal. Hospital portal. Payer portal. Credentialing specialist portal. Document OCR later, where the system could read uploaded documents. A marketing landing page. A national platform. The whole mountain.

That is when the design decision and the product decision started to blend together.

I had to narrow V1 to the Provider Passport and Credentialing Engine. In plain English, that means the first version should focus on the doctor’s core profile and the basic process that moves credentialing forward.

Even that is a lot.

The multi-portal shell still exists as the structure, but I had to stop pretending I could perfect every doorway at once. The design needed to help me stay disciplined. Deep navy and teal became less about decoration and more about keeping the project anchored.

When I felt overwhelmed, I could ask: does this screen support Clinical Trust, or am I adding clutter because I am nervous?

That question helped more than I expected.

I still have doubts. I still hit parts where the AI gives me something that looks convincing, and I have to slow down and ask whether I actually understand what is happening. I still worry that I am building something too complex for my own current ability.

But I care about this design choice because healthcare already feels heavy enough. If this tool ever helps someone, it should not add confusion on top of confusion.

It should feel steady.

That is what I wanted the colors and layout to do before the app ever proves anything else.

Small takeaway: sometimes design is not decoration. Sometimes it is the first promise you make.