SaaS Contracting: Tips Leading to the Decision and What to Include in the Agreement

 

There are many items to consider before deciding to adopt a SaaS approach to your IT operation.  Marcia Gulesian, a software developer, project manager, CTO, CIO, and author of numerous feature articles on IT, has captured the salient points in her article SaaS: Financial, Legal & Negotiation Issues.  As the title to her article suggests, the financial implications should be addressed first.  Gulesian has a very descriptive section on the differences between buying the software application and leasing it.  She discusses the differences of owning an asset and its tax advantages of the deductibility of depreciation as opposed to the leasing option.  There is a brief explanation of cash flows between the two alternatives, finding your opportunity cost, and making your determination on the comparison of the present values of the cash flows from the cost of owning versus the cash flows from the cost of leasing.  Before we go too far afield, my readers can attest to the fact that I always try to define our terms before delving into the nuances that the subject line suggests.

Wikipedia’s definition of SaaS is very complete yet succinct:

“Short for Software as a Service, SaaS is a software delivery method that provides access to software and its functions remotely as a Web-based service. SaaS allows organizations to access business functionality at a cost typically less than paying for licensed applications since SaaS pricing is based on a monthly fee. Also, because the software is hosted remotely, users don't need to invest in additional hardware. SaaS removes the need for organizations to handle the installation, set-up and often daily upkeep and maintenance. Software as a Service may also be referred to as simply hosted applications.”

I also have a posting in this blog, which I must admit has become quite popular based on the number of hits registered to it, entitled SaaS is the Future.  In it I discuss how a Managed Service Provider (“MSP”) can help software developers get their product to the market faster since the infrastructure barriers and capital expenditures are significantly lessened.  In another posting about Unified Communications I have quoted Mat Taylor, a senior software architect with British Telecom, regarding the benefits of SaaS:

"The ability to get things done faster, get workers more engaged in a business scenario, provide better customer service, are all big productivity wins that benefit the bottom line"

In light of the above discussion surrounding “lower total cost of ownership and quicker time-to-value”, Gulesian cautions us that the other factors to include in the financial calculation is the maintenance and support fees that come with ownership as compared to the SaaS fees which includes these items.

SO WHAT DO I INCLUDE IN THE SAAS CONTRACT?

Gulesian points out three areas that must be addressed in the contract:

·         Integration with your non-SaaS systems

·         Loss of control of data

·         Dependence on the provider for security

The CIO and his or her team are the main players to address the integration issue.  Although the next two points also require the IT organization’s participation and input, these are matters that must be addressed upfront in the agreement itself.

Risk of loss of your data is paramount.  In the event that the SaaS provider is unable to provide the support anticipated, it is essential that you have access to the applications as well as your proprietary data.  Inability of the provider to provide support may happen for a myriad of reasons such as bankruptcy of the provider or a real or threatened patent infringement claim and subsequent injunction.  The preferred approach to protect against such loss is to insist that the provider place its code into an ESCROW account.  Language can be drafted which will instruct the trustee  of the escrow ( an independent and trusted third party) to release the code to the beneficiary (i.e. you) upon the happening of certain events which are defined in the escrow language in your SaaS agreement.  One shortcoming to this occurrence is the downtime that may be involved in getting your systems up and running, but this is a necessary protection that you must include in your contract.

Transition assistance is another item to consider.  In the future you may wish to change the SaaS application currently in use.  Language should be included to require the provider’s assistance in developing the data migration strategies and the procedures to be followed so you can move your data to another application.

Since the SaaS model is economical by nature (see Wikipedia definition above), traditional discounting expectations are not available.  Pricing is based on users or seats.  The more users subscribed, the more likely the cost per user can be discounted.  So plan accordingly and try to build in volume discounting per blocks of users.

Other items Gulesian notes for inclusion in the agreement are:

·         Service Level Agreements (SLAs) regarding

§  Availability

§  Response times

§  Notifications of outages

·         Regulatory compliance

·         Data integrity

·         Data Privacy

·         Frequency of backups

·         Disaster Recovery

Gulesian’s article hits the main points and I highly recommend it to my readers.

 

 

