APAC CIOOutlook
About UsConferencePartner With Us
  • Technologies
    • Blockchain
      Data Intelligence and Management
      Digital Transformation
      FinTech
      Generative and Agentic AI
      Low Code No Code
      Mobile Application
      Networking
      Robotics
      Storage
      Wireless
  • Industries
    • Automotive
      Aviation
      Banking
      Construction
      E-Commerce
      Food and Beverages
      Healthcare
      Insurance
      Logistics
      Manufacturing
      Retail
      Supply Chain
      Travel and Hospitality
  • Platforms
    • Microsoft
      Salesforce
      SAP
  • Strategic Solutions
    • Business Intelligence
      Contact Center
      Corporate Finance
      CRM
      Cyber Security
      Data Center
      Enterprise Asset Management
      Enterprise Performance Management
      IT Infrastructure and Services
      Managed Services
      Procurement
      Unified Communication
      Workflow
  • Home
  • CXO Insights
  • Leadership Perspectives
  • Innovation Insights
  • Research
  • News
  • Whitepapers
  • CXO Awards
#

Apac CIOOutlook Weekly Brief

×

Be first to read the latest tech news, Industry Leader's Insights, and CIO interviews of medium and large enterprises exclusively from Apac CIOOutlook

Subscribe

loading

THANK YOU FOR SUBSCRIBING

  • Home
Editor's Pick (1 - 4 )
left
Why Share Point is a Robust and Powerful Digital Platform?

Sandy Jacolow, CIO, Silverstein Properties

The Future of SharePoint from a CIO

Sallie Wright, CIO, Fulton County Georgia

Travel APIs: Easing the Turbulence from Origin to Destination

Matt Minetola, EVP & Global CIO, Travelport

Tips for Evaluating APIs as Part of the Build vs Buy Strategy

Donna DeMarco, Co-Founder & VP, Viddler

Why Your API Should be Your Next Product

Todd Mezrah, VP, Drawloop Division, Nintex

right

Application Lifecycle Management

Judi Flournoy, CIO, Kelley Drye & Warren LLP

Tweet
content-image

Judi Flournoy, CIO, Kelley Drye & Warren LLP

It wasn’t long ago that buying software programs was a routine activity for Law Firms and Law Departments. What has changed, particularly in the last five years, is not only how we buy software, but how we manage it.

Application Lifecycle Management is many things. It is a process, a discipline and a strategy.

If you were to review the list of applications used by most law firms you would quickly identify the typical programs such as the Microsoft Office Suite, a document management system, a time and billing system and other tools.

Most software companies license their software based upon the “enterprise” model where the number of users in an organization drives the per seat cost. The total per seat cost then drives the annual maintenance which can be upwards of 20%. percent.

So what’s changed? A number of things. Firstly, whenever we evaluate new software programs whether they are cloud based aka Software as a Service or SaaS, or hosted on premises we are looking not only at the functionality of the program but also how it fits into our information governance programs and our information security programs.

Check Out: PLM Software Companies

If cloud based, does the software meet our basic security requirements? Is our data secured in the hosted facilities systems? Is the data encrypted? Who holds the encryption keys? If on premises, does the software integrate with existing systems? Is it compatible? What features are most relevant? Are there any security settings that we need to implement?

Secondly, how we buy or pay for software is changing. More and more firms are negotiating new terms and conditions that reflect today’s business climate. This is particularly true of the traditional library research programs. The business reasons for negotiating favorable contracts not withstanding, the reality is we do not have to build a one size fits all desktop anymore which means that we neither deploy nor should we have to pay for every attorney, staff or other professional to be licensed to use software they will never use.

Our approach is quite simple. Find the best software or service and then negotiate the pricing based upon what we really need. If we are confident that only 2% percent of our community will use the software that is the basis for the software purchase. So instead of entering into an Enterprise Agreement, we buy in smaller quantities say 15-30 licenses. Then we negotiate the contract terms to include a provision to true up to the actual utilization of the software if it exceeds the base purchase or subscription.

Why do this? Our firms are responding to the pressures of our clients to keep costs down.

How? One way of doing that is to:

1.Truly understand what you need and who is going to use it

2.Not allow any agreement to auto-renew

3.Start small with any new software program and monitor adoption

4.Make sure that which is well intentioned is well utilized.

5.Jettison anything that isn’t being used. This goes back to number

As technologists, business strategists, business owners and administrators our job is to insure that the business gets the most value of any investment it makes. This means avoiding parking a software program never to revisit the original decision to purchase it. Constant evaluation and monitoring are key.

tag

Information Security

SaaS

Document Management

Weekly Brief

loading
Featured Issue

I agree We use cookies on this website to enhance your user experience. By clicking any link on this page you are giving your consent for us to set cookies. More info

APAC CIOOutlook
Follow on LinkedIn

About

  • Home
  • About Us
  • Partner With Us

Stay Connected

  • Subscribe
  • Newsletter
  • Sitemap

Contact Us

  • editor@apacciooutlook.com
  • sales@apacciooutlook.com
  • marketing@apacciooutlook.com

Legal

  • Editorial Policy
  • Privacy Policy
  • Terms of Use

© 2026 APAC CIOOutlook. All rights reserved. Headquarteblue in Fort Lauderdale, FL, USA.

This content is copyright protected

However, if you would like to share the information in this article, you may use the link below:

https://api.apacciooutlook.com/ciospeaks/application-lifecycle-management-nwid-1994.html