One login to run
your whole practice.

The plan was credentialing.

A single job, done well: get a provider's documents into GiggEx and out to the hospital's credentialing portal, without the busywork.

The first build was focused entirely on credentialing. A provider uploads their license, CV, immunizations, and references one time. GiggEx reads them, sorts them, structures them, and pushes them out to the hospital's MD App portal — then watches for changes and keeps both sides current.

That work is real, and it's running today. It is the backbone of the August 12 demo. But the last conversation made one thing clear: credentialing was never the whole product. It was the first spoke of something much larger.

Fifteen logins to run one career.

It isn't that credentialing is hard. It's that everything lives in a different system, and none of them talk to each other.

So the direction sharpens. GiggEx becomes the hub. Every outside system becomes a spoke. You connect each one once, and from then on GiggEx is the single place you work. The other systems stay live — when you change something in GiggEx, it changes there too. Nothing gets thrown away. Everything gets easier.

The systems every provider juggles.

This isn't a GiggEx problem or a TidalHealth problem. It's the whole industry. A working clinician touches a dozen of these — each its own login, each its own password, none of them talking to the others.

It's worse than it looks

Even the same system doesn't talk to itself. Each hospital runs its own separate copy of MD App — so credentialing at Summit and credentialing at Mariah Parham are two different logins that never sync. You do the same work twice. And CAQH, the one national database every insurer already shares, still makes you log in and re-confirm your profile every 120 days or your paneling quietly lapses. The fragmentation isn't a bug in one product. It's the water every provider swims in.

GiggEx sits above all of it. When you update your work history once in GiggEx, it flows to every connected MD App instance, every schedule, every payer profile — at the same time. One change, everywhere it needs to go.

The hub, and its spokes.

You work in one place. GiggEx quietly keeps every connected system current — in both directions.

The Connect button.

One control turns a pile of disconnected logins into a single cockpit. Four steps, done once.

Behind the scenes, GiggEx connects one of two ways. Where a system offers a clean data connection, GiggEx plugs straight in — fast, stable, never breaks. Where a system doesn't, GiggEx logs in the same way a person would: a real browser, a real login, clicking through the pages to read and write what's needed. Either way, you never see the machinery. You just see one place that works.

A promise we keep

Your passwords are used to make the connection and are never stored. Same rule as the credentialing portal. GiggEx holds the keys only for the moment it needs them, then lets them go.

Five spokes, and counting.

Each connection is a self-contained piece — built once, reused everywhere. A Lego.

Where we go, in order.

Ship what's proven first. Build the big idea on top of it. Never bet the demo on something half-built.

How the dollars move.

Invoicing and payment distribution are already part of the finished product you see on the GiggEx site — weekly pay periods, line-item invoices, overtime breakdowns, and the deposit view. Here's how the real money flows through it.

How it's priced.

Simple, and it scales with the work. The base covers the platform; connectors are priced by how hard they are to build and keep running.

The logic is honest: a native data connection almost never breaks, so it costs little to keep. A browser-based connector can break when a site changes its layout — and repairing it takes real time. Price follows effort, nothing else. As more connectors come online, the value compounds: every provider on GiggEx gets the full set.