SAP's Business ByDesign Aimed at SMB Market

 

Richard Adhikari reports in InternetNews.com that SAP plans to move aggressively forward with its SaaS offering, Business ByDesign, and is targeting the SMB customer in his article SAP to Innovate Heavily in SMB On-Demand Suite - updated - Business intelligence to pervade enterprise software giant's forthcoming products.  It appears from some of the comments quoted from the SAP executive suite that the word “aggressive” is only the tip of the iceberg:

Henning Kagermann, co-CEO stated:

“When you come to challenging times, you have to take risks. Business ByDesign is not just about product, we also want to focus on profitability, and in the volume business you have to do a lot of innovation to make the business profitable”

Jim Snabe, head of SAP's business solutions and technology, stated further:


“You can look at it from two angles. One is how to convert money into ideas; the other is how to convert ideas into money”


In addition to the predicted new innovation of this SaaS offering which includes CRM, SAP will integrate its Business Intelligence (“BI”) technology into the business suite as a direct result of its purchase of Business Objects last year.  This will bring the analytics portion into the new offering.  Customers will be able to analyze their historical projections as well as future projections.


So when should we expect this new business suite to be rolled out.  SAP says to look for it by next year.  Just exactly when next year isn’t quite clear.


In related SAP news:  In a move to emphasize its focus on profitability and a bid to match the pricing of Oracle, its chief competitor, SAP customers are none-too-happy with the recent price increase for its enhanced maintenance “Enterprise Support”.  For the full story see SAP CEO Defends Price Hikes as Customers Gripe - In its drive to become more profitable, has the enterprise software vendor stirred up a hornet's nest?  Kagermann defended his company’s actions by stating:


"We're offering a new service which is much larger than before, has a certain value and a certain price. The cost for us is higher, and so we believe it's a fair price."

Mobile Computing: A Unified Platform Is Essential As Technologies Converge

 

I have reported on several new technologies as they have entered the market, such as SaaS and SOA, and also the newest devices powered by the latest applications.  Jim Hemmer, an experienced CEO in the hi-tech and communications industries, brings this altogether in his cutting-edge Op-Ed for SandHill.com entitled The Mobile Bang Theory.  I highly recommend this article to my readers and it is a must read for the IT managers trying to get a handle on the security and control issues that mobile computing presents.  Hemmer begins his article by announcing the new shift in the archetype and identifying its 3 components:


“a mobile renaissance is afoot as a result of more powerful devices, faster wireless networks and broader use and acceptance of Web services and SOA”


Hemmer’s insight begins by recognizing the catalyst for enterprise mobility.  He labels this the “outside-in demand” phenomenon.  Consumer’s personal use of mobile services on mobile devices has forced enterprises to rethink their approach.  With this new approach come the challenges of providing access to the data and applications so the employee/user can optimize their efficiency.


For the enterprise the competitive advantage comes from the ability of the mobile user being able to enter data once into a mobile device which results in not one response but puts in motion a multitude of real-time business processes.  Hemmer identifies the trends in mobile computing and how the applications perform.  He then provides some real-life examples of how this approach works and the higher returns the innovative enterprises have experienced.


Hemmer’s advice to the IT managers is to develop a mobile strategy that supports multiple devices and multiple solutions.  The old siloed approach does not fit into this model. Its inflexibility is too costly.  He puts it succinctly by stating:


“The real game-changer is to mobilize diverse business processes, applications and data from a variety of internal and external sources — from one unified, cohesive platform.”

 

SaaS: Will the Large Enterprises Accept it?

 

Richard Adhikari reports on a recent summit of SaaS executives in his article Are Changes Coming in the SaaS World?  The direction the industry should take was discussed but with little consensus.  It seems that those assembled see the huge potential in acceptance of SaaS by the large global enterprises, but no one can quite figure out how to break through the barriers.  Adhikari has done an excellent job of presenting the plethora of diverging views on why or why not the SaaS vendors should target the large enterprise market and how to go about doing it.  I am not privy to their marketing research nor have I suffered the trials and tribulations that some of the participants relate.  It just seems to me that sometimes it might be best to let the sleeping giants sleep.  Will these large enterprises come on board sooner or later?  Adhikari cites Maynard Webb, CEO of virtual call center company LiveOps who states:


