Build–Operate–Transfer Engagements.
XVICA designs, builds, and operates infrastructure to a specified maturity threshold, then transfers it with documentation, runbooks, and transition support.
Model
For organisations that intend to bring capability in-house but need delivery quality and pace now.
Under Build-Operate-Transfer, XVICA designs, builds, and operates the platform until it reaches a specified maturity threshold. Maturity is defined concretely (control effectiveness measured, documentation reviewed, runbooks exercised, knowledge transfer assessed against a defined rubric) before transfer proceeds. Post-transfer support remains available on a defined tier where required.
Three phases, one programme
Each phase has defined entry and exit criteria. Transfer does not proceed against time; it proceeds against maturity.
Build
XVICA designs and builds the platform against specified outcomes. Client team contributes domain knowledge and participates in review milestones. Architecture, controls, and documentation produced to institutional standards from day one.
- Joint specification and architecture
- Build to production standard
- Control evidence and documentation
- Parallel run and cutover
Operate
XVICA operates the platform under SLA. Incidents are handled; changes are managed; runbooks are exercised in real conditions, not only in drills. Maturity indicators are monitored against the transfer rubric.
- Operate under defined SLA
- Structured incident management
- Runbooks exercised in production
- Maturity measured against rubric
Transfer
Transfer proceeds when maturity criteria are independently verified. Documentation, runbooks, training, and structured shadow operations deliver capability uplift alongside the platform handover.
- Independent maturity verification
- Knowledge transfer against rubric
- Shadow operations and dual-run
- Post-transfer support tier
Maturity is measured, not asserted
Transfer only proceeds when the platform and the receiving team both clear specified thresholds.
Control effectiveness
Controls evidenced through at least two attestation cycles with independent review of findings and closure.
Incident maturity
Incident runbooks exercised under real conditions; post-incident reviews completed and remediations closed.
Team readiness
Receiving team assessed against defined competency rubric; gaps closed through structured knowledge transfer.
Observability
Monitoring, alerting, and dashboards exercised; on-call procedures tested across severity tiers.
Change management
Change, release, and configuration processes operated by the receiving team under XVICA oversight before transfer.
Dual-run proof
Specified period of dual-run operation with the receiving team as lead and XVICA in shadow before formal handover.
How BOT is priced
Each phase has its own commercial structure. Fees land when milestones are verified, not only when invoiced.
Build phase
Milestone-based fees against specified deliverables. Control evidence, documentation, and production readiness are explicit milestones with independent acceptance.
Operate phase
Time-bounded operating fees with SLA-linked service credits. Operating scope, hours, and out-of-scope handling documented in the operating agreement.
Transfer phase
Transfer fee payable against independently verified maturity criteria. No transfer fee released for a milestone that is not verified.
Post-transfer support
Tiered support for twelve to twenty-four months covering severity-1 incident response, major-change review, and scheduled knowledge-transfer sessions.
Where BOT is the right model
In-house end state
Organisations whose long-term intent is to operate the capability with their own team, but who need delivery quality and pace now.
Capability to be built
Situations where the receiving team does not yet exist at the required scale; knowledge transfer is part of what is purchased.
Regulated deadlines
Regulatory or commercial deadlines that cannot wait for internal hiring and ramp cycles.
Discrete scope
Scope bounded enough to hand over cleanly. Work that genuinely requires long-horizon partnership fits Co-Build better.
Documented standards matter
Organisations that value the enforced discipline of building to transferable standards: documentation, runbooks, test evidence.
Board-level visibility
Situations where the board needs the assurance of a specified transfer path rather than open-ended external dependency.
What clients expect of us
Measured maturity
Transfer against a concrete rubric, not an arbitrary date.
Team uplift
Receiving team built alongside the platform, not handed documentation.
Independent verification
Transfer milestones checked by a party with no commercial incentive to pass them.
Graceful exit
No transfer fee released for a milestone that is not verified. Structure rewards genuine handover.
Capabilities commonly delivered under BOT
Transaction & Settlement Systems
Core transaction platforms built, operated to maturity, then transferred with full documentation.
Read onIntegration Fabrics
Integration platforms built and operated through initial modernisation, then handed to internal teams.
Read onSecurity Infrastructure
Security platforms built to institutional standards, operated until control maturity, then transferred.
Read onBuild-Operate-Transfer
The questions that come up most often during briefings.
When is Build–Operate–Transfer the right model?
When you intend to bring capability in-house over time but need delivery quality and pace now. XVICA designs, builds, and operates the platform to a specified maturity threshold, then hands it over with documentation, runbooks, and transition support.
How is the transfer point defined?
By concrete maturity criteria agreed at contract: control effectiveness measured and evidenced, documentation complete and reviewed, runbooks exercised in production incidents, and knowledge transfer assessed against a defined rubric.
What support is available after transfer?
Tiered post-transfer support is available, typically for twelve to twenty-four months, covering severity-1 incident response, major-change review, and scheduled knowledge-transfer sessions. Ongoing managed operations remain an option if priorities change.
How are the operate and transfer phases priced?
Operate fees are time-bounded with SLA-linked components. Transfer fees are milestone-based against the maturity criteria. No fee is payable for a milestone that is not independently verified.
Compare with Platform Adoption and Co-Build + Operate.
Build it, run it, hand it over.
Request a confidential briefing to discuss whether Build-Operate-Transfer fits your end-state intent.
Talk to sales