Commentary

Bob Evans
Senior VP, Global CIO  

Do CIOs Want SaaS Contracts To Extend To 3-5 Years?

Blogger Vinnie Mirchandani says that while today's duration for SaaS deals averages 1.5 years, "the secular trend is towards higher renewals…and multiyear deals. SaaS will likely become like outsourcing contracts -- 3, 5, 7-year deals." Sounds good in theory, but will CIOs go for it?

Blogger Vinnie Mirchandani says that while today's duration for SaaS deals averages 1.5 years, "the secular trend is towards higher renewals…and multiyear deals. SaaS will likely become like outsourcing contracts -- 3, 5, 7-year deals." Sounds good in theory, but will CIOs go for it?Writing about disruptive trends and economics in technology on his deal architect blog, Mirchandani says CIOs will be more likely to accept longer-term deals if SaaS vendors "allow customers more expansion/contraction options over the term of the contract." With that, Mirchandani highlights another key issue in the bitter battle Salesforce.com is waging against Oracle, Microsoft, and SAP.

That could provide significant value for SaaS vendors for two reasons: First, it gives those vendors a more-predictable revenue stream and lets them step away from having to run a permanent campaign to re-sign customers year after year; and second, it gives Wall Street a well-grounded rationale to consider raising the valuations for successful SaaS vendors.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Under the current model, Mirchandani says, with signed SaaS deals averaging 1.5 years, "Wall Street does (and should) not assign a value to that 'likely' deferred revenue beyond that" limited term.

In return, SaaS vendors will need to give CIOs the type of flexibility Mirchandani highlights as well as perhaps a few other perks such as a limited degree of customization, or premium-level security assurances.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links