It's a vicious circle: SaaS vendors can't sell to the enterprise because they haven't solved many of the concerns IT has with on demand software, so they don't try.  Most SaaS vendors target the SMB market, while the rest aim "at niches in the enterprise such as human resources"


What becomes apparent when reading Adhikari’s article is that there isn’t just one reason for the reticence of large enterprises to accept the SaaS model.


In my research in this area I have come across varied opinions and insight into just what exactly SaaS is and who should take advantage of it.  In my February 10, 2008 posting to this Blog SaaS is the Future software developers were scrambling to meet the demands of their market.  At that point their market was the SMB enterprise.


A further explanation as to the non-universal acceptance of SaaS can be gleaned from an insightful comment by Sybase CEO John Chen:


“ … But the reality is that every new technology and every new method will have its audience – but it won’t wipe out the previous ones.”  For the full story and an interesting perspective see my May 1, 2008 posting What Customers Want from their Software Vendors.


Of course there also is the other side of the coin.  The SaaS software developers themselves have their own internal hurdles to surmount.  In my June 1, 2008 posting Growing Pains of OnDemand I highlight one of the problems of managing a subscription business:


“Simply put, the business processes needed to run a subscription business do not yet exist, and when these new business processes do come on line, they will be incompatible with the existing business processes for a large enterprise software company.”


Perhaps it is best summed up in Adhikari’s article by Lisa Lambert, managing director of the software & solutions group at Intel Capital:


Intel's Lambert thinks the notion of selling to the enterprise is a red herring.  "I don't think it's a question of enterprises not being ready to buy SaaS, it's that it makes more sense for small businesses to buy SaaS.  The value proposition of SaaS really appeals to small businesses, which were excluded from being able to buy legitimate software infrastructure that's enterprise ready because they couldn't afford it, it was too expensive and complex, and had long implementation cycles."


SAP's Business Objects Partnership with Oco: Low-Cost Solutions for SMB's


Business Objects, an SAP Company, continues its strategy of partnering with innovative companies offering Business Intelligence (“BI”) in a SaaS approach with the blessing of its parent, SAP. Its latest association is with Oco. Although both companies are players in the SMB space and both offer BI in the SaaS mode, Oco is a much smaller company. Oco’s competitive advantage comes from its development of templates for various vertical niche markets such as analytical tools and reports in the retail, industrial manufacturing, and consumer packaged goods industries. This collaboration suits both companies. SAP furthers its desire to make its products work with other vendors’ products and Oco gains an entrée to the larger SMB customer that was not previously available to them.


The BI marketplace has become extremely competitive. The main distinguishing factor for vendors in this market is to provide the products that give the enterprise the ability to make decisions faster. Business Objects’ SaaS offering, Business OnDemand, provides a fast and accurate solution. Now with the added advantage of Oco’s data discovery and mapping tool, the solutions for the SMB will come faster and at a lower cost. These partners recognize that the much larger enterprises who want their intelligence customized might not be so receptive to the Oco data model. Richard Adhikari explains in his article Business Objects Teams Up With Oco the customer first accepts Oco’s data model and this data model then finds all the data in the enterprise and produces the BI in a low cost manner.


Adhikari cites Business Objects Vice President Mani Gill, who explains the enhanced OnDemand offering this way:


Oco will let us deliver hosted multi-source data warehouses in multiple industries and functional areas.


We use our enterprise information management tools to pull data from customers, host it ourselves and provide business intelligence on top.


For a fuller explanation see Adhikari’s article. He points out that the combination of these two vendors additionally benefits both by allowing Oco to become a reseller of Business Objects products and permitting Business Objects yet another opportunity to differentiate itself and gain a foothold in this market space.


Unified Communications: Should SMB's Look to SaaS for the Solution?

 

First I would like to define what we mean by Unified Communications (“UC”).  Unified Communications encompasses email, instant messaging, texting, phones, and other networking and mobility applications.  In short Unified Communications “ … lets users access people and resources, no matter the location or communication channel, spurring productivity and boosting business processes at an economical cost.”  For an in-depth discussion on this topic see UC Will Prove Challenging to Buyers And Sellers by Judy Mottl.


