Before a provider can bill an insurer, the insurer has to approve them. At Beeline, a credentialing and billing company for US providers, those approvals lived in a workbook: one row per provider per insurer, a color for status, a date somebody typed by hand. Nobody could say which applications were waiting on the team and which were waiting on the insurer. Follow-ups happened when someone remembered.
So I built the system its team works in every day. Since June 2026 it has held 250 clients and 2,042 insurer applications, and it screens every morning against the US government's list of excluded providers, all 83,665 rows. The full account, including what broke, is in the Beeline case study.
How I work with a billing company
- A review first. I sit with the people who do the credentialing and follow-up work, list every tool and sheet the work runs through, and count where the hours go. You get a written report, and if a tool you can buy does the job, it says so.
- Running it. Most of the value is in using the system every day, not in building it. So I run it with your team: I check it every month, fix what breaks, and train new people.
- A build, when the review says so. I take one build at a time. A new build starts from my own base, with the record-keeping, the follow-up lists and the finance engine already working.
What stays out
- Patient data. The system runs the work around the claims. The code checks every free-text box for patient details before saving, and every AI request is told to keep them out.
- Claims work. Anything that needs claims or patient records, I decline.
- Passwords in plain text. Insurer portal logins sit in encrypted storage, and the screen hides anything that looks like a password.
The practices you serve
Your clients are practices, and they need to be found. I build fast practice websites with no form that collects health details, and I do search, AI-answer and ads work for them. That work can come through you. The page for medical practices has the details and the prices.
