So, it was recently mentioned that “BSM doesn't lend itself to tossing cheap and cheerful code over the wall”, and I’m left to ask – Why? Let’s take the processes an organizational philosophy changes required to achieve the full promise of BSM out of the picture for a moment and focus on the solutions that support BSM. Why should it take 3 days, just to prep the operating system to install the solution? Why should it take another three weeks to configure? Why should it require a 6-figure starting price? And why can’t it be cheerful?
These questions jump to the heart of the failures of the Old Guard when it comes to BSM. No wonder BSM adoption is practically stagnated at 26% in the Enterprise and is non-existent in the SMB market (at least in Pre B.E. times). No one wants to put themselves through so much pain to end up with a solution that’s collecting dust a year after deployment because it was too hard to maintain.
These questions were also the core reason why we came up with BSM:BE. I knew we had something when a graphic designer friend, someone who thought TCP/IP was a brush setting in Photoshop, was able to get FireScope up and running, collecting data and delivering financial analysis of his technology in a little under an hour.
We live in a Web 2.0 world. No one has patience for dinosaurs selling Web 1.0 technologies.