July 21, 2015 | Written by: Michael Worthington
- How did you get started with Bluemix?
I went to a Bluemix Day workshop with some of my colleagues. In a matter of minutes we managed to launch the system, develop some code, run a scenario, and it simply worked. So I met with more IBM folks about Bluemix, and we talked about the capabilities, the roadmap, and IBM’s commitment to helping us build on the platform. Based upon the established relationships, we were reassured. We saw how serious the IBM team was about the Bluemix platform. So we decided to take that leap of faith.
Now I need to pause and tell you a little bit about my culture. Trust is very important. IBM is not a vendor for us. IBM is our partner. And when I say partner, I don’t just mean sales. I mean a commitment to quality and service delivery. Be there, with my team, in the trenches, shoulder to shoulder.There’s an example when Bluemix was just emerging. It was Sunday, and Israeli businesses operate on Sundays, though the rest of the world doesn’t. A global IT security patch took our system down, which was terrible. And even though it was Sunday morning, US time, church time, the head of services at IBM and his team had a conversation with us to fix it. In a matter of one or two days, the problem disappeared. Since then, for nine months, the system is up and running with no downtime!
So it’s not just about technology. It’s also about people, the ability to react, and the ability to deliver. The moment my team can’t deliver due to IT issues, that’s the moment I basically have to make a decision to swap an IT vendor. The Bluemix guys were with us in the trenches, and still are.
- How was working with Bluemix?
When we started with Bluemix, our deploy time was about 15 minutes. Now it’s one minute or two, which is amazing. So imagine how many development cycles you can save. I can give you an example. I met with a marketing expert who was named one of Forbes’ Top 20 Social Media Influencers. We showed him our solution and he was very excited about our startup. I asked him, how many people and how much time do you think it took to develop what you just saw? So he said, well I think it’s about 30 people, and roughly two to three years. I said actually, it was six months, 2.5 developers, and Bluemix.
Only a few weeks after launching, 20 businesses, retail chains, and hotels have joined our platform. We’re in full production mode, and growing exponentially, daily. Keep in mind, it’s been less than one year since the company was formed, and less than 10 months after we started development. This could not have happened with any technology other than Bluemix.
- What’s it like to be a startup?
Being a startup is basically like trying to build your own racecar in your garage. You start to assemble an engine and some tires and some bodywork and it looks great because in the light of the warehouse everything looks great. But the moment you open the door and start driving, what you thought was beautiful is actually not that great—the wheels are creaking, the engine is making an alarming noise, and you have to fix things as you go. So you put an engineer near the engine to fix it while your car is running because you cannot stop (since you forgot to assemble the brake system). In the meantime you’re trying to drive, instruct the engineer, and figure out where to go all at once.
So you need to call some repair guy to assist your engineer. But the repair guy also has to be in a moving vehicle because you cannot stop (you did not assemble the brakes yet, remember?). So they need to drive beside you and start passing new engine elements and gasoline and whatever you need, while you are driving, getting distracted, and figuring out how to climb the next hill.
And that’s IBM. They are our on-the-fly, elements-as-you-go, mobile repair team. They assist us in building our racecar. And when we all hit the finish line, they will be there cheering with us. That’s giving us more and more value as we need it, when we need it, with the best quality, agility, and speed, as we drive towards our goals.
This interview has been edited and condensed for clarity.