That's a cool idea. If you combined it with a Coin style card that allowed you to switch cards on the fly you could not worry about blowing your budget.
Any light on how to pull back once a change has been deployed? If it's version controlled you can check out a previous version but do you automate tht?
I've created dozens of sites and never really noticed any CSS performance issues.
I have got orders of magnitude faster sites by combining CSS or js files, gzipping content, adding cache control headers, serving via a cdn and not serving code that's not used.
I've also really benefitted from using logical markup and CSS selectors, not those designed for "efficiency" of the computer rendering them.
The new homepage you dudes have is a big improvement. Why haven't you blogged about how you're previewing this stuff on GitHub? It's fun to watch a start up growing and changing there and I think it it's in really well with the MVP/agile mindset
It sounds plausible but I'd love to verify it. I have no idea what % of people in the emergency room are uninsured and what % are not in an emergency setting.
Did you look at Wepay or authorize.net? They both seem like they do money in and out as well. I'd love to see a neutral party summarize the field for payment processing as it's quite hard to see what the differences are without doing some digging.