[blastbking]

If the bill is larger than predicted, we end up covering the difference (assuming that the services we showed the user are the ones the user ended up getting). We match the prices shown in the table of 'All Covered Services' that we show to the user, so if you go to a derm to have a mole looked at, it might be $150 for a consultation, and we'll tell you it'll be $70 to have a biopsy done, and if you get the biopsy, we'll guarantee all you owe is $220, and if you don't we guarantee it's $150.

In terms of padding the bill, we think that doctors tend to pad it in order to get reimbursed more by insurance, but they're pretty soft on holding patients liable to these padded things, and also they will get in trouble if they do it too much. We do need to figure out the patient experience though, our goal is that patients know the cost of procedures a doctor is recommending (for ex if my doctor says I should get an arthroscopy and an x ray, I want to know ahead of time how much it costs), and can make an educated decision on whether they want to get the procedure done or want to see a different doctor.

The pricing information, we're likely to publish broad analytics level information, but from a business perspective we're thinking that the discrepancies between the published data and our experiential data are really our 'data moat' for the business, so that's likely to be our IP (as it's what prevents someone from easily copying us by scraping our site). We want consumers to have to go through our site in order to get the pricing info, otherwise if it's just an informational site and people use us to look up pricing then end up going to competitors, we wouldn't be able to financially support the site existing long term.

[darkclouds]

So an insurance hedge for insurance schemes, with an AI as the hook?