On this page
An AI initiative's costs extend beyond its software purchase, into budgets outside the sponsor's. The business unit using a tool may pay for licenses while central teams provide cloud infrastructure, maintain its data and support the service. Staff time spent checking the output can remain within departmental budgets rather than appearing in the initiative's cost report.
This division of expenditure makes it difficult to assess returns. Finance may have the underlying records, but reviewers of one initiative still need to bring together the costs incurred on its behalf and an appropriate share of the services it uses.
Forrester's November 2026 analysis of AI cost classification addresses that problem by connecting expenditure to AI capabilities and then to the outcomes they support. The practical starting point is a cost view for one initiative, with allocation assumptions that finance, the service owner and the business owner can explain.
The initiative boundary and reporting period
Start with the business result the initiative was approved to deliver. Record which systems, teams and activities are needed to produce it, including work funded outside the sponsor's budget.
For a customer-service assistant, the scope would include the model, the search service it uses, maintenance of approved guidance, integration with the service platform and staff review. The worked calculation later in this article uses this hypothetical application to show how those costs can be combined.
Define the reporting period before adding those costs. Separate expenditure incurred to date from the forecast cost of operating the service over the next year. Comparing a full year of expected benefits with one month's usage bill would overstate the return.
Keep the scope stable between reviews. If the assistant expands to a second business unit, record that change alongside the additional costs and expected benefit. Reviewers should be able to distinguish an increase in unit cost from an increase in the amount of work supported.
Cost categories that reconcile with finance
Use the existing cost hierarchy where it can accommodate the expenditure. Add detail only where reviewers need it to understand a material cost or make a decision.
A practical initial view should cover:
- Models and software: provider subscriptions, model access and usage charges.
- Infrastructure: cloud processing, storage, search services and monitoring.
- Data and integration: preparing source material, maintaining connections and correcting data problems.
- People and process: implementation, support, human review, training and changes to working procedures.
Record the initiative against the relevant cost items so that expenditure can be brought together without replacing the finance hierarchy. An AI tag identifies the type of work; an initiative identifier shows which investment incurred the cost.
Keep accounting treatment separate. CapEx and OpEx describe how finance treats expenditure, rather than what was purchased or which initiative uses it. A cost item can retain its operational category and carry the accounting attribute finance assigns.
What each AI cost item carries
The finance hierarchy stays as it is; the cost item carries the extra detail
Recorded on the cost item- Cost categoryWhere the item sits in the existing finance hierarchy
- AI tagIdentifies the type of work
- Initiative identifierShows which investment incurred the cost
- Accounting treatmentCapEx or OpEx, assigned by finance as an attribute, not a separate branch of the hierarchy
A separate AI classification system would create another set of records to reconcile. Retain the category definitions and identifiers that finance uses, including those in the ERP system, and document any additional detail needed for initiative reporting.
Shared-cost allocations with named owners
Direct costs are relatively straightforward when an invoice or usage record identifies the initiative. Shared services require a rule.
In the customer-service example, a search platform might support several assistants. Usage could be a reasonable allocation basis if reliable records are available and consumption explains the cost. A fixed platform subscription might require a different method, agreed with finance and the service owner.
Document the cost being allocated, the basis for the split, the reporting period and the person responsible for maintaining it. Where the method uses an estimate, label it as an estimate. Staff time can be estimated from an agreed workload assessment when detailed time records are unavailable.
Apply the same principle to shared benefits. If two initiatives support the same improvement in customer-service performance, assigning the full benefit to both would overstate the combined return.
The allocation method should be consistent enough to support comparison, but the figures it produces should be no more precise than the records behind them. If a plausible change in an allocation assumption materially changes the total, show both calculations and explain which assumption the service owner considers more representative.
A worked monthly cost calculation
Use a simple calculation to test whether the categories and allocation rules produce a total that the owners can explain. The figures below are illustrative, not benchmarks or a recommended spending level.
Suppose the customer-service assistant incurs $4,000 in monthly model charges. It uses 30% of a shared search service that costs $6,000 a month, so its allocated search cost is $1,800. The service owner has confirmed that recorded usage is an appropriate basis for this split.
Data maintenance and integration support account for another $2,000. Staff review takes an estimated 80 hours at a finance-approved loaded labor rate of $50 per hour, adding $4,000. The resulting monthly operating cost is $11,800, comprising $4,000 in model charges, $1,800 in shared search costs, $2,000 in support and $4,000 in staff review.
Keep the supporting records beside that calculation: the invoices, usage report, staff-time estimate and approved labor rate. Check that the $2,000 support figure excludes the staff-review hours already counted. Otherwise the total would include the same effort twice.
Record implementation costs separately from this monthly operating view. If the initiative required $36,000 of setup work, show that amount and its accounting treatment alongside the operating forecast. Do not silently add the full setup cost to each month's total or mix an amortization charge with the same underlying expenditure.
One month of operating cost for the assistant
Illustrative figures for the hypothetical customer-service assistant, not benchmarks
Monthly operating cost- Model chargesMonthly model charges$4,000
- Shared search service30% of a $6,000 monthly service, split by recorded usage$1,800
- Data and integration supportData maintenance and integration support, excluding staff-review hours$2,000
- Staff reviewEstimateAn estimated 80 hours at a finance-approved loaded rate of $50 per hour$4,000
An allocated cost is also different from a cash saving. Retiring this assistant would not necessarily reduce the shared search subscription or payroll. For that separate decision, use the guide to deciding when an AI initiative should end.
A reconciled baseline for the next review
Choose an initiative with a named business owner and an upcoming review. Bring together its direct expenditure, shared-cost allocations and internal effort for the agreed period.
Ask finance to reconcile the recorded expenditure with its source records and confirm the accounting treatment. Ask the service owner to confirm the allocation assumptions and the business owner to confirm the process costs.
Record gaps explicitly rather than replacing them with zero. The next review should show which estimates have been replaced by actuals and explain material changes in the total.
Before extending the approach, assign an owner and a replacement date to each material estimate. Use the next review to check those replacements and test whether the allocation methods still reflect usage. Keep the categories consistent with Kiplot's guide to structuring cost hierarchies as more initiatives enter the reporting process.