Initially SMB’s have found it a daunting task to try and pull all these various applications together into one cohesive platform.  The lack of funds and the lack of familiarity with these tools have hindered their move to UC.  The familiarity issue is evaporating as more people are using these communication tools in their non-work life and begin to demand these tools in the workplace.  For further discussion on the capabilities and uses of the newest wireless devices and the coming of the Mobile Web see the following posts in this blog:


Blackberry Bold RIMs Next 3G High Speed Wireless Handset


4G and The Mobile Web: WiMAX v LTE


SaaS may be the way that SMB’s can overcome the budgetary constraints as well as the integration problems that have acted as a barrier for these enterprises.  SaaS provides a faster deployment and the right provider can pull all the telephony tools and applications together into one unified and interconnected unit.  Judy Mottl has written an excellent article that details in the ins and outs for those SMB’s considering this next step into UC.  In her article SaaS Best Path for SMB Unified Communications: Service strategy lets small companies enjoy technology benefits without the headaches she interviews Simon Edwards, UC project director, British Telecom (“BT”), who cautions not to get locked into one particular platform:


"SMBs have to make sure they stick to an agnostic platform," said Edwards, adding that the best approach is an open standards platform that allows emerging technologies from different tool makers


Mottl concludes her article with a quote from Mat Taylor, a senior software architect with BT:


"The ability to get things done faster, get workers more engaged in business scenario, provide better customer service, are all big productivity wins that benefit the bottom line"


For more on the coming of age of handheld devices for the UC revolution see the following posts in this blog:


Future of Wireless Devices


SAP Sapphire 2008


Software Vendors Find Another Advantage to SaaS

 

Daniel Druker posted an interesting article in his blog SaaS 2.0 entitled Sage Advice. In it he explores an interesting twist to the value of SaaS to the Channel Partner. SaaS is not only the wave of the future, but it also fits quite nicely into one’s retirement planning.


Druker points out that the Value Added Reseller (“VAR”) has a business model that emphasizes upfront revenue. They sell the software and can also look to implementation as another source of revenue, but by and large there is no steady stream of cash that hits the P&L. The value of the Channel Partner’s business is dependent on finding new customers and selling year after year.


The missing element to the cash flow problem is what the SaaS business model can provide, Contracted Monthly Recurring Revenue (“CMRR”). See my post in this blog March 2nd entitled Best Practices for the SaaS CEO – Top Ten Rules. Byron Deeter’s first rule is that “Cash is King”.


In Daniel Druker’s article he recounts a discussion he had with an established Channel Partner thinking about retirement and the selling of his business. Adopting the SaaS model seems to provide the answers this VAR owner needs. As Druker points out:


• the valuation of any business is driven by future cash flows
• shifting to SaaS will mean a much higher valuation and selling price


Albeit not entirely altruistic, yet another reason to adopt the SaaS approach.


Augmentation of Recent Posts

 

In my reading of interesting and relevant articles posted on the web, there have been several follow-on articles which expand on some of my more recent posts to this Blog. Due to the number of articles that I have come across, I thought it best to cite to some these articles, with a line or two of brief explanation, and let the reader pick and chose any article(s) of interest. I found the following to be of particular interest:

Growing Pains of On Demand

 

There is a revolution of sorts going on in the computing world. I do not want to over-dramatize this fact; however I am reminded of author and pamphleteer Thomas Pain who wrote:


• “Lead, follow, or get out of the way”
• “These are the times that try men’s souls”
• “The harder the conflict, the more glorious the triumph”
(yes, this is drama)


Why all the drama? Well, I recommend you read Tien Tzuo’s article entitled The Global Transformation to On-Demand. Tzuo’s subtitle may aid in understanding my reference to the drama (i.e. “Why the world is moving to subscriptions and what it means for businesses”). This article should be read in conjunction with Daniel Druker’s article Different is hard: SAP - (Not Too Much) Business by Design.


Let’s start with Tzuo’s rather succinct history of the change in the paradigm from on-premises computing to subscription buying via the internet. Tzuo was on the cusp of the wave that brought in the SaaS business model. The guiding ideology for Tzuo and his contemporaries regarding SaaS is that


