Home / Client Stories / Credentialing Platform Modernization
Flagship Client Story · Legacy Modernization

From a one-star app to a platform

A PE-backed healthcare credentialing company runs access control for hospitals nationwide — 100,000+ medical device and pharma reps credentialed, badged, and checked in at hospital doors. The product worked. The technology didn't: a 20-year-old server-rendered web app, and a mobile "app" that was the website in a webview — rated 1.0 on Google Play, with no iPhone version at all. We rebuilt the experience and the architecture underneath it.

The starting point

A good business trapped in old technology

The domain is demanding: hospitals require every visiting sales rep to be credentialed — background checks, policies, certifications — before entering. Reps check in at kiosks with QR codes and badges; subscriptions gate access; compliance is continuous. The company had won this market with a platform built two decades ago. Three forces made "keep patching it" impossible.

1 · The users had voted

The mobile app was the website wrapped in a webview — slow, awkward, and unloved. A 1.0 rating on Google Play, and no iOS app at all, for a product whose primary users live on their phones between hospital visits.

2 · The owner had plans

The PE firm behind the company was acquiring complementary businesses that needed to integrate. A 20-year-old server-rendered monolith had no clean way to let anything connect.

3 · The vision had changed

A new CTO arrived with a platform vision: the product shouldn't just have an app — it should expose its capabilities so acquisitions, partners, and future products could build on them.

Before · Google Play
☆☆☆☆
1.0 rating · a webview wrapper around the website
no iOS version existed
After · both stores
★★★★★
Native React Native app, mobile-first design
iOS and Android, one codebase

Star visual illustrative — the 1.0 "before" rating is the real, painful number.

What we built

New front doors, and a backend that finally has an API

The rebuild ran on two tracks: a React Native mobile-first experience (plus modern web) for every persona, and a backend transformed from page-renderer into an API platform.

React Native app iOS + Android · mobile-first reps: credentials, QR, expirations Modern web app company managers · facilities dashboards, rosters, invoices, scans Kiosks & badges QR / RFID check-ins at hospital entrances & zones Acquired companies & partners — integrating through the same APIs API-first backend platform one API surface serving every client — apps, web, kiosks, and integrations alike The domain engine, preserved and strengthened credential packets per facility & health system · subscriptions · multi-tenant · scans & audit history
The old app rendered pages; the new backend serves capabilities. Every consumer — including future acquisitions — speaks to the same API.

Mobile-first, because the users are

A rep's real workflow happens in parking lots and lobbies: check what's expiring, upload a document, pull up the QR code at the kiosk. The new app is designed around those moments — not a desktop site squeezed into a phone.

Two decades of domain logic, kept

The rebuild honored what made the product win: credential packets per hospital's rules, subscription gating, kiosk scan flows, multi-tenant operation. We modernized the delivery, not the hard-earned business rules.

Designed for the roadmap, not just the release

The API surface is the PE thesis made technical: every acquired company that needs to integrate now has a front door instead of a fork of the codebase.

The outcome

The product the business already deserved

100k+
vendor reps served by the new experience
2
app stores — up from one, badly
1
API surface for apps, web, kiosks & integrations
20 yrs
of domain logic carried forward, not thrown away
Modernization isn't a rewrite for its own sake. It's giving a proven business the technology its next decade requires — without breaking the decade that got it here.
Why the domain engine survived and the webview didn't

Client identity withheld under confidentiality; diagrams recreated for publication.

What this means for you

The same work, productized

Partnering with a new CTO on the modernization strategy — what to rebuild, what to preserve, and in what order.
Fractional CTO & Technology Leadership →
Replacing a 20-year-old server-rendered app — mobile-first React Native, modern web, without losing the business rules.
Workflow Modernization →
An API-first platform ready for M&A integration — the architecture matching the investment thesis.
Operational Intelligence Assessment →

Is your best product stuck in its oldest code?

Legacy modernization done right keeps the business logic and replaces everything holding it back.

Book a Strategy Call