Financial transition model
Show how investment converts into operating change.
The financial case is structured as a transition ledger: BrokerLink Portal and GroupLink build spend, Contact Center AI value capture, mainframe run-cost reduction, engineering throughput, and control-platform operating cost.
Report date
Updating...
Program case
$47.2M
Illustrative 5-year NPV from current business case.
Run-cost transition
FY27
Mainframe savings begin when workloads are retired, not merely migrated.
Service value
QA + FCR
Cleaner service outcomes reduce repeat work and coaching lag.
Control cost
Mandatory
Governance, evals, observability, and evidence are platform costs.
Investment ledger
Spend categories tied to outcomes and controls.
Financial review should connect spend to what is being built, what will retire, and which controls are required to operate safely.
| Category | Purpose | Value mechanism | Evidence needed |
|---|---|---|---|
| BrokerLink Portal | Broker user experience, workflow services, document handling, self-service, API integration. | Increase digital completion and reduce manual service leakage. | Release scope, adoption, completion rate, defect trend, API contract tests. |
| GroupLink Portal | Group administration, eligibility/account workflows, role access, reporting, service integration. | Reduce group servicing cycle time and improve data quality. | Task cycle time, source sync checks, role/access review, UAT evidence. |
| AI contact center | Agent assist, RAG, guardrails, CRM writeback, QA automation. | Faster lookup, better resolution, fewer repeat contacts, improved coaching. | Call replay, QA flags, adoption, agent edit rate, CRM note quality. |
| Mainframe migration | Assessment graph, landing zone, facade, data replication, parallel run, cutover. | Reduce legacy run cost through decommissioned jobs, interfaces, licenses, and contracts. | Retirement ledger, savings ledger, dependency signoff, cutover evidence. |
| AI SDLC platform | Agentic delivery, eval harness, secure release gate, AI inventory, audit store. | Increase delivery throughput without unmanaged risk or untraceable AI artifacts. | AI BOM, change evidence, eval output, blocked release reasons, delivery trend. |
| Governance and change | Policy, training, risk review, compliance alignment, operating-model rollout. | Lower operational, legal, privacy, and security exposure as adoption scales. | Policy trace, training records, control tests, incident response, access review. |
Cost transition chart
Mainframe savings only count when retirement is proven.
Migration cost peaks before the legacy run rate drops. The model separates build spend, coexistence cost, and verified retirement so savings are counted only when legacy work is actually removed.
FY26 build and assessment
Peak build
FY27 coexistence and cutover
Inflection
FY28 decommission savings
Capture
FY29 optimized run rate
Steady
Financial controls
Monthly program finance questions.
These questions should be asked monthly so the transformation stays tied to measurable operating outcomes.
Value realization
- Which workflow metrics moved?
- What was adopted by users?
- Which benefits are verified?
- What remains assumed?
Run-cost removal
- Which jobs are retired?
- Which licenses are removed?
- Which interfaces are closed?
- Which contracts changed?
Delivery health
- What shipped?
- What failed release gate?
- What needs rework?
- What reduced future risk?
Control spend
- What controls were built?
- What evidence is reusable?
- What exceptions remain?
- What audit risk changed?