“ … software belonged on the Internet, not on a CD, and in that process it is transformed from a product that you buy to a service that you subscribe to.”


Tzuo’s analysis of why the trend towards subscriptions (i.e. On Demand or SaaS) rather than the traditional purchase or licensing model covers a broader spectrum than just the software industry. He explains that the internet has transformed the way people buy. The purchaser now has more options from more packages and as their needs change so can their subscription. Buyer’s remorse is eliminated.


“no large up front investment, no ongoing maintenance costs or hassles, no insurance costs – just pay for how much you use.”


Tzuo points out that there are significant differences between the processes for managing a subscription business versus the traditional product for sale business. These differences are:


• The ability to offer your product in parts, as well as full packages
• Invoicing and payment terms must be able to track the flexibility in the product offerings
• There are constant changes in the subscription and the revenue collection process becomes convoluted
• The metrics for this type of business differ from the usual billing metrics and so the ability to measure success and redirect efforts must adapt


The difficulties in managing a subscription business can be demonstrated by reference to the current situation at SAP and its announced delays and reduction in investment in its hoped for SaaS offering, Business by Design. Daniel Druker presents an in-depth analysis to the possible problems facing SAP. He lays out the trials and tribulations that a mega-corporation must face when trying to adapt to the changes in the industry. Instead of the purported technical issues facing this new service such as the “Mega-tenancy” model that a company the size of SAP is trying to implement, Druker sees the problem as the age-old issue of resistance to change. He labels this the “innovators dilemma”. The best and the brightest personnel shun the new innovation, especially if the promise of returns is far removed from the fundamental business model. It almost seems as though the company sets up its own barriers. A matrix organization, such as SAP, organized by country or region, is more inclined to focus on hitting their sales goals for the quarter or month and less likely to assist in the latest project.


In addition to the innovators dilemma, Druker also includes a discussion much like Tzuo’s differences between a subscription run business and that of the traditional product driven business model. Simply put, the business processes needed to run a subscription business do not yet exist, and when these new business processes do come on line, they will be incompatible with the existing business processes for a large enterprise software company.


Druker concludes by stating that, “SAP is an amazing, well run company”. It remains to be seen how well they will manage this latest innovation in the computing world.


What Customers Want from their Software Vendors


Maryann Jones Thompson interviews Sybase CEO John Chen in an Op-Ed in SandHill.com. Thompson artfully takes the reader through the strategy and growth of Sybase and allows Chen to discuss his stewardship of the company from 1998 to the present.  What I found of particular interest was Chen’s response when asked why Sybase was slow to embrace SaaS, Open Source, and other new technologies.  Chen responded as follows:


“In the 1980s during the transition from mainframes to UNIX, everyone forecasted the death of mainframes. Then NT arrived and the end of UNIX was proclaimed. Now people are talking about open source or SaaS in the same way. But the reality is that every new technology and every new method will have its audience – but it won’t wipe out the previous ones.”


To me this answer is right on and makes good business sense.  Chen’s approach seems to fit quite nicely with another SandHill.com Op-Ed piece written by M.R. Rangaswami entitled Old Rules for a New Era.  It appears that Rangaswami has a similar view vis-à-vis Chen’s recognition that new methods come online and attain their own audience.  I think implicit in Chen’s comment is what Rangaswami discusses regarding the fact that today’s IT Buyers struggle with the ever-changing new models and technologies such as SaaS, Cloud, and SOA.  Yes, the future does look bright as these new products come to market and affect the technology strategies of today’s global enterprises.  However, the proliferation does have its drawbacks. Just how can the software vendor get its products noticed?  In essence the question becomes ‘Just what is it that the IT Buyer wants’.  The answer to this question is alluded to in the subtitle to Rangaswami’s article, “Software vendor success will not be determined by a specific technology or model but by meeting customer expectations”.  Here are those expectations as developed by M.R. Rangaswami:


  • Reliable – Products will be expected to work out-of-the-box and continue to do so as they interoperate with other products. Heavy integration work will not be expected or tolerated.

  • Secure – Software must be secure beyond today’s acceptable levels. Vendors must provide guarantees and incentives to convince buyers of this heightened security.

  • Fast – Solutions have to be able to be deployed quickly and offer a speedy time-to-value. If it can’t be on-demand, then it needs to be close.

  • Simple – The hallmark of next-generation software will be its ability to be intuitive for its users – as intuitive as an online application aimed at consumers. No training should be required. It must also be simple to purchase and deploy.

  • Innovative - Buyers will expect vendors to continue to innovate their solutions. They will value new approaches to solve the same problems as well as attempts to solve entirely new business problems.


