Problem
A medical-billing company runs three jobs at once: win the next provider, keep the current providers' credentials current, and get paid for the work. Each was living in its own tool, and the riskiest part, anything touching patient health information, kept threatening to leak into ops systems that had no business holding it. They needed one portal for finance, sales, and credentialing that was deliberately built to never become a PHI store, because the cheapest compliance posture is the data you never hold.
Approach
The first architectural decision was a boundary: PHI does not live in the portal, by design, isolated from the surfaces the team works in every day. Inside that boundary, three modules are live. The finance module runs the money side of the business. The sales pipeline tracks providers from first contact to signed. The provider credentialing module tracks each provider's credentials and the dates that matter, so nothing lapses quietly. Zoom is integrated for meetings and for logging inbound calls and events, so the conversation that moved a deal or flagged a credential is on the record next to the work. It is built in modules so the company got working surfaces early instead of waiting for a big-bang launch.
Outcome
Live and in use. Finance, the sales pipeline, and provider credentialing are in production today; the build is roughly half delivered, with the remaining modules shipping over the coming weeks. The PHI-out-of-the-portal posture is holding, which keeps the compliance surface small and the audit story simple. This is the healthcare finance and credentialing recipe, retuned for a billing company's shape rather than a clinic's.
Notes
What's running today
Three modules are live and carrying real work.
The finance module runs the money side of a billing company: the part the whole business depends on. The sales pipeline tracks providers from first contact through to signed, so the next month's revenue is visible before it lands. The provider credentialing module tracks each provider's credentials and the dates that matter, so a lapse is caught early instead of discovered during a claim.
Zoom is wired in for meetings and for logging inbound calls and events. The conversation that moved a deal forward or surfaced a credential question is recorded next to the work it affected, not lost in a separate app.
Decisions I'd defend
No PHI in the portal, by design. This is the load-bearing decision. The portal is built so patient health information never enters it, isolated from the surfaces the team uses daily. The cheapest data to keep compliant is the data you never hold. It keeps the audit story short and the risk surface small.
Ship in modules, not in a big bang. Finance, sales, and credentialing went live as they were ready, so the company got working tools early. The rest lands over the coming weeks, on the same backbone.
What's next
The remaining modules ship over the coming weeks, on the architecture that is already in production. The credentialing and finance shape here is the same recipe the rest of my work runs on, fitted to a billing company rather than a clinic. If you run a billing or credentialing operation that has outgrown its stitched-together tools, reach out.