Operating models / Offshore development center
Plan the operation behind the offshore team.
An offshore development center needs more than engineers in another country. It needs a continuing mandate, accountable leadership, a way to build capability and an operating arrangement that survives changes in people or suppliers. Decide what the center will own, how it connects to the business and how it could be continued or transferred before committing to its footprint.
The working definition
A continuing engineering unit with an operating mandate.
An offshore development center, or ODC, is a durable engineering unit in another country, aligned to a client's continuing product or technology work. Its scope includes how people are led, work is accepted, knowledge is maintained and the operation is supported. The label alone does not determine who employs the team, owns the facilities or directs delivery. Confirm those responsibilities in the proposed arrangement.
- Beyond a project
- An ODC is organized to carry capability and context across successive work. A single outsourced deliverable does not by itself establish that continuing operation.
- Beyond a roster
- A dedicated team can be part of a center. The center question also includes leadership, recruitment and development, operating support, controls and continuity.
- Separate from a legal form
- A provider-supported unit, a client-owned operation and a planned transfer allocate ownership differently. Read the entity, employment and asset arrangements separately from the delivery model.
Three arrangements to investigate
Choose the ownership path deliberately.
These working arrangements illustrate different commitments. They are not exhaustive or standardized packages. Thoughtworks describes an ODC preceding REA's GCC and separately discusses build-operate-transfer; those accounts show possible paths, not a universal progression or a Werkon offering.
Provider-supported center
01Arrangement: A provider supplies agreed local and engineering operating responsibilities for a client-aligned unit.
- Consider when
- The business needs continuing capability and wants to contract for specified parts of the operating layer.
- Confirm
- Employer, leadership, facilities, tools, data access, subcontractors and retained client responsibilities.
- Operating question
- Who handles a leadership vacancy while keeping product decisions and accepted delivery connected?
- Client authority
- The client retains its business mandate, priorities, risk decisions and acceptance authority.
- Inspect
- Named responsibilities, proposed capability, usable delivery records and continuity arrangements.
- Main exposure
- The client depends on a provider relationship without enough understanding or access to continue the work.
- Before proceeding
- Make ongoing oversight and exit obligations as concrete as onboarding.
Client-owned operation
02Arrangement: The client establishes and owns the local operation, with specialist support where required.
- Consider when
- The business has a durable mandate and is prepared to carry local operating obligations.
- Confirm
- Entity and employer arrangements, local leadership, people operations, finance, workplace and technical support.
- Operating question
- Which functions will the client actually run, and which will remain supplied by external parties?
- Client authority
- The client owns the operating decisions as well as product direction, subject to the confirmed local structure.
- Inspect
- Qualified setup advice, named functional owners and a realistic ongoing operating budget.
- Main exposure
- Direct ownership is mistaken for immediate capability or effortless management.
- Before proceeding
- Resolve the local obligations and receiving leadership before treating ownership as readiness.
Build, operate and transfer
03Arrangement: A partner establishes and initially runs agreed capability with a defined later transfer to the client.
- Consider when
- The intended destination is client operation and a proposed partner can support a feasible transition.
- Confirm
- Exactly what can transfer, conditions, timing, charges, permissions and the client's receiving capability.
- Operating question
- What happens if the client is ready to receive the work but a person, asset or agreement cannot transfer?
- Client authority
- Authorized parties approve the transfer; the client accepts the operation it can actually receive.
- Inspect
- An asset and responsibility inventory, qualified review and a tested receiving plan.
- Main exposure
- A transfer label is treated as a guarantee that every person, tool or right moves automatically.
- Before proceeding
- Resolve transfer conditions before relying on the planned destination.
The center charter
Give every part of the operation an owner.
A role is a responsibility to cover, not necessarily a separate full-time hire. Confirm the skill, authority and actual capacity behind each assignment.
| Area | Required decision | Responsible function | Evidence to review | Unresolved gap |
|---|---|---|---|---|
| Mandate | Products, users and work boundaries | Client sponsor and product owner | Roadmap and acceptance criteria | A center with no coherent work |
| Leadership | Technical and delivery authority | Engineering and delivery leads | Decision path and dependencies | Every decision waits for headquarters |
| Capability | Skills, assessment and development | People and technical leaders | Role evidence and onboarding plan | Hiring volume substitutes for capability |
| Delivery | Review, integration and operation | Delivery team and receiving owners | Accepted changes and relevant checks | Local completion never becomes usable work |
| Operating support | Employment, access, tools and suppliers | Local operations and specialist owners | Confirmed obligations and access records | Responsibility assumed from the label |
| Economics and exit | Full costs and continuation options | Finance, commercial and service owners | Cost assumptions and receiving plan | Low rates with an uncosted transition |
From mandate to accepted work
Establish the smallest operation that can prove the model.
Illustrative first assignment: maintain and extend a bounded internal application. Before expanding the unit, ask it to carry one agreed change through clarification, implementation, review and operating handover. This is a useful check on the arrangement, not proof of all future capacity or a prescribed pilot size.
- 01
Define the continuing mandate
Describe the work, its expected continuity and its interfaces with the rest of the business. Compare an ODC with a smaller team or a bounded project if the need does not support an operating unit.
- 02
Validate the arrangement and location
Assess proposed capability, working-hour coordination, infrastructure and operating conditions. Have qualified advisers resolve legal, employment, tax, data and ownership questions for the actual parties and location.
- 03
Assign leaders and prepare the operation
Confirm product, technical, delivery and people responsibilities. Establish relevant hiring assessment, onboarding, tools, permitted access, records and escalation before depending on the unit.
- 04
Accept a complete piece of work
Inspect the first assignment across the center boundary. Check the result, review evidence and the receiving team's ability to support it. Repair missing responsibilities and knowledge.
- 05
Review before expanding
Use observed workload, accepted delivery, leadership capacity and full operating cost to assess the next commitment. Keep continuity and exit records current as the center changes.
Economics and resilience
Count the work required to keep the center useful.
A lower quoted rate is not a complete business case. Compare the same mandate and quality requirements across setup, operation and transition, using current proposals and explicit assumptions.
- Build a complete cost view
- Include setup, recruitment, equipment, leadership, learning, coordination, retained client effort and exit. Separate one-time and recurring items, show currency assumptions and keep uncertain costs visible.
- Control the actual supplier boundary
- Agree proportionate protection, permitted subcontracting and incident responsibilities. Limit, monitor and review access for the actual people and systems involved; a facility or policy alone is not evidence of control.
- Keep knowledge usable
- Maintain clear, findable and current decisions and operating records. Ask another authorized participant to use them. Plan for leadership changes and concentrated knowledge as well as individual departures.
- Join exit to the receiving operation
- Inventory work, assets, rights, data, access and dependencies. Connect the outgoing responsibilities to an incoming team with the capability to receive them. Confirm transfer conditions and the cost of overlap.
Questions before establishment
The center should fit the mandate you can sustain.
The arrangement needs enough definition to assess, while leaving unconfirmed capability and commercial facts explicit.
- Does an ODC require a fixed number of people?
- This guide sets no minimum. The relevant question is whether the continuing work justifies the leadership and operating responsibilities. Define capability and workload before using headcount as a target.
- Is an ODC the same as a GCC?
- The terms can overlap in supplier usage. A global capability center can support functions beyond software engineering, while this ODC definition focuses on a continuing engineering operation. Confirm the actual mandate and ownership rather than relying on the acronym.
- Does the client need to own a local entity?
- That depends on the arrangement. A provider-supported center and a client-owned operation allocate local obligations differently. Qualified advisers must determine the structure required for the actual engagement.
- Does offshore automatically mean lower total cost?
- No. Compare current proposals against the same work and include setup, local operation, client participation and transition. Rate differences do not establish equivalent capability, accepted output or whole-life savings.
- Does Werkon already have a center available?
- This page explains the model; it does not claim an available Werkon center, office, local employer or roster. Location, operating structure, proposed capability and commercial terms would need to be confirmed for an engagement.
Source basis
Model context and operating guidance.
- 01
Thoughtworks
REA Group's journey with ThoughtworksProvider-authored account reviewed. Describes an ODC preceding a GCC and continuing transition support. Used as model context, not independent outcome evidence or a Werkon case study.
- 02
Thoughtworks Perspectives
Global capability centersJuly 2025 article reviewed for purpose, leadership, operating setup and build-operate-transfer discussion. Market forecasts, talent figures and client performance claims are not adopted.
- 03
GOV.UK
The Sourcing PlaybookSelected delivery-model, whole-life cost, mobilization and transition sections reviewed. Public procurement, legal requirements and prescribed approval structures are not generalized.
- 04
GOV.UK Service Manual
What each role does in a service teamNovember 2023 role guidance reviewed for product, technical, delivery and service responsibilities. It does not define a mandatory ODC roster.
- 05
NCSC
Supply chain security: establish controlGuidance reviewed October 2025; main controls inspected. Supports proportionate requirements, supplier access, subcontracting, incidents and termination. Government-specific requirements are not imposed.
- 06
DORA
Documentation qualityCurrent guidance based on 2021 and 2022 research reviewed for clarity, findability, reliability and maintenance. No uplift is used as an ODC performance prediction.
Start with one real workflow
A Systems Audit is the usual starting point. If the opportunity is already clear, we can move directly into a focused build.
Show Us the WorkflowStart with the free automation readiness checklistOBSERVEQUANTIFYDECIDEBUILD