Lucidea logo - click here for homepage

Understanding Shadow AI: Risks, Costs, and Governance

Lauren Hays

Lauren Hays

March 18, 2025

According to writers at IBM, shadow AI is, “the unsanctioned use of any artificial intelligence (AI) tool or application by employees or end users without the formal approval or oversight of the information technology (IT) department.” 

What Should Special Librarians Know About Shadow AI?

Previously, I wrote about the importance of AI policies in special libraries, and hope your organizations have moved to develop policies or guidelines for the use of AI. When properly implemented, AI-powered tools can greatly enhance search, discovery, and operational efficiency in libraries. However, the rise of “shadow AI” highlights the need for oversight to maximize benefits while managing potential risks. 

Something to be aware of is that “shadow” AI usage can bring financial risks beyond compliance concerns. Some AI platforms employ usage-based pricing models, similar to how libraries pay per reader access for e-books. Without centralized oversight, costs can escalate quickly and unpredictably when employees independently adopt AI tools. 

Common AI Pricing Models

As AI capabilities become increasingly embedded in business software and services, organizations need to carefully evaluate the various pricing structures offered by vendors. Some common models include: 

  • Pay-per-token or pay-per-query pricing 
  • Monthly subscription tiers based on usage volumes 
  • Enterprise licensing with predetermined usage limits 
  • Hybrid models combining fixed and variable costs 

Each pricing model has different implications for budgeting and cost control. For example, usage-based pricing offers flexibility but can lead to surprise expenses if usage spikes unexpectedly. Fixed-cost models provide more predictable budgeting but may result in paying for unused capacity. 

Understanding Your Library’s AI Needs

To make an informed decision, organizations should: 

  1. Audit current and projected AI usage across departments 
  2. Compare total cost of ownership across different pricing models 
  3. Consider implementation and integration costs 
  4. Evaluate scalability needs as AI adoption grows 
  5. Account for potential training and support requirements 

The key is not to automatically reject or embrace any particular pricing model, but rather to thoroughly assess your organization’s specific needs, usage patterns, and budget constraints. This evaluation should be part of a broader AI governance strategy that balances innovation opportunities with cost management and risk control.

By proactively creating an AI policy and governance strategy, libraries and other organizations can harness its power while maintaining cost efficiency and oversight. 

Lauren Hays

Lauren Hays

Librarian Dr. Lauren Hays is an Assistant Professor of Instructional Technology at the University of Central Missouri, and a frequent presenter and interviewer on topics related to libraries and librarianship. Please read Lauren’s other posts relevant to special librarians and learn about Lucidea’s powerful integrated library systems, SydneyDigital and GeniePlus.

**Disclaimer: Any in-line promotional text does not imply Lucidea product endorsement by the author of this post.

Similar Posts

Leave a Comment

Comments are reviewed and must adhere to our comments policy.

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Pin It on Pinterest

Lucidea logo - click here for homepage
Lauren Hays
SydneyEnterprise's Request Management Dashboard in a browser on a laptop.
Lauren Hays
Keeping Up with Copyright and Generative AI: What Special Librarians Need to Know
Interview with an Author: Fernandez on Streaming Video Collection Development
Interview with the Author: Saffady on Information Governance Technologies
Reflections on David Epstein’s Range: How Generalists Triumph in a Specialized World
Lucidea logo - jump to home page here
undefined
undefined
undefined
undefined
undefined
Share This