Day One GA review….@boundary

The day started with some concern. We thought we had tested everything but some things slipped through the cracks. In our situation there was a corner case in our registration process which meant that a small percentage of people were delayed receiving their activation emails by a few hours. The “bug” was found (it was actually to do with our implementation of automation systems), corrected and emails released to those that did not received them.

There were a couple of other minor issues for instance some folks asked us about pricing and, (even though we are waiting a short while before fully publishing pricing on the web site) there was a pricing FAQ page that didn’t quite make it to the final web push (this is also updated now).

But, apart from these minor items the GA launch day was a good one. By the end of the day there were over a 100 more people enjoying Boundary than there were just 24 hours earlier and, we had another company make the commitment to being a paying customer. I’m sure we will make the marketing announcement as soon as we have that company’s permission.

From a product perspective all went really well. The twitter comments which can be easily viewed by searching @boundary were very positive in terms of speed of setup “Took 3 minutes to setup a @boundary meter. 2 minutes and 30 seconds of that was the ec2 instance starting up”, the visibility of the data that Boundary is providing “…I’m watching network traffic in realtime. Ladies and gentlemen, your jetpack”, and the super cool user interface “Goddamn the @boundary UI is cool.”

We received some positive press coverage as well. A selection of the articles:

http://www.talkincloud.com/boundary-launches-saas-based-monitoring-for-big-data-and-cloud-applications/

http://www.enterpriseappstoday.com/data-management/meeting-challenge-of-monitoring-big-data-in-the-cloud.html

http://siliconangle.com/blog/2012/03/27/devops-dossier-boundary/

Our infrastructure and datacenter was great and even though someone at our provider decided to pull a cable on one of our production servers in the middle of the day…..customers didn’t notice a thing. That’s why you write resilient software, because people do dumb things.

Another real positive for me for the day was the level of direct interaction between our engineering team and new customers particularly on the IRC channel (#Boundary on Freenode). Constant discussion all day long with our engineers helping users directly with questions and comments.

So, what now? Well the “spike” that you get from launch interest is very short-lived and real life typically resumes as soon as day 2. Today we’re all business….need to gather the sales and marketing folks together to ensure that we’ve got our plans together for the next few weeks, the engineering team will need to get together this week to start researching and assessing the next waves of capabilities that we’re going to add to the solution, the customer support teams need to be sure that they are following up with all our users and making sure their Boundary experience is an exemplary one and of course….we need to ensure that we take some time to enjoy the achievement so far, of which beer will play a major role.

Thanks to everyone for their support so far – now we’ve got some work to do.

Comments are closed.