Sunk Cost"We are invested too much in .Net" is a phrase we often hear. It's like playing poker and not willing to give up while the odds are against you. CFO's often use the word "sunk cost*". Sunk costs are irrelevant in making strategic decisions. .Net is the industry standard. So why don't large corporations run their mission critical applications on it? Why doesn't even Microsoft build their ERP systems on .Net? SaaS is the future. Absolutely, but not the solution for all your customers. You need a hybrid model. .Net does not support that from a single code-base. We don't need cross-platform functionality. Windows is still the major platform ... Correct, but Mac and Linux are rising quickly .Net supports all browsers. Sure it does, but only with a lot of additional coding and debugging. .Net is a productive environment. Have you ever asked yourself whether the resources you spend on your platform shouldn't be spent on where you make your money -- your application? There are plenty of frameworks available for .Net. Very true, but do you really want to invest resources in selecting, implementing, integrating, training your staff etc on third party frameworks (sometimes over 15 of them)? So what do you guys sell? We have a complete development and deployment environment for companies like you. We make a living by charging for licenses, like you do. We do not believe that you should rewrite the heart of your organization by yourself. By charging you for our products, we have a vested interest to get you to deployment so we both can make money. To learn more, attend a free WEBINAR for more discussion on this topic. How we compare to .Net from a cost point of view, click here. * Click here for a definition of Sunk Cost. |