The challenge is that these new features drive a bill that your customer sends to their customer. I am a little surprised by this response to problems that could undermine your customer's business relationships.
I am also surprised that none of your current customers would give feedback or comments on how the release worked for them: why not just deploy it to current customers who want to use it (since it's appears to be free to them) and make this announcement after you have had more than a week's testing? Or was that also a joke?
You should consider appending the "jump" sentences (e.g. "jump into a new feature...") to your announcement blog post so that new visitors are aware of your approach to developing and delivering software.
Yaw, I agree in hindsight-- the language should have been more "beta-ey" to warn off the risk-averse. We did have a small collection of private beta users, FWIW. There are some scattered issues, but the release is pretty solid.
These new features CAN drive a bill (though most of the users were surveyed who were interested in this feature were NOT billable folks, interestingly enough). Given that the feature has existed for less than 1 business day, I think the chance of undermining business relationships is pretty darn slim.
Did I do something to offend you, Sean? I can't QUITE tell if your comment is snarky or not.
No snark, concern that your new application has more serious consequences of failure: sending a client an inaccurate bill is much less recoverable than a poor understanding of how I use my time.
I am also surprised that none of your current customers would give feedback or comments on how the release worked for them: why not just deploy it to current customers who want to use it (since it's appears to be free to them) and make this announcement after you have had more than a week's testing? Or was that also a joke?
You should consider appending the "jump" sentences (e.g. "jump into a new feature...") to your announcement blog post so that new visitors are aware of your approach to developing and delivering software.