Sun Let's Software Vendors Run SaaS Without Code Rewrites

 

Andy Patrizio reports for InternetNews.com on a new offering from Sun Microsystems that will allow software vendor’s customers to convert from an on premise version of their application to SaaS using existing technologies.  The good news is that this conversion can be done without rewriting code, which in some cases can take many engineers an inordinately long period of time to design and then test the new architecture.  This is all made possible through Sun’s new “virtualization service”.  Sun or a Sun partner will then host the application.  Of course the service only “supports applications hosted on a Sun server using Solaris, Solaris' Containers virtualization technology and xVM, Sun's virtualization software.”


The advantage to this service was explained by Vince Vasquez, business development manager for SaaS programs at Sun:


"People see the demand for on-demand but they are stuck with a year or more of development time without actually knowing if there's a market there for their product.  With virtualization, they can get into that market right now."


If this is of interest, I strongly recommend reading Patrizio’s article entitled, Sun Latest to Help App Vendors Get 'SasSy'.  In it Patrizio reports on the success to date of this service with a case study and also discusses pricing and Sun’s 90-day free trial offer.


Best Practices for the SaaS CEO - Top Ten Rules

Byron Deeter, Partner with Bessemer Venture Partners, a founding CEO of one SaaS business and a board member of three other pure-play SaaS companies, has firsthand experience with the on-demand model and is well-qualified to state that CEO’s of pure-play SaaS companies need to change their paradigm.  When one lacks a role-model and cannot find a neatly put together list of best practices, the skillful CEO pulls together his own rule book. Deeter and his team studied both hybrid and pure-play SaaS companies and developed their own list of best practices for the on-demand model. Veteran software CEO’s might want to heed his advice and shift their paradigm. I strongly urge my readers to read Deeter’s article Bessemer’s Top 10 Laws for Being “SaaS-y”. I’ll try to summarize below his ten “laws” for running a successful SaaS business.

1.     Cash is King (i.e. Contracted Monthly Recurring Revenue or “CMRR”): The old model that would value a longer deal with slightly less CMRR over a short term deal with a larger CMRR is out. The new model recognizes the likelihood that renewals will make up the difference. The need for working capital in the SaaS model emphasizes the importance of “customer churn” on this first rule. “The top performing SaaS companies typically achieve annual renewals on a customer count basis above 90% (much of which is often due to bankruptcies, acquisitions, and other events beyond the company’s control), and over 100% renewals on a dollar value basis due to up-sells into this installed base.”

2.     Sales Learning Curve – don’t ramp up your efforts too quickly: Refine your sales model and as it grows think in terms of CMRR.

3.     Once the Sales Learning Curve peaks begin to hire more renewal orientated account managers. These new account managers should be compensated on customer service, renewals, and upsells.

4.     Sell Directly – Channel relationships are unattractive. Without systems integration work nor the need to require huge hardware purchases or vast amounts of software licenses, the old Channel partnership model is not appealing. A new generation of partners and resellers will develop.

5.     Don’t rush to go global - Hold on Europe and save Asia for later. More barriers exist such as service level expectations, data access, and security. Don’t weigh down your company with the costs. Develop a strategy where Europe and Asia will come online as you become a public company.

6.     One datacenter: Studies show one datacenter is sufficient. No need to take on the costs and organizational complexity, at least until your company is public. Invest in backup and disaster recovery.

7.     Design a SaaS product that is single instance and multi-tenant. Multi-instance and single tenant does not apply to this model.

8.     Online marketing is a core competence – Your sales prospects are online. Leverage search engine optimization.

