Commentary

Bob Evans
Senior VP, Global CIO  

Are Your Software Vendors Force-Feeding You Needless Stuff?

Are your enterprise software vendors trying to make their problem - revenue targets - your problem by force-feeding you add-ons and modules and services you don't want or need? CIOs say this "value-destruction" approach manifests itself in three specific ways, according to Forrester VP Ray Wang's latest installment in his five-part series, "It's The Relationship, Stupid!"

Are your enterprise software vendors trying to make their problem - revenue targets - your problem by force-feeding you add-ons and modules and services you don't want or need? CIOs say this "value-destruction" approach manifests itself in three specific ways, according to Forrester VP Ray Wang's latest installment in his five-part series, "It's The Relationship, Stupid!"In "Part 3: Pushing products that clients don't need in order to grow revenues," Wang says that while software companies can try to justify this approach by saying they have quarterly numbers to hit, they are nevertheless running the risk of "jeopardizing brand value, trust, and market credibility for short-term gain."

In these days of ruthless budget-cutting among the customer set, is that really a wise approach? I think not, and CIOs who in this environment might be vulnerable to strong-arm tactics due to their companies' desperate circumstances are sure to have long memories that will stay fresh well into the time of improving business climates.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

And with more competition coming from new approaches and new companies via SaaS, cloud computing, hosted models, and more, Wang's message throughout his entire five-part series is a powerful one: will software companies be willing to exchange relatively modest short-term term revenue gains for ruined relationships in the long term?

Wang cites three approaches that CIOs say enterprise software vendors are employing that are focused solely on the revenue targets of the software companies rather than the business needs of the customers:

  • "Forcing clients to spend more to keep a low rate for maintenance." Wang cites an ERP director at a global oil and gas company who says that his company has "adopted a concerted focus to limit our exposure to this vendor" because of "how much they took our relationship for granted."
  • "Selling additional products that have no future road map because of post-acquisition roadmaps." The CIO at a North American manufacturing company said it has put a freeze on all future spending with this vendor for the next eight months" because it felt forced to purchase additional licenses before the vendor completed an acquisition, only to be told after the acquisition that the product was being discontinued and that no credits would be given.
  • "Suggesting additional consulting services that require additional product purchases." Wang says that an ERP program manager at a global consumer-products company experienced ongoing pressure of that sort. The pressure become so bad, the ERP manager said, that he finally "called members in our local user group and they gold us that other members have complained as well but the user group had been over-influenced by the vendor and was not able to assist."
  • These ham-fisted approaches seem so obviously counterproductive - why do some software companies insist on making the buyer-seller relationship even more complex than the underlying code? Be sure to check out the first two parts of Wang's five-part series, with the next two installments due on April 20 and April 27.


    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