Why I built BillComb

I'm a data engineer. My work is reading messy records other people generate and finding the places they don't add up - duplicated rows, totals that don't reconcile, the same thing billed twice under two different codes. So when that bill arrived, I did what I do all day: I asked for the raw data. Not the summary statement with one big number - the itemized bill, every line.

It took six weekends. I learned what a CPT code is, which charges are illegal to bill a patient after an in-network visit, how to catch the same lab run charged twice, and how a "facility fee" can quietly double a number. By the end the $6,214 was $1,900. Nothing about that required a lawyer or a medical degree. It required patience, a few reference tables, and someone willing to read every line.

Most people don't have six weekends. That's the whole problem. The information that gets a bill corrected exists - it's just scattered across statutes, billing manuals, and benchmark rates that nobody hands you while you're staring at a number you can't pay. BillComb is those six weekends turned into software: it reads your itemized bill the way I learned to, and hands you the report and the letter to send yourself.

I built it deliberately small and deliberately honest. Flat fees, never a cut of what you save. Your documents are deleted after your case closes, never sold, and never used to train models. The free scan tells you the truth - how many red flags, and roughly how much is at stake - before you pay a cent. If BillComb is wrong, you get a full refund without asking.