9.     Cash flow is critical due to low monthly subscriptions and so financial management is key. Weigh investments carefully and structure them in a way to allow future CMRR to produce measureable amounts.

10. Have enough investment capital to last at least 4 years. It takes a while to get to breakeven. The SaaS model takes a lot of R&D and sales expense on the front end.

I particularly like Deeter’s eleventh rule. Oh, did I say there were only ten? Here is number 11:

 You can ignore one of the above 10 rules. But only one. Deeter recognizes that there are no absolutes and welcomes a refinement when needed. However, his studies show successful SaaS companies stayed very close to the above best practices.

The 7 Trends for ERP in 2008: SaaS, SOA, and Web 2.0

So you want to know the hot areas in ERP. If so I highly recommend to my readers Forrester Research’s R. “Ray” Wang’s Op-Ed piece 7 Trends in Enterprise Software Adoption for 2008. In it Wang discusses the latest survey that finds the trend for IT Decision Makers is for upgrades, collaboration, and knowledge management. Wang’s article is comprehensive and includes detailed bar graphs that enable the reader to clearly follow his text and assists in understanding the salient points.

I’ll list out these 7 trends with a brief explanation/summary, but check out his article for the full impact of the findings:

1.     Software spending budgets for 2008 nearly identical to 2007:  There actually is a slight up-tick of 9% planned for 2008. Although enterprises will be spending on licenses, operations, and development, there still is quite a lot to be spent on maintenance.

2.     There is a need for Long Term App Strategies: Companies are laboring under the disjointed approach of the past (i.e. a little upgrade here, a little BPO there, with a little project integration thrown in for good measure). As we move to a Service Oriented Architecture (“SOA”) enterprises will take advantage of this and begin to implement long term strategies. Integration of applications is the number one priority.

3.     A move toward packaged applications: Due to a possible economic slowdown, enterprises are focusing on operational efficiency and compliance as their main business drivers. Interest in BI is closely followed by CRM. There also will be major upgrades of ERP suites.

4.     Web 2.0’s time has come: Enterprises are slowly recognizing how these tools improve collaboration and productivity, but are still reticent about security.

5.     A majority adopt SOA: This supports the enterprise’s integration projects.

6.     SaaS adoption grows by 50% in 2008: Pricing, ease of deployment, and minimal IT involvement are the key drivers for adoption.

7.     Software investment in collaboration and content management: Enterprises allow access to new stakeholders such as suppliers, partners, and customers.

Wang concludes his article with a list of three recommendations and urges enterprises to develop a long term app strategy:

·         Don’t delay: No need to buy all the new technology today. Plan ahead with an eye on use of existing technology and investment in future apps.

·         Take an inventory of existing apps:Organize these apps by business process.

·         Ongoing review of your apps strategy: Gauge progress and adjust accordingly.

SaaS is the Future

SaaS is no longer solely for the start-up software firm. Enterprise software developers have heard the call from their customers and seen the competition latch on to SaaS and are now offering mainstream applications. Software developers, big and small, face many demands and constraints placed upon them by the market. Their customers seek rigorous specifications.  The application development process comes with a whole new group of constraints, and the competition is fierce and ever present.

Gary McAuliffe, in his article Excelling in the Evolution of Sass, points to the Managed Service Provider (“MSP”) as the “great equalizer”. 

Managed Service Providers engineer infrastructure for reliability, resiliency, and security, in some cases offering 100% network uptimes. 

McAuliffe lays out a detailed analysis of the value MSP’s bring to the table. He describes how using an MSP can get your product to the global market faster. The other advantage is what McAuliffe labels “optimal user experience” (i.e. customer satisfaction). This customer satisfaction could potentially reap rewards downstream as opportunities for selling licenses present themselves.

The benefits are not solely for the external market. McAuliffe adroitly states:

Internally, partnering with a Managed Service Provider can provide software companies with a plethora of benefits. The capital expenditures to provide and maintain everything the business requires to launch and sustain itself from the application, developers, system administrators, to any commercial software required to run the application, along with a full infrastructure pose daunting barriers to overcome. A MSP will deliver those harsh capital expenditures over a more tolerable operational cost structure allowing software companies to reinvest their upfront capital into software where it is more beneficial in the overall well being of the firm.

