The TCO of Automation: How CFOs Should Measure the ROI of an Operations Platform

Budget season for 2027 is close. On most CFOs' desks right now sits a stack of automation proposals: an e-approval system, a digital signature tool, a contract management platform. Each one comes with a very clear number, the annual license fee, and each one promises to "save time and improve efficiency."

The problem is that the two numbers that matter most are missing from the slide: the total cost of ownership (TCO) over three to five years, and the benefits expressed in money. Without them, an investment decision turns into a license price comparison, even though the license is usually the smallest part of the story.

This article offers a measurement framework that lets CFOs evaluate an operations platform in financial terms: where the real costs sit, which benefits can be measured, and how to calculate ROI rigorously enough to put into the annual plan.

The Purchase Price Is Not the Cost

An automation system generates costs in three layers, and usually only the first layer makes it into the business case.

• Visible costs: license or subscription fees, initial implementation, and infrastructure if the system runs on premise.

• Operating costs: integration with ERP, CRM, and accounting systems; user training; annual maintenance, upgrades, and technical support.

• Hidden costs: calling the vendor every time an internal rule changes; staff still re-entering and reconciling data between systems by hand; spreadsheets, chat groups, and paper processes growing alongside the system because it cannot keep up with reality.

The third layer is the hardest to see because it never appears on a vendor invoice. It is spread across payroll, approval wait times, and contracts signed late or signed wrong. Two systems with the same license price can have very different TCO, simply because one needs reprogramming every time the business changes how it works, while the other can be reconfigured by the business itself.

Four Benefit Lines a CFO Can Put a Number On

Benefits deserve the same discipline as costs. Instead of vague phrases like "higher productivity," measure the four value lines below. Each one can be assigned a figure.

1. Contract Value Erosion

Contracts are where most of a company's revenue and spend is committed. The ROI of Contracting Excellence report by World Commerce & Contracting (WorldCC) in collaboration with Deloitte, based on data from more than 1,200 organizations, estimates average contract value erosion at 8.6%. The best performers lose a little over 3%, while the worst lose more than 20%.

Erosion is the gap between the value expected at signing and the value actually realized: negotiated discounts that are never applied, late-delivery penalties nobody claims, auto-renewals that roll over without a price review. According to the research, most of the loss comes from a fragmented contracting process rather than the wording of individual contracts. We explore this view further in Contracts Are Assets, Not Paperwork: A CFO's View of Agreement Lifecycle Management.

For a CFO, the question should be concrete: what is the company's total annual contract value, and how much money does each percentage point of erosion represent?

2. Cycle Time and Working Capital

Cycle time is the number of days from a contract request to the moment the contract takes effect. Until a contract is effective, goods are not delivered, invoices are not issued, and cash is not collected. Every day of delay is a day of working capital locked up. WorldCC found that contract cycle times vary enormously between organizations, with the best performers operating almost four times faster than the worst.

Here is a real example. An FMCG distribution enterprise with more than 300 suppliers used to need 12 to 15 business days to push a vendor contract through five approval layers. After digitizing the approval workflow, that time fell by 60% to 5 to 6 business days, and more than 90% of low-value contracts now clear approval within 48 hours. Read the full story: Distribution Enterprise Cuts Vendor Contract Approval Time by 60% with Kyta eFlow.

3. Cost of Change

Approval thresholds change, contract templates change, new decrees take effect. These things happen several times a year. The question for a CFO is how long each change takes to reach the system, how much it costs, and how staff process contracts while they wait.

If the answer is "submit a request to the vendor, wait a few weeks, approve by email in the meantime," the company pays for change twice: once in money and once in control risk. This is also one of the questions we suggest leaders ask in 5 Questions Every CEO Should Ask About Their Operating Architecture Before 2027 Planning.

4. Manual Labor Hours

This is the easiest benefit to measure: the hours each month staff spend re-entering data, reconciling between systems, searching for paper contracts, and messaging each approver to ask about status. In the distribution example above, each procurement employee saved an average of 4 working hours per week. Multiply those hours by the average loaded labor cost and you have a figure.

A Sample ROI Calculation

To see how the framework works, take a hypothetical company. The figures below only illustrate the method. They are not a price quote or a promise of results.

Working capital is calculated separately because it is a one-time release. If sales contract revenue is VND 120 billion per year (about VND 329 million per day) and the signing cycle shrinks by 7 days, roughly VND 2.3 billion in cash arrives earlier.

The three-year ROI formula: ROI = (Total three-year benefit - Three-year TCO) / Three-year TCO.

Under these assumptions, total three-year benefit comes to about VND 8.3 billion. Any option with a three-year TCO below that level delivers positive ROI from three benefit lines alone, before counting working capital. What matters is that the company fills in its own numbers instead of relying on figures supplied by a vendor.

Five Common Mistakes When Measuring Automation ROI

• Comparing license prices only: ignoring integration costs, cost of change, and the manual hours that remain.

• Skipping the baseline: without "before" data, there is no way to prove "after." Measure cycle time, approval steps, and labor hours before rollout.

• Measuring too late: waiting a full year removes the chance to adjust. Set a measurement checkpoint at 90 days.

• Counting benefits nobody owns: each benefit line needs an owner, usually the head of procurement, legal, or accounting.

• Forgetting the cost of doing nothing: keeping the current process also has a TCO, made up of contract erosion, locked working capital, and repeated manual work.

A 90-Day Roadmap to a Real ROI Figure

• Days 1 to 30, measure the baseline: pick one high-volume process, such as vendor contract approval. Record average cycle time, number of steps, number of manual re-entries, and weekly labor hours.

• Days 31 to 60, run a pilot: digitize that process at one branch or one department, keeping the same set of metrics.

• Days 61 to 90, compare and decide: set the before and after figures side by side, convert them to money across the four benefit lines, and decide on rollout based on data rather than impressions.

How Kyta Platform Supports This

Kyta Platform by FPT IS is designed as an operations orchestration layer that sits on top of existing systems, rather than one more standalone tool. Its modules can be rolled out step by step, in line with the roadmap above:

• Kyta eFlow: automates approval workflows through low-code/no-code configuration, with routing by contract value and type, mobile approval, and real-time status tracking.

• Kyta Signature: signs contracts digitally inside the approval flow, shortening the signing stage.

• Kyta eCLM and Kyta ALM: centralize contract storage and lifecycle management, with renewal alerts and obligation tracking to limit value erosion.

When approval thresholds or contract templates change, business administrators can reconfigure the workflow themselves without writing code, keeping the cost of change low.

Conclusion

For an operations platform, the right question is not "what does this software cost?" It is "what is the total cost over three years, and how much money does it keep in the business each year?" When it is measured across four value lines (contract erosion, working capital, cost of change, and labor hours), an automation decision becomes an investment decision backed by data, rigorous enough to go into the 2027 plan.

Want to discuss how to measure ROI for your own processes? Contact the Kyta Platform team:

• Hotline: 1900 636 121 (ext. 2)

• Email: support.kyta@fpt.com

• Website: kyta.fpt.com