The Integration Budget Is Missing the Hard Part

Integration budgets count software and migration. The expensive work is authority, data meaning, exceptions and operating redesign.

The answer

Integration budgets are precise about licences, consultants and migration hours. They are vague about the work required to make two institutions behave as one. Identity must be reconciled.

Integration budgets are precise about licences, consultants and migration hours. They are vague about the work required to make two institutions behave as one.

Identity must be reconciled. Data meanings conflict. Manual exceptions must be discovered. Providers need new authority. Staff must operate both states.

Budget scarce attention

Senior operators, legal advisers and domain experts become the critical path. Their time is consumed by decisions no implementation partner can make.

Value object — The Integration Friction Budget

- Authority reconciliation.

- Data and process discovery.

- Dual-running period.

- Control and evidence redesign.

- Management capacity.

- Contingency for unknown dependency.

Price delay to value

Connect each friction item to the synergy or separation milestone it can delay. The cost is not only the invoice; it is the postponed thesis.

The hard part of integration is not moving systems. It is rebuilding institutional truth while the business keeps operating.

Where this breaks

Budget owners estimate implementation effort and omit the discovery required before implementation can be safe. Unknown data meaning and authority then emerge as programme delay.

The operating move

Fund discovery, dual operation and senior decision capacity explicitly. Tie reserves to the integrations whose uncertainty threatens the thesis.

Price domain-expert time.

Reserve for parallel systems.

Budget evidence and reconciliation.

Track delay to synergy.

The test

Choose one “simple” migration and trace every exception, approval and external dependency. Use the result to recalibrate the rest of the budget.

Sources

  1. NIST: Cybersecurity Framework 2.0NIST: Cybersecurity Framework 2.0

    Primary authority

  2. NIST SP 1305: Cybersecurity Supply Chain Risk ManagementNIST SP 1305: Cybersecurity Supply Chain Risk Management

    Primary authority

  3. FINMA: Risk Monitor 2025FINMA: Risk Monitor 2025

    Primary authority

Jonathan P. De CollibusFounding Partner, Svperior / Cyber

Adam J. De Collibus

Adam co-founded Svperior and leads systems engineering from requirements through implementation. His work connects architecture, implementation, deployment, and operating discipline across complex environments where failure must be anticipated and technical capability must remain dependable under pressure.

Systems engineering / Technical architecture / Production operations / Operating resilience

Need to apply this to a specific situation?

Send us the initial context. If the matter fits, we will respond directly.

Send private inquiry
The Integration Budget Is Missing the Hard Part \