Skip to content
Interface language: English
Audit / Signal

What do AI tools really cost your company?

Build a register of AI services, charges, uses and owners, then compare options without interrupting work.

Article language: English

An illustration of a woman looking at an architectural model through a large lens.
In this article

An invoice shows what a company paid for a tool. It does not show who uses it, what data enters it or whether a second service performs a similar function. That is why a discussion about AI costs should start with one register, with owners and dates.

We do not assume the company spends too much. A more expensive plan may solve an important permissions or collaboration problem. A small subscription may support a process the finance team does not know about. The review aims to establish what you pay for and which decisions you can make without interrupting work.

What information should an inventory start with?

Collect invoices, business-card statements, central purchasing lists and information from team leads. Ask about individually paid tools too if they are used for company tasks. Explain why you are gathering the information. People are more likely to describe their actual work when they know the result will help establish rules.

Start with a spreadsheet containing a repeatable set of fields:

  • Service name, provider, plan and company administrator address.
  • Person responsible for the purchase and the team using the tool.
  • Number of paid and assigned accesses.
  • Amount, currency, billing period and next renewal date.
  • Task performed in the tool and types of data supplied.
  • Information source, date checked and open questions.

Convert costs using one explicit rule. Annual and monthly invoices can look similar in a list even though they affect the budget differently. Retain original amounts and calculate monthly cost separately. Taxes, exchange rates and usage above the subscription also need their own columns.

What does the number of active users tell you?

First check the definition of activity. Signing in to an admin panel, opening an application and performing a task are three different events. Tools may report them differently. A chart without a definition can easily lead to a premature decision.

Microsoft provides service-usage reports in the Microsoft 365 admin centre. They can be compared with licence assignments to identify accesses for further investigation. Report scope and available data depend on the service and permissions. Use the official Microsoft 365 reports documentation as a reference.

An account with no recent activity belongs on a question list. It may belong to someone on leave, be used for monthly closing or support an infrequent task. Before removing access, ask the process owner to confirm. A saving followed by urgently rebuilding a needed environment has an additional cost.

How can you find overlapping subscriptions?

Compare the tasks people perform. Two chat services may handle different data, have different contract terms and retain history under different rules. Conversely, three differently named tools may all be used by the same team solely to summarise meetings.

For each task record the requirements: language, output quality, collaboration, export, permissions and integrations. Then check whether an already paid service meets them in practice. A short test using materials approved for use gives a better basis for a decision than a feature-list comparison.

The result may be consolidation, a plan change or retaining several services. Record why. Three months later it will be easier to distinguish a deliberate choice from another item on a card statement.

Where does Shadow AI fit?

Shadow AI means using AI tools outside the established purchasing and oversight process. A company may not know that its documents are entering an external service. Finding an application's name alone, however, does not explain which materials were submitted or the terms of the account.

Gather a description of the use and the data category. Identify who can check the contract, settings and access. Read provider documentation for the specific product and plan. Terms for a consumer account and a business version may differ; a brand name cannot replace that check.

Separate established facts from gaps in the register. “History settings not checked” is honest and useful. “The service is safe”, without a scope of assessment, tells little to the person who must approve its use.

How do you reconcile one register entry with several charges?

Give the tool its own identifier, independent of the name on an invoice. The same product may be purchased through different sellers or in several organisation accounts. Describe the service and use in one row and link the charges to it. Retain the original documents. This keeps the total from depending on whether a provider's name was entered identically each time.

Aeneia conceptual photography

Working example: a department has a subscription, an additional usage charge and a separate purchase for a project team. Instead of combining three amounts without distinction, record their scope and ask whether they cover the same people. If one payment reimburses an employee, mark the funding method. This is a proposed register layout, not data about a particular company.

Before totalling, check the period is complete and account for corrections. Do not compare part of a month with a whole year by simple multiplication if the usage pattern does not support it. When renewing a particular product, use the Copilot licence review (in Polish), where the purchase decision has its own record and confirmation of execution.

How do you compare two services doing a similar task?

Choose a task and specify material permitted for the trial. Record the required output, how it will be checked, correction time and export capability. Then perform the same action in both services. The mere presence of a “summarise” feature does not establish that the team receives a useful document with the required source. For extensive material, compare information omitted in a long AI context (in Polish) too, so accepted file size does not replace an assessment of what reached the output.

Add organisational constraints: the process owner's access, account management, collaboration and how use ends. One team may chiefly need to read particular documents; another may need a second person to take over the result. Preserve those differences rather than forcing one score across all roles.

Set trial conditions through AI pilot criteria (in Polish). If a tool bases answers on outdated sources, return to the company's knowledge architecture (in Polish). Replacing a subscription will not resolve a conflict between two instructions that are both in force. The comparison should also identify dependencies to correct before consolidation.

How do you find tools absent from central invoices?

Walk through a selected task with the person doing it. Ask about browser extensions, meeting add-ons, integrations and trial accounts. Initially request a description of the input and result without confidential content. The goal is to reconstruct how work is performed, so explain how you will use the information collected.

A Shadow AI review in a law firm (in Polish) develops this procedure for client documents. Whatever the industry, record no-cost tools too if they receive company materials. No purchase cost does not remove questions about the account, access and subsequent copies of data. For a local model, add dependencies found when testing work without internet access (in Polish), so the register describes the solution in use rather than just the model name.

A list alone does not approve every use. Entries needing clarification should go to the process owner and the person assessing relevant terms. Prepare sources using the audit materials checklist (in Polish), explicitly separating established facts from gaps.

When can an entry be closed?

For a tool being retired, record the contract end date, required export, task handover and permission check. Confirm that the provider accepted the instruction. Also check integrations and copies of outputs used by the team. Crossing a name off a list does not confirm these actions were performed.

Use an agreed set of evidence to close the entry: confirmation of the billing change, a new task owner and checked access to needed materials. We checked Microsoft's usage-report documentation on 27 October 2026; the scope of a report still needs to be read for the specific product. After a plan or organisational change, return to the definition before comparing numbers.

Link the account register to a separate task list. One licence can support several processes, and one process can use several products. In the AI use-case register, record the owner and reason for continued investment. Then calculate the total cost of the AI process (in Polish), including data preparation, output checking and corrections. For preparation, see the guide to preparing an AI use-case register (in Polish).

If the register is a spreadsheet, include a check of the spreadsheet used with AI (in Polish). Account names, dates, identifiers and formulas have different requirements. An automatic cell transformation should not silently change the meaning of evidence used for a decision.

How do you turn the register into decisions?

Prepare three lists: questions to clarify, changes awaiting approval and tools retained with reasons. Each item needs an owner, date and possible consequence. Put renewals and contractually established notice deadlines in a separate calendar.

Calculate amounts only after checking whether a change can actually be made. Distinguish a proposal from an approved cancellation and from savings visible on the next invoice. Those three numbers should have three different names.

The register should remain in use after the review. Add it to purchasing, role changes and employee departure processes. To start organising licences, uses and responsibilities, read about Aeneia Audit. For what an agent may do with company data, see the boundaries of agent work (in Polish).

Add a data-flow register if you need to understand a document's path through integrations. Before a broader review, prepare an index of audit materials. For preparation, see the guide to preparing an AI data-flow register (in Polish) and the guide to preparing AI audit materials (in Polish).

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear