China plus one is a diversification strategy where organizations with operations or delivery capability in China add a second offshore location to reduce reliance on a single market. In software development, this means assessing whether engineering capability, delivery knowledge, IP governance, and product ownership should sit across more than one location.
For Australian organizations using China-based software delivery, this approach helps evaluate how offshore engineering capacity should be distributed as business needs evolve. Vietnam is one practical option for the second location, with time zone proximity for real-time collaboration, a growing engineering workforce, and ownership models such as Build-Operate-Transfer.
How China+1 changes when the asset is software
Software delivery follows the same risk logic as hardware, but the operating implications are different. A hardware supply chain moves materials and finished goods. A software delivery model builds knowledge, architecture history, engineering practices, product context, and IP over time.
| China+1 in hardware | China+1 in software delivery |
| Adds a second manufacturing base | Adds a second offshore engineering capability |
| Reduces production and supplier dependency | Reduces vendor, country, and delivery dependency |
| Protects physical output and supply continuity | Protects engineering capacity and product continuity |
| Manages factories, suppliers, logistics, and inventory | Manages teams, governance, IP, architecture, and delivery knowledge |
| Measures transferability through production readiness | Measures transferability through knowledge ownership and operating maturity |
China plus one in software development is a capability design decision, where the second location needs to reduce risk while also protecting the knowledge and delivery assets created through software work. A Build-Operate-Transfer model goes further than a standard vendor arrangement by creating a path to own the offshore development center, the team, the governance structure, and the IP framework over time.
The three practical drivers behind China plus one in software development
Australian organizations are asking both where software should be delivered from and how much dependency they are comfortable carrying in their offshore engineering model.
1. Concentration risk
When too much engineering capacity sits in one country, one vendor, or one operating model, the organization carries a single point of failure. A second offshore location gives leaders more optionality, allowing the business to keep existing China-based arrangements where they still make sense while building capacity for future growth, modernization programs, and platform engineering needs.
2. Cost structure
China’s senior software development rates have increased over the past decade, narrowing the cost advantage that originally justified many offshore arrangements. Vietnam offers a more competitive cost base while continuing to expand its engineering workforce, making it a strong candidate for new software capacity without deepening dependency on a single delivery location.
3. IP governance and AI-era ownership
Ownership is no longer limited to source code. Delivery assets now include AI-assisted workflows, reusable prompts, generated components, automation configurations, test scripts, and product decision history. If these sit inside a vendor-owned framework, ownership becomes difficult to prove and harder to transfer. This is where China plus one in software development planning should connect directly to Build-Operate-Transfer: if the motivation includes IP governance and long-term control, the second location should be structured for eventual transfer to the client.
Why Vietnam is the logical second location
The full case for Vietnam as an offshore delivery market belongs on the CBTW Offshore Development Center for Australian Businesses page. This article has a narrower role: to explain why Vietnam makes sense as the second location in a China+1 software delivery strategy.
Vietnam combines proximity, cost competitiveness, engineering talent, and a stronger bilateral relationship with Australia. It sits one to three hours behind Australia’s east coast, supporting real-time collaboration across sprint planning, architecture reviews, and incident response. According to Vietnam’s National Innovation Center, the country has over 500,000 IT engineers, with universities producing 50,000 to 60,000 new tech graduates annually. Australia and Vietnam also elevated their bilateral relationship to a Comprehensive Strategic Partnership on 7 March 2024, strengthening the long-term context for organizations considering Vietnam as a strategic engineering location.
Three ways Australian organizations can apply China+1
| Model | Best fit | What it solves |
| Parallel capability | Organizations that want redundancy without disrupting current China-based delivery | Reduces delivery concentration risk |
| Capability migration | Organizations shifting new investment into Vietnam over time | Improves cost structure and future flexibility |
| Build-Operate-Transfer | Organizations that want a Vietnam-based capability they can eventually own | Addresses IP governance, ownership, and vendor dependency |
Parallel capability: A second engineering team in Vietnam takes on a separate product stream or platform while the existing China-based arrangement continues. The objective is controlled diversification, with enough separation to reduce risk and enough integration to maintain consistent delivery governance.
Capability migration: New engineering investment is directed into Vietnam while China-based arrangements reduce naturally over time. This is often more realistic than abrupt transition and is particularly relevant when the next wave of work involves new platforms, AI-enabled delivery practices, or modernization programs.
Owned capability through Build-Operate-Transfer: Under BOT, a Vietnam-based offshore development center is built and operated first, then transferred to the client at the agreed maturity point. The offshore development center provides the delivery structure; BOT provides the ownership path. For organizations applying China plus one in software development because of IP governance and vendor dependency concerns, BOT is the most structurally aligned model.
The ownership dimension the hardware analogy misses
In hardware, the output is physical product. In software, the output is cumulative capability: the engineers who understand the product, the architecture decisions behind the platform, the operational knowledge, the AI-assisted workflows, and the delivery routines that keep software moving.
In a vendor-managed model, much of that knowledge remains tied to the vendor. Even when the client owns the source code, the capability to maintain, extend, and govern the system may not transfer cleanly when the contract ends.
This is why BOT matters in the China plus one in software development discussion. It turns the second location from a sourcing alternative into an ownership pathway, using a Vietnam-based offshore development center as the structure for building, operating, and eventually transferring the capability to the client. For a deeper explanation of the delivery structure, see What is an Offshore Development Center. For broader delivery model options, see Offshore Development Services for Australian Businesses.
What Australian technology leaders should decide first
Before moving forward, technology leaders should align on three questions:
- Is the goal resilience, cost optimization, or ownership? Each goal points to a different operating model, and confusion here usually creates weak governance later.
- Which assets need to be owned or transferred? Source code is only part of the picture, because AI workflows, automation assets, documentation, and product knowledge also matter.
- How will the second location integrate with the internal technology organization? Offshore delivery works best when integrated with clear governance and delivery cadence from the start.
Frequently asked questions
Does China+1 mean shutting down China-based software teams?
China+1 means adding a second location while keeping the existing location where it still provides value. The practical path is to direct new investment into Vietnam while existing China-based arrangements continue or wind down naturally.
How does BOT fit into a China+1 software delivery strategy?
BOT fits when the organization wants the second location to become a capability it can eventually own, with the team, governance structure, IP framework, and entity setup built for transfer. This is especially relevant when the China+1 motivation includes IP governance, AI-era delivery assets, and long-term control.
Is China plus one in software development the same as IT outsourcing diversification?
IT outsourcing diversification spreads work across multiple vendors to reduce commercial dependency. China plus one in software development is specifically about adding a second geographic delivery location to reduce country concentration risk and build a better long-term operating model.
When should an organization consider BOT over a vendor-managed offshore team?
BOT becomes the stronger option when offshore delivery is strategic and the organization wants critical capability within its own operating structure over time, with stronger IP governance and knowledge retention than a vendor-managed arrangement provides.
Next steps
For an introduction to how offshore development centers work and how the model matures toward BOT, see What is an Offshore Development Center. For the full ownership model, see the Build-Operate-Transfer service page. For a broader framework on choosing the right offshore software delivery model, read the Offshore Software Development Guide.
