I take repetitive work off small medical billing teams.
I work with billing companies whose staff spend too much time on recurring checks, like rechecking coverage and tracking authorizations. Together we choose one workflow, and I build and run a four-week pilot with human review, measured against how your team does it today.
Bring one recurring task. Afterward I'll send a short written recommendation, including whether your current tools can already handle it. You don't need to share patient data or commit to anything.
Gadi Cohen, founder. I build software for medical billing case work. More about me
| Claim | Payer | Service | Days outstanding | Status | Next step |
|---|---|---|---|---|---|
| SYN-20418 | Ridgeline Health | 90837 | 38 | Waiting on payer |
Portal shows claim received. Check again for adjudication. |
| SYN-20433 | Tallgrass Medicaid Plan | 90791 | 64 | Waiting on payer |
No change after two portal checks. Check clearinghouse for a payer response. |
| SYN-20456 | Corwin Mutual | 99214 | 41 | Denied | Timely filing denial (CO-29). Pull clearinghouse acceptance report for the appeal. |
| SYN-20471 | Alder Valley Health Plan | 90834 | 29 | Waiting on payer | Payer asked for treatment notes. Sent; confirm they were received. |
| SYN-20502 | Bluewater Mutual | 97110 | 57 | Denied | Missing modifier (CO-4). Add GP modifier and resubmit after biller review. |
| SYN-20519 | Tallgrass Medicaid Plan | 90837 | 33 | Waiting on payer | Coverage ended before the date of service. Ask the practice for current insurance. |
| SYN-20527 | Ridgeline Health | 90832 | 46 | Waiting on payer |
Portal says in process. Recheck in 7 days. |
| SYN-20540 | Hollins County Health Plan | 90847 | 22 | Waiting on payer | Under 30 days. First status check is scheduled. |
This is a synthetic example of the kind of work a pilot could cover. The claims, payers and reference numbers are made up.
Problems worth looking at
- Staff recheck the same patients' coverage every month. We'd look at running those checks on a schedule and flagging only the changes.
- Authorization dates and remaining units live in spreadsheets or several systems. We'd look at reconciling them and surfacing the ones that need attention before they lapse.
- Benefits for a new patient take several portals or a call to piece together. We'd look at producing one checked result where your team already works.
- Claims get revisited without a clear next step. We'd look at preparing the follow-up with the supporting details attached.
These are examples. The starting point is whatever is taking your team's time.
What I do
I start by looking at where your team's time goes. Together we pick one workflow that's repetitive and easy to measure.
Then I build the automation for that workflow and run it with human review. Anything that needs judgment, such as an appeal, a write-off or a payer response that isn't clear, comes back to your team with the details attached.
We agree on the review and escalation rules for each pilot before it starts. I work in the systems you already use, and your team keeps the client relationships.
How a pilot works
-
Step 1. A walkthrough of your workflow
On a free 20-minute call, you walk me through one recurring task and how it's done today. Afterward I send you a short written recommendation. I don't need any patient data for this call.
-
Step 2. A four-week pilot on one workflow
We agree in writing on the workflow, a cap on volume, what counts as done for each item, the review and escalation rules, the one measure the pilot is judged on, and a fixed fee. I sign a business associate agreement (BAA) before I see any patient data. Then I run the pilot for four weeks.
-
Step 3. Results against your current process
At the end, I compare the pilot's numbers with how the same work ran before. You decide whether to continue. You'll already have an estimate of the ongoing price from before the pilot, and I confirm it in writing if you go ahead.
Who does what
I handle the setup and the day-to-day work. That means building the automation, running the pilot, looking into any problems and reporting to you every week.
On your side, you provide one person who owns the process. They explain how the work runs today and arrange the access we agree on. Before we start, we agree on how much of your team's time the pilot needs.
Founding partner pilots
My first pilots are founding partner pilots. As a founding partner, you get:
- A reduced fixed pilot fee, which we agree on after we scope the work.
- Direct access to me, the person building and running the service.
- A service shaped around a real recurring problem in your business.
- A results report every week, and a clear point to stop after four weeks.
- An estimate of the ongoing price before the pilot starts, so there's no surprise if it works.
In return, I ask for enough access to understand the process and a short feedback call each week. If the pilot works, I may ask you to be a reference.
What you see each week
During the pilot, you get a short report every week. Here's a sample from a claim follow-up pilot. The measures in the report depend on the workflow we choose.
Subject: Week 2 of 4, claim follow-up for Lakeside Counseling Group
| Claims worked this week | 112 |
|---|---|
| Paid | 33 |
| Corrected and resubmitted, awaiting payer response | 8 |
| Awaiting payer response, with a next check date | 52 |
| Sent to your team | 19 |
Sent to your team
11 need your decision on an appeal or a write-off.
6 need current insurance information from the patient.
2 had a payer response I wasn't sure how to read, so I didn't act on them.
Corrections
None this week. Anything your team flags is listed here with what I changed.
Who you'd work with
Queuelight is me for now, so you'd work with me directly.
Gadi Cohen
I've spent the last few years building software that works medical billing cases. Most of that work is checking claim status and eligibility on payer portals, reading EOBs, and deciding which items the software can close on its own and which need a person to look at them. I started Queuelight to do that work directly for billing teams. Before this, I worked on voice automation for patient calls at Assort Health and on disinformation detection at Blackbird.AI.
Questions
Do you need access to patient data?
Not to get started. The walkthrough and the pilot scoping don't involve any patient data. Before a pilot touches patient information, I sign a business associate agreement (BAA) with you, and the work runs in a setup covered by that agreement.
Will you contact my clients?
Your client relationships stay yours. I won't solicit your clients, and any operational contact requires your approval. I'll put that in writing.
What access would you need?
It depends on the workflow. Usually it's a user account in the systems where the work happens, such as your practice management system or clearinghouse, for the client in the pilot. Your team creates the accounts, so you can see what I do and turn access off at any time. We settle the exact list during scoping.
What does the pilot cost?
It's a fixed fee for the four weeks, reduced for founding partners. I set it in a written proposal once we've scoped the workflow together. The proposal also gives an estimate of the ongoing price.
What happens if it doesn't work?
The pilot ends after four weeks, and nothing commits you beyond that. I hand back every open item with a note on where it stands. The weekly reports mean you'll see how it's going well before the end.
If a recurring task is taking up too much of your team's time, bring it to a 20-minute call. Afterward I'll send you a short written recommendation.
You can also email me at hello@queuelight.com.