I’d also like to ask you for feedback on what you think and whether you think I’m on the right track. Please feel free to challenge and question me in the comments field below.
Tip #11: Set financial penalties for downtime: I agree, there should definitely be some financial incentive for the Cloud provider to perform for a couple reasons:
Second, it demonstrates that they understand there’s a direct relationship between what’s running in their cloud and the quality of the environment they’re supporting.
And third, now let me let you in a dirty little secret of financial penalties – if you actually do that math (my SLA included, by the way), you’re going to see that the number that I’m on the hook for is relatively small. In the words of one of my client CIO’s
Tip #12: It takes time to see ROI on SaaS development: Sage advice from Adam on this one – it’s going to take time and a concerted effort to make Software-as-a-Service (SaaS) pay off for you. His comments make me think about focus. Our experience is that many SaaS companies have little to no experience running a hosted infrastructure – so that skill must either be hired or acquired. Hiring people is hard, so I might argue (because this is our business) that SaaS companies can get further, faster by focusing on writing the code and driving demand, while leaving the hosting to experts like BlueLock. That’s exactly what SaaS company Right On Interactive did – they focused on writing better code and allowed us to help them get further, faster by managing their infrastructure. Check out their cloud computing case study.
Tip #13: Savings are not in the cloud, but in headcount: Oh man, I wish I could make this tip #1!! Adam hit the nail on the head. I’ve presented an infrastructure choices presentation to Rick Chapman’s Softletter SaaS University conferences several times and I tell the Software CEOs in the room that one of BlueLock’s key value propositions is about people. I even take them through a little back of the napkin math around the difference in cost of 5-10 servers doing it on your own, doing it at Amazon or hosting it with BlueLock. BlueLock wins and I tell the crowd that you could substitute BlueLock for another managed cloud provider because it’s not about my ability to pay my people less, it’s about my ability to “fractionalize” our labor cost, where they must have a full time equivalent (FTE) or 2 (if that person wants to take a vacation) or 3 (if you want 24×7 coverage and let someone take a vacation or get sick). So the software company that has dedicated staff to “manage” their cloud environment at Amazon is, in the end more expensive, than allowing me to manage their environment for them at BlueLock. If you’d like to see the analysis – send me a note at bwolff at bluelock.com and I’d be happy to share the slide and take you through my logic.
Tip #15: Let the cloud lead you to new innovations: This last tip takes the previous tip and Lincoln’s presentation to the next level. Companies that choose to deliver their software via SaaS (in the cloud) open up many new opportunities for revenue and value creation. The first step toward opening up new horizons for your software company is to migrate to SaaS and let the users take you to a better place. The cloud will only continue to get better, and SaaS companies taking advantage of the benefits of cloud computing will be leaps and bounds ahead of their competition in terms of cost efficiency and flexibility.
Thanks for reading this post – if you’d like to learn more about how BlueLock is helping enable other SaaS companies just like yours, drop me a note at bwolff at bluelock.com or visit our website to find out more about our cloud hosting services.
I would also love to hear what you think about my take and if you think I’m on track or “off in left field”.