Capabilities

We sign off only what can be accepted

"Digital transformation" is not a deliverable. What can be accepted is a data dictionary signed by three functions, a process engine rewritten to your committee rules, a field-level permission model, a response time written into the contract, and an AI module you can switch off. That is how the six capabilities are cut.

CMMI Level 3 engineering100+ software copyrights60%+ engineering headcountPublic cloud, private cloud or isolated intranet

How the capabilities combine

Two set direction, three build capacity, one keeps it running

Most clients arrive asking for platform delivery; what determines whether the platform survives year two is data governance. We will not recommend starting an implementation without a data dictionary and a named owner for each definition — which is why strategy and platform are separate capabilities with separate leads, artefacts and durations.

Groups usually buy three or more together: blueprint first, definitions next, then business-line modules released in sequence.

Six capabilities

Each page gives method, artefact list, typical duration, technical base and deployment options.

Artefacts, duration, acceptance

Standard ranges; group programmes are re-sequenced against the phased roadmap. Clock starts when the work-breakdown structure is agreed.

CapabilityCore artefactsTypical durationAcceptance method
Strategy & blueprintBreak inventory, data dictionary v1, roadmap, business case5–7 weeksSign-off by business, risk and finance
Platform deliveryWorkflow configuration, legacy migration, field permissions, integrations8–16 weeksUAT pass rate plus a live filing rehearsal
AI agents & riskOCR extraction, indicator alerts, behaviour logs, effort costing4–10 weeksSampled accuracy with reviewable evidence
Data governance & metricsMetric library, change process, quality rules6–12 weeksDefinition-consistency audit
Security & localised ITTopology, encryption chain, compatibility list, remediation3–8 weeksThird-party assessment report
Delivery & operationsSLA, runbook, training and knowledge base, quarterly reviewFrom year oneResponse-time attainment

Nineteen business systems on one dictionary

Names follow the company’s published product scope. Cross-system reporting shares one dictionary, so consolidation stops drifting.

PE/VC investmentGuidance fund / FOFInvestment bankingFinancial holding groupInvestor relationsManager portalWealth managementReal-estate fundDebt trading & issuanceInfrastructure investmentAMC operationsREITsOA collaborationDistressed assetsSOE online supervisionFamily officePortfolio risk monitoringFundraising & LP reportingAI desktop behaviourMicro-lending

Engagement questions

Can we buy the advisory work without the build?
Yes. Assessment and blueprint are a contract in their own right; you keep the dictionary and roadmap and procure delivery elsewhere if you wish. Our position is unchanged: without agreed definitions, whoever implements will rework.
We have an in-house team. What do we need from you?
Usually governance plus reusable components: metric definitions, the change process, module-level interfaces, and the 18 warning indicators and valuation logic delivered as libraries instead of being rebuilt.
Does the AI layer send data outside our network?
In intranet deployments the OCR and indicator models run inside the client environment with no outbound path. Enabling each agent is a client permission; disabling one leaves the workflow intact.
What happens after the free year?
One year of service after acceptance is a standard contract term. Beyond that, operations and iteration are priced annually and include the quarterly definition review and response-time commitments.

Start with a current-state assessment

In 45 minutes we map the breaks across your pre-investment, portfolio, post-investment and reporting chain, then set out a phased path.