This definitely will give you some interesting leads, but a spell check ahead of posting here might gain more positive support. "Our Questionairre. We analyze your answers to a series of specially crafed questions designed to understand your business objectives" .. the words Questionnaire and crafted have typos.
That's not exactly accurate - he's blaming Obamacare for them having to provide new insurance products that have a net higher cost going forward - the incident of distressed babies happened before the ACA, which means they did have that choice, and chose to pay the costs.
Regarding what most insurance policies cover, there are actually several scenarios that would leave AOL on the hook. First, they could have a policy that has an Annual or Lifetime payment limit, which would leave the company (or individual) responsible for anything over. Alternatively, if the number of incidents was significantly higher than average for the carrier, AOL could see a significant premium increase due to the higher utilization of their plan. Or, they could actually be running a self-funded insurance program, which means they are managing the risk instead of relying on a separate insurance carrier.
Either way, there are several situations in which AOL's costs could be significantly impacted by the situation.
The most accurate part of this is that line near the end... "...nor will I mention the [A], the [Z], and everything else." That feeling of an endless list of responsibilities is a definitive property of launching a startup.
A fan of the idea - giving people permission is a good solution. The word "expected", however, can carry different connotations. VSRO (very short reply okay) might be friendlier?
Oh yeah - thinking back to consulting work - something that let me "make a beautiful spec and share it" would have felt like a one-time-use service. Subscribe for a month, make a spec, take the learnings and add it to my own Word template.
The problem I mentioned (collaborative spec maintenance) is something that I know I'd pay for as a subscription - specifically because it helps me manage something for the ongoing health of our products. It becomes more core.
The only downside is that a solution more aligned to infrastructure costs (as I have suggested) can't command as high a price premium as something that is aligned to revenue (i.e. help me rationalize/explain higher estimates to customers).
Coming up with a spec format that clients will like has always been a fairly easy problem to solve - as well the spec is usually worked on once the project has been awarded, so isn't even part of the sales process. As well it's hard to improve the writing + sharing experience of Word + Email or Google Docs + Sharing.
The attention to estimating is nice, and will save freelancers or less experienced teams time, but is only really useful to teams that do contract and custom work.
I was hoping for more of a focus on the collaborative work that comes out of writing specs: more around the commenting/editing/workflow. When working on a spec (either internal or external) change requests or modifications are important, as are interdependencies and change tracking.
Your product title made me think "GitHub for Specs" and it doesn't seam you're going that way. Shame.
Also, 4D theatres where they add motion, wind and water to enhance the experience.
Arguably, amusement park rides are all about messing with your sense of touch (proprioception, balance, etc)