The Hidden Cost of Fragmented Operations: The Numbers Your P&L Doesn't Show

Every finance leader knows the cost of the systems already in place: licences, implementation fees, IT and operations headcount. Those numbers are visible, audited and debated in every budget cycle. The more expensive number is the one no report shows: the cost of work that falls between systems.

As Vietnamese and FDI enterprises enter 2027 planning, this invisible line deserves a place on the executive agenda. Not because it is new, but because it grows with every new tool bought to solve a local problem.

What fragmentation actually costs

World Commerce & Contracting (WorldCC), working with Deloitte on data from more than 1,200 organisations, estimates that the average business loses 8.6% of contract value through poor contracting processes. The best performers keep that erosion a little above 3%. The worst lose more than 20%.

For a CFO, that range is the real story. Two companies with similar revenue, similar contract portfolios and similar teams can end the year several percentage points of value apart, simply because one runs its agreements through a connected process and the other runs them through inboxes, spreadsheets and individual memory.

WorldCC's 2025 research adds another clue: on average, contract-related data is spread across 24 systems. When information lives in 24 places, nobody really owns the whole picture.

Where the value leaks

Fragmentation rarely looks like a crisis. It looks like ordinary friction, and three patterns appear again and again.

1. Approval latency. A purchase request waits for a signature from a manager who is travelling. A contract sits in the legal queue because nobody flagged it as urgent. Each delay is small, but across hundreds of transactions a month it adds up to weeks of lost cycle time, late supplier onboarding and deals that close a quarter late.

2. Re-keyed data. The same customer, supplier or employee record is typed into the CRM, the ERP, the HR system and a spreadsheet. Every copy is a chance for error. Every error needs someone to find and fix it, and some are never found at all.

3. Forgotten obligations. Once signed, many contracts go into a folder and are forgotten. Renewal dates pass. Price escalation clauses trigger unnoticed. Service levels are missed without penalties being claimed. The WorldCC data shows these are not edge cases; they are where most value erosion happens.

None of these appears as a separate line in the income statement. They are absorbed into longer cycle times, higher headcount, write-offs and missed savings.

Why more tools have not solved it

Most enterprises have responded to these problems in good faith: a signing tool here, a workflow app there, another module in the ERP. Each purchase solves one department's problem. Together, they increase the number of systems the next process has to cross.

This is the paradox many CIOs now describe. The organisation is more digital than it was five years ago, yet end-to-end processes are not faster, because the gaps between tools have multiplied.

For FDI enterprises the problem compounds. A Vietnamese subsidiary may run locally compliant e-signing and electronic identity verification, while regional headquarters requires reporting in its own format and approvals under its own delegation-of-authority matrix. Without a shared operating layer, the local team becomes the integration layer, manually.

From tools to orchestration

Business Orchestration and Automation Technologies (BOAT) describes a different approach. Instead of adding another point solution, BOAT connects people, data, documents and decisions across the systems an enterprise already uses, so that a process runs from start to finish in one governed flow.

In practice, an orchestration layer does four things:

• Makes every process visible: who holds a request, how long it has waited, where it is blocked.

• Captures data once and reuses it across steps and systems.

• Applies rules consistently: approval thresholds, compliance checks, identity verification.

• Leaves an audit trail by design, rather than rebuilding one at audit time.

Low-code and no-code configuration matters here, because it lets operations and IT adjust these flows in days instead of launching a new development project every time the business changes.

How to put a number on it

Executives do not need a perfect model to start. A practical first estimate uses three questions for each critical process, such as procure-to-pay, customer contracting or employee onboarding:

• Cycle time: how many days from request to completion, and what does each day of delay cost?

• Touch points: how many times is the same data entered or checked manually?

• Exposure: how many active contracts have renewal dates, obligations or penalty clauses that no system is tracking?

Multiply the answers by transaction volume and the hidden cost stops being hidden. In most organisations, two or three processes account for most of the leakage, which also makes them the natural place to start.

What to bring to the 2027 budget discussion

Fragmentation is not an IT line item. It belongs in the same conversation as working capital, margin and risk. Leaders who see it that way usually make three decisions:

• Name an owner for each end-to-end process, not only for each system.

• Fund an orchestration layer before funding another point tool.

• Track a small set of operational measures, such as cycle time and contract value erosion, with the same discipline as financial KPIs.

The gap between 3% and 8.6% value erosion is not a technology gap. It is an operating model gap, and it can be closed deliberately.

Kyta Platform, built by FPT IS on BOAT principles, helps enterprises connect electronic identity verification, approvals, digital signing and contract management into one governed flow, on top of the systems they already run.

Kyta Platform - kyta.fpt.com | ☎ 1900.636.121 ext 2 | ✉ support.kyta@fpt.com