Build, Operate, Transfer
We build the capability, run it with your people, then transfer the team and its work to you.
A Capability Centre Has to Stand on Its Own
A capability centre is more than a delivery team. It has to become an operation your own people can run without the provider.
Build, operate, transfer joins technical leadership close to your business with XSIS engineering capacity, and ends with your team owning the work.
What You Get
You end with a running centre, a trained team and the records that prove you own both.
A Target Operating Model
The roles, the service catalogue, the decision rights and the reporting lines of the centre.
A Staffed Centre With a Named Lead
Engineers, analysts and a centre lead, hired and trained against the operating model.
Documented Processes and Runbooks
How work is planned, released, supported and escalated, written for your team to use.
A Transfer Register
The intellectual property, credentials, contracts and open risks, each with an owner and a transfer date.
How the Transfer Runs
The centre moves through five stages. Your team takes the lead before ownership changes.
Design the Centre
We agree the services, the roles, the reporting lines and the measures with your sponsor. You approve the operating model. End: a signed operating model and a cost plan.
Build the Team
We hire, train and set up the centre, its tools and its processes. Your managers meet the people. End: a staffed centre and a tested release process.
Operate the Centre
XSIS runs the centre against the service catalogue while your team learns the work. You see the monthly service report. End: a stable service and a named understudy for each key role.
Shadow the Work
Your people lead planning, releases and incidents while XSIS supports. You decide when each role is ready to take over. End: a readiness check for every role.
Transfer Ownership
The team, the intellectual property, the runbooks and the vendor contracts move to you. End: a signed transfer record and a support period you define.
What Transfers to You
Build, operate, transfer is judged by what the client owns at the end.
The Intellectual Property
Ownership of the centre's work, its code and its documents passes to you, and the register records each item.
The Operations
The service catalogue, the runbooks, the monitoring and the vendor relationships move to your team.
The Team
Your people run the centre, with the roles, training and decision rights written in the operating model.
The Security Operations
Where the engagement includes a security operations centre, its people, tooling and playbooks transfer with the rest.
What We Need From You
The transfer depends on your decisions about people and ownership.
A Sponsor Who Owns the Outcome
One executive who can approve the operating model, the budget and the transfer date.
Hiring and HR Decisions
Approval for the roles, the employment model and the people who will take over each function.
Access and Supplier Agreements
Access to the systems, and the vendor agreements the centre will inherit at transfer.
Where Build, Operate, Transfer Fails
Three failures are common. Each has a control in the transfer plan.
Knowledge Stays With XSIS
The centre runs, but your team never learns why. Every key role has a named understudy and a written decision log from the first month.
Transfer Comes Too Early
Ownership moves before your team can carry it. A readiness check for each role must pass before the transfer date is set.
Hiring Delays the Plan
The roles you need are not filled in time. We start recruitment at design and name a fallback for each critical role.
What Good Looks Like
You can check these signals before you accept ownership.
Your Team Has Run a Release
Your people planned, tested and released one change while XSIS watched, and the release record is yours.
Every Role Has a Named Owner
Each function in the operating model has a person, a backup and a written handover.
The Transfer Register Is Complete
Every item of intellectual property, access and contract has an owner and a signed transfer date.
The Service Level Holds After Transfer
The first month after transfer meets the agreed targets, and every miss has an action.
Questions and Answers
What is build, operate, transfer?
XSIS designs a capability centre, hires and trains its team, and runs it. We then transfer the team, the operations and the intellectual property to you.
What does the client take over?
The centre's people, its operations, its intellectual property and its supplier agreements. Where the engagement includes a security operations centre, that transfers too.
What does the handover cover?
Training, runbooks, decision logs and a shadow period in which your team leads the work with XSIS support.
How does a capability centre start?
With a conversation about the services, the roles and the transfer date. We then propose the operating model, the team and the governance before you sign.
Tell Us What You Need to Build or Connect.
Describe the systems, the timeline and the constraints. The right engineers take it from there.
What Happens Next
Pre-Consulting Session
A free 30-minute online pre-consulting session: we go through your goals, systems and constraints.
Readiness Review
In a free 48-hour Readiness Review, a Principal Architect checks your project against What we need before we start and recommends the track that fits.
Choosing the Track
Scope-ready projects receive a binding proposal within 3 to 5 business days. Concept-stage projects start with Discovery and Design. A live system that is failing, undocumented or needs integration starts with the Live System Review of 1 to 2 weeks. Discovery and Design and the Live System Review each have a fixed fee, quoted in the proposal.
Delivery in Five Stages
Mobilisation, sprints with live demonstrations, integration and hardening, acceptance and go-live, then managed services. After launch comes a warranty period, then optional support and maintenance.