Skip to main content

Dev Station Technology

Build, operate, transfer

A Vietnam team you will own, on a date agreed at the start

We hire and run the team while you have no entity here, then hand the whole thing to your own Vietnamese company. The model turns on one clause: whether the transfer price and the trigger are written into the first contract or negotiated on the day you want to leave.

Book a 30-minute scoping call Read where BOT goes wrong

Most companies asking about BOT should run a dedicated team for a year first. We will say so on the first call.

Transfer terms, settled at signature rather than at exit.
Transfer price A formula in the first contractAgreed
Trigger Your notice, or a headcount, or a dateAgreed
Staff terms Seniority and salary carried acrossPreserved
Per-engineer handover fee Not in the contract, not payableNone
Support after the date Length and cost fixed up frontIncluded
Every row here is something a vendor could otherwise charge you for at the end.

What we bring to a build, operate and transfer engagement

  • Ho Chi Minh City10+ years working with US, UK and EU teams
  • Dedicated teamsRecruitment, HR, payroll and equipment already run in house
  • German software firmTeam grown to 60+ engineers at peak
  • No completed transfer yetWe say so rather than imply otherwise

The honest question first

BOT is the wrong answer more often than it is the right one

It is a two to three year commitment with a legal project attached. Plenty of companies ask for it when a dedicated team would give them the same engineers and none of the paperwork.

Do not commit to BOT when

The entity is not actually the goal

  • You want the team, and owning a Vietnamese company is incidental
  • The team will stay under about fifteen people
  • You have never run an engineering team outside your own country
  • Nobody has checked the tax and legal case with an adviser yet
  • The budget holder changes every year

Run a dedicated team instead. You can convert later, and the people carry across.

BOT earns its keep when

You have already decided to be here

  • A Vietnamese entity is on your plan regardless of who builds the team
  • Headcount will pass twenty and keep going
  • You want engineers hired and working before the entity exists
  • Your board wants a known exit price rather than an open negotiation
  • The work is core enough that you will not outsource it forever

This is the case BOT was designed for, and it is worth the contract work it takes.

Plain definitions

Two questions that come before any of the numbers

Both get answered with acronyms in most proposals. Both decide whether the engagement is worth starting.

What is build, operate, transfer?

A supplier hires and runs an offshore team under their own company, with a written intention from the first day that the team will become yours. Three phases. Build the team, operate it while you direct the work, then transfer the people and the operation into an entity you own.

The word that matters is intention. Ordinary outsourcing has no end state; BOT is a purchase paid for in instalments, and the last instalment is the one people forget to price.

BOT, a captive centre, or a dedicated team?

A captive centre is what you build yourself. You register the company, take the office, hire everybody and carry the risk from day one. It is the cheapest per head eventually and the slowest to start, and the first hire typically lands the better part of a year after the decision.

A dedicated team is the opposite. We employ everyone, you direct the work, and nothing transfers. BOT sits between the two on purpose: our risk at the start, your ownership at the end, with the swap priced before either side has an incentive to argue about it.

The three phases

What each phase actually consists of

Written as the work rather than as a diagram. The durations below are what we would commit to; your legal timeline is set by your advisers and runs alongside.

  1. Month 1 to 4

    Build

    Roles and salary bands agreed against your standards, job specs written, hiring run by us. You interview every candidate and you can reject all of them. Desks, laptops, network access and security policy go in alongside. A core team is working by the end of this phase.

  2. Month 5 to 24

    Operate

    We carry payroll, HR, contracts, appraisals, equipment, the office, and the leavers and replacements nobody plans for. Your engineering manager runs the work itself. Reporting covers headcount, attrition, cost and delivery on whatever cadence you set.

  3. Runs in parallel

    Your entity, on your side

    Registering a foreign-owned company in Vietnam is a legal project with its own timeline, and it belongs with a Vietnamese law firm rather than with us. Start it during Operate rather than at the end, because an entity that is not ready is the most common reason a transfer date slips.

  4. On the agreed date

    Transfer

    Staff move to your entity on their existing seniority and salary. The price and the trigger were fixed at signature, so this phase is administration rather than negotiation. We stay on for an agreed handover period at an agreed cost, so nothing stops on the day.

Tell us what you want to end up owning

Three fields. An engineer reads it, not a sales rep. You get an answer within one working day.

  • We map the roles, the timeline and what the transfer would involve
  • You get a written view, including the view that BOT is wrong for you
  • No obligation, and no phone number needed to start

The agreement

Six clauses that decide whether BOT works out

If a supplier proposal is missing three of these, the transfer is not really priced. Ask for them before you compare rates.

The transfer price, as a formula
Not a number to be agreed nearer the time. A formula tied to something both sides can count, such as headcount at the transfer date, so neither of us can move it later.
The trigger
What starts the transfer and who can start it. Your notice, a headcount threshold, a fixed date, or any combination. Without this the supplier decides when you are allowed to leave.
Staff terms on the day
People move on their existing seniority and salary, and they are told the plan early enough to believe it. Anyone surprised by a transfer starts looking for another job.
Code and IP throughout
Yours from the first commit, in every phase, rather than transferring with the team. If ownership of the work depends on completing the transfer, you have a hostage rather than a contract.
Support after the date
A defined handover period with a defined cost. The first payroll run, the first appraisal cycle and the first resignation under your entity all benefit from somebody who has done them here before.
What happens if you never transfer
Plans change. The agreement should say what the engagement becomes if you decide against an entity, and it should be a dedicated team on ordinary terms rather than a penalty.

Where it goes wrong

Five failures we would rather you saw coming

None of these are unusual. All of them are cheaper to plan for than to discover in year two.