If this has sparked your curiosity, then perhaps you might also be interested in Jeff Kaplan’s article Top Ten Reasons Why On-Demand Services Will Soar in 2008. I’ll whet your appetite and list out the ten reasons. You’ll have to read his whole article to get the benefit of his wisdom and predictions.

The Top Ten Reasons are as follows:

1.     Services are Recession Proof

2.     Everyone’s Going Virtual

3.     Amazon, IBM and Google Bet on Utility Computing

4.     Nick Carr Returns

5.     SaaS Solves SOX

6.     Managed Services 3.0, Unified Communications Services and Service Automation (Hint: The key for Kaplan is the “3.0” in the title)

7.     Carriers and Channel Companies Find Success With New Services

8.     Failure Doesn’t Matter

9.     IT Discovers Services are the Solution

10. Wall Street Buys Into Services

SAP Touts New BI Software

SAP unveiled nine new software packages that allow the monitoring and response to business information from any format or application. Three of the nine new offerings are targeted to the SMB market space. This all stems from SAP’s purchase of Business Objects (see post 12/21/07 in this Blog SAP Merges with Business Objects). SAP’s CEO, Henning Kagermann, stated:

Our key competitive differentiator is that we're building a portfolio on the most open platform. We are the only one that can offer business performance optimization in a closed loop.  At the end of the day, you have to take immediate action. Our business suite and business intelligence close the loop. You have faster and better insights and you can transform it immediately into actions.

Is this rollout all in response to the current activity now taking place in the industry? As I alluded to in my post of 1/9/08 What’s Next for ERP in 2008, Larry Ellison has not and will not sit on the sidelines as these mergers and new products are rolled out to the customer base. Just this week Reuter’s reports that Oracle has finally succeeded in its bid for BEA.

Kagermann addressed the issue of growth and competition in the industry stating:

You never in life should exclude an opportunity in business. The question is where is your priority.  Growing through organic growth is No. 1 for SAP.  If there's a unique opportunity to expand our opportunities, we will do it.  These are things you can't plan ahead and sometimes you have the opportunity and must take advantage of it.

SAP plans to integrate functionality from Business Objects into its Saas offering, Business ByDesign. SAP’s 2007 operating margins were down by .8% due mainly to its approximate half a billion dollar investment in getting Business ByDesign to market.

To read the full article click here

More Growth in Outsourcing in 2008

InternetNews reports that Gartner predicts outsourcing will grow by more than 8% this year to approximately $441 billion. The trend in this continued use of outsourcing seems to be moving away from large vendors to more of the smaller vendors with specialized products or services that can meet a company’s particular needs. Gartner’s survey results indicate a recent change in company’s strategies and priorities vis-à-vis outsourcing. There has been a decidedly huge increase in the percentage of companies from 2005 to today that have established a disciplined process in their approach to determine if they will outsource.

"[We're] seeing our clients set up internal processes and applications to create a service model for other internal organizations to leverage," Hemant Ramachandra, managing director of BearingPoint's Technology Solutions unit, wrote in an e-mail to InternetNews.com. "This can be software-as-a-service or even application as a service. Setting up the right governance structure is critical to ensure that outsourcing is leveraged appropriately."

In 2007 IBM increased its market share for IT outsourcing to 8.1%. EDS was second with a 5.3% increase followed by a 3.3% increase for ADP.

In know what you’re thinking. Woe is me. All of our jobs are going overseas. This is the initial knee-jerk reaction when one hears about outsourcing and its inevitable increased use. But this does not have to be the only truth. As our economy evolves and adapts to the changes in our society and new needs arise, the way we work and the makeup of our workforce will necessarily evolve as well. The largest increases in new businesses in the US are in small business and a large percentage of those new small businesses are home based. New companies will also need to be created to meet the changing model from ASP to the new approach of Web-based Software as a Service (“SaaS”), which allows businesses access to software functionality for a more cost effective monthly fee instead of the cost of the application’s license fee and the upfront cost of more hardware. Who these new companies will employ is yet to be determined.