Candidates decline because nobody has heard of you
Hiring for a foreign brand with no local presence is harder than hiring for ourselves, and it shows in the offer acceptance rate. We deal with it by being explicit in the job spec about who the eventual employer will be, which shortens the list and improves who stays.
People leave at the transfer
A change of employer is a moment when everybody reconsiders. Attrition around the date is the single largest risk in the model. Telling the team early, carrying seniority across and keeping the manager the same are what reduce it, and no supplier can promise it away.
Fees appear at the end
Per-engineer handover charges, transfer administration, an exit fee nobody discussed. This is why the price belongs in the first contract as a formula. Ask any supplier to write it down before you sign, and watch what happens.
The entity is not ready and the date slips
Company registration in Vietnam runs on its own timeline with its own approvals. It is the part outside everybody control, and it is why we push clients to start the legal work during Operate rather than in the final quarter.
The transfer never happens
The most common outcome across the industry, and not always a failure. Sometimes a dedicated team turns out to be what the company wanted. It is only a failure if you paid a premium for an option you were never going to use, which is a decision to make honestly at the start.

Who does the work

Twenty engineers, eight of them senior

Small for a model this size, and we would rather say so. It means we can build you a team of twenty well and we would decline a brief for a hundred.

Engineers in Ho Chi Minh City
20
Senior engineers
8
Average experience
5+ yrs
Working with US, UK and EU teams
10+ yrs

We have run recruitment, payroll, HR and equipment for client teams for years, and we have grown one engagement to more than sixty people at peak. We have not yet completed a transfer into a client entity, and you should weigh that.

How we work

Five engagement models, and you pick how much you keep

The models differ in one thing: how much of the management you hand over. Everything else, including who owns the code, is the same in all five.

Changing model later is normal. Augmentation into a dedicated team is the common direction, and the people stay.

Engineers join your team and work inside your process, your board and your code review.

Team control
You manage the day to day
Pricing
Monthly per person, by role and seniority
Minimum
1 month

A team that works only on your product, with a lead on our side running delivery.

Team control
Shared. Our lead runs delivery, you set priorities
Pricing
Monthly per role, lead included
Minimum
3 months

A long-term engineering site under your standards, where we carry recruitment, HR, payroll and equipment.

Team control
You direct the work, we run operations
Pricing
Monthly per role plus site costs
Minimum
6 months

One price for a scope that is genuinely settled, with the overrun carried by us.

Team control
We deliver, you accept against written criteria
Pricing
Fixed bid, paid against milestones
Minimum
Project based, usually 10 to 14 weeks

05

You are hereBuild, Operate, Transfer (BOT Model)

Everything in the centre model, with the whole team moving into your own Vietnamese entity on an agreed date.

Team control
Transfers from us to you
Pricing
Monthly per role, transfer price agreed up front
Minimum
2 to 6 years

FAQs

Questions we get on the first call

Have you completed a BOT transfer before?

No. We run dedicated teams and an offshore development centre, we handle recruitment, payroll, HR and equipment, and we have grown one client engagement past sixty people at peak. The transfer step itself we have not yet done for a client, and we would rather tell you that than let a page imply otherwise. If a completed transfer is a requirement for your board, ask us early and we will say so on the first call.

How long does BOT take from start to finish?

Two to three years is the normal shape. A core team working inside four months, a year or two of operating while your entity is registered and the team settles, then a transfer measured in weeks once the date arrives. Anything promising a transfer inside a year is either a very small team or a plan that has not met a registration queue yet.

What does the transfer itself cost?

It should be a formula in your first contract rather than a number quoted later. We write it against something countable, usually headcount at the transfer date, so neither side can move it. What it should not be is a per-engineer fee introduced at the end, and any supplier unwilling to put the formula in writing at signature is telling you something.

What kind of entity do we need in Vietnam?

A foreign-owned company here normally needs an investment registration and then an enterprise registration, and which form suits you depends on your ownership, your activity and your tax position. That work belongs with a Vietnamese law firm and their advice governs, not ours. What we can tell you is how long it has taken clients in practice and why starting it early matters.

Do the staff have to agree to move?

Yes, and treating that as a formality is how transfers lose people. Employment moves to your entity on their existing seniority and salary, and the team is told the plan long before the date rather than in the month of it. We would rather lose somebody early, when there is time to replace them, than on the day.

Can we stop before transferring?

Yes, and the agreement should say what happens when you do. In our version it becomes an ordinary dedicated team on ordinary terms with no penalty, because a company that changed its mind about an entity is not a company that broke a contract.

How is this different from an offshore development centre?

The centre model is the same operation with no transfer written into it. Same recruitment, same payroll and HR, same reporting, and the team stays with us. BOT is the centre model plus a priced exit. If you are unsure which you want, start with the centre and add the transfer terms later, which costs nothing beyond a new agreement. Our offshore development centre page covers the operating half in detail.

What is the smallest team worth doing this with?

Below about fifteen people the entity overhead rarely repays itself, and a dedicated team gives you the same engineers without the legal project. We usually suggest starting a team of five or six under a dedicated arrangement, running it for a year, then deciding about an entity with real information instead of a forecast.

Who owns the code while all this is happening?

Your company, from the first commit, in every phase. Ownership of the work does not wait for the transfer and is not part of what gets transferred. Repositories, pipelines and documentation are yours throughout.

Tell us what you want to own, and when

Bring the headcount you are aiming at and the year you want the entity running. Thirty minutes is enough to tell you whether BOT is worth the contract work, or whether a dedicated team gets you the same thing for less.

Book a 30-minute scoping call Read where BOT goes wrong

Let's Talk