Business

Staff Augmentation, Project or Build-Operate-Transfer: Choosing How to Engage a Software Partner

November 11, 2026 · 8 min read · Etzal Group Team

A company in Singapore wants a customer portal built. One provider offers three developers at a monthly rate. Another offers to deliver the portal for a fixed price. A third proposes to set up a team of eight in Jakarta that will become the client's own in two years. The proposals are not three prices for the same thing. They are three different divisions of work and risk: staff augmentation, project delivery and build-operate-transfer. Choosing among them comes before choosing a provider.

The three models in one sentence each

  • Staff augmentation. You rent people. You manage them.
  • Project delivery. You buy a result. The vendor manages how.
  • Build-operate-transfer, BOT. A partner builds and runs a team for you, then hands it over.

Staff augmentation

External engineers join your team. They attend your meetings, use your repository and tools, and take work from your product owner or technical lead.

You are responsible for:

  • Deciding what is built and in what order.
  • Day-to-day management and code review.
  • Architecture and quality.
  • The outcome.

The provider is responsible for:

  • Finding and employing suitable people.
  • Payroll, benefits, equipment and replacement if someone leaves.

It fits when:

  • You already have technical leadership and a working process.
  • You need more hands, or a skill you lack, for a period.
  • Requirements are evolving and you want to steer daily.

It fails when:

  • Nobody on your side can direct engineers. Three developers with no lead produce activity, not a product.
  • You expect the provider to take responsibility for delivery. They have sold you time.

Cost shape: a monthly rate per person. Predictable per month. Total cost depends on how long you keep them and how well you use them.

Project delivery

You describe what you need. The vendor proposes a solution, a plan and a price, and delivers it with their own team under their own management.

You are responsible for:

  • Clear requirements and timely decisions.
  • Access to users, data and systems.
  • Reviewing and accepting what is delivered.

The vendor is responsible for:

  • The team, the method and the management.
  • Architecture, quality and testing.
  • Delivering the agreed scope.

It fits when:

  • You have no internal development team, or it is busy.
  • The outcome can be defined well enough to scope.
  • You want one party accountable for the result.

It fails when:

  • Requirements are vague and expected to change constantly under a fixed price. Every change becomes a negotiation.
  • The client is unavailable. Vendors cannot deliver without decisions.

Cost shape: fixed price for a defined scope, or time and materials with a budget. Higher cost per unit of work than augmentation, because management and delivery risk are included.

Build-operate-transfer

A partner sets up a dedicated team for you: recruiting, employing, housing, equipping and managing operations. The team works only for you. After an agreed period, typically one to three years, the team transfers to your own legal entity.

Three phases:

  1. Build. The partner recruits to your profile, sets up the workspace, and establishes process with you.
  2. Operate. The team works on your roadmap. The partner handles employment, administration and local management. You direct the work, often with a local lead.
  3. Transfer. Employees, assets and knowledge move to your entity, on terms agreed at the start.

It fits when:

  • You want a permanent team in another country.
  • You do not yet have a legal entity, an employer brand or recruiting capacity there.
  • You have enough ongoing work to occupy a team for years.

It fails when:

  • The need is short term. BOT is a long commitment.
  • Transfer terms are left vague. The end of the arrangement is where disputes concentrate.
  • You do not invest in the team as your own during the operate phase. People who feel like contractors do not transfer happily.

Cost shape: setup fees, then monthly cost per person plus the partner's margin, then a transfer fee. More than augmentation in the early period, and less than building a foreign entity alone on day one.

Side by side

Staff augmentationProject deliveryBuild-operate-transfer
What you buyPeople's timeA defined resultA team that becomes yours
Who manages daily workYouVendorYou, with the partner's local support
Who carries delivery riskYouVendor, within scopeYou
Who employs the peopleProviderVendorPartner, then you
Flexibility of scopeHighLower, through change requestsHigh
Typical durationMonthsMonthsYears
Needs your technical leadershipYesLessYes
Knowledge stays withPartly youVendor, unless handed overYou
Speed to startFastMedium, after scopingSlow, months to recruit

How to choose

Five questions decide most cases.

1. Do you have someone who can lead engineers? No: project delivery. Staff augmentation and BOT both assume your direction.

2. Can the outcome be defined? Yes: project delivery is possible. No, and it will keep changing: augmentation, or a project run on time and materials in short phases.

3. Is the need temporary or permanent? A peak or a single product: augmentation or project. Continuous development for years: consider BOT, or augmentation with a long horizon.

4. Who should hold the knowledge? If the system is central to your business, you want understanding to stay with you. That favours augmentation into your team or BOT, or a project with a deliberate handover.

5. How much risk do you want to carry? If you want someone else accountable for delivery, pay for project delivery. If you want control and accept the responsibility that comes with it, augment.

Hybrids that work

Real engagements often combine models.

  • Discovery as a project, build with augmentation. A vendor runs a fixed-price discovery, then supplies engineers who work under your lead.
  • Project first, then a retained team. The vendor delivers the first release, and part of the team stays on a monthly basis for further development.
  • Managed team. Augmentation with a lead supplied by the provider who takes responsibility for the team's output. Useful when you have a product owner and no technical lead.
  • Project delivery with handover to an in-house team that was hired during the project and paired with the vendor's engineers.

Contract points by model

Staff augmentation:

  • Named individuals, with your right to interview and to request replacement.
  • Notice period for scaling down.
  • Replacement time if someone leaves.
  • Intellectual property in the work belongs to you.
  • Confidentiality and security obligations binding the individuals.
  • Whether you may hire the people directly, and at what fee.

Project delivery:

  • Scope, acceptance criteria and milestones.
  • Payment tied to accepted deliverables.
  • Change request process and rates.
  • Warranty, support and ownership of code.
  • Handover obligations.

Build-operate-transfer:

  • Recruitment profile, your approval of hires and time to fill.
  • Cost breakdown: salaries, overhead, partner margin.
  • Transfer terms, fixed at signing: when, what transfers, at what fee, and what happens if you transfer early or not at all.
  • Employee terms on transfer: continuity of service, benefits.
  • Local employment law and tax advice in both countries. This area is specialised, and the rules differ by country.

Mistakes by model

Augmentation:

  • Hiring augmented staff without a lead.
  • Treating them as outsiders, with no access to context.
  • No plan for knowledge retention when they leave.

Project:

  • Fixed price on a vague scope.
  • An absent client.
  • No handover, so the vendor is needed forever.

BOT:

  • Vague transfer terms.
  • Underestimating the time to recruit.
  • No senior person on your side building the relationship with the team.

Working across Indonesia and Singapore

For companies in Singapore engaging teams in Indonesia, a few practical points:

  • Time zones are close. Jakarta is one hour behind Singapore, so working days overlap almost fully.
  • Language. Technical work is commonly done in English. Check the working level of the actual team, not just the account manager.
  • Data. If personal data moves between the countries, both Singapore's PDPA and Indonesia's personal data protection law are relevant. Settle the terms early.
  • Visit. A few days on site at the start does more for a working relationship than months of calls.

We work with clients in all three ways, and we will say so when we think the model a client has asked for does not suit their situation. See our approach in Enterprise Software, or contact us to talk through which model fits.

Summary

Decide the engagement model before the vendor. Staff augmentation rents people whom you manage and suits teams with technical leadership. Project delivery buys a defined result with the vendor accountable and suits clear scopes and clients without a team. Build-operate-transfer creates a permanent team abroad and needs years of work and precise transfer terms. Choose by who can lead, how well the outcome can be defined, how long the need lasts, who should hold the knowledge and how much risk you want.

Frequently asked questions

What is staff augmentation in software development?

It is adding external engineers to your own team for a period. You direct their daily work, they follow your process and tools, and you pay for their time. The provider supplies and employs the people. You keep control of what is built and carry the responsibility for the result.

What is the build-operate-transfer model?

A partner sets up and runs a dedicated team for you, often in another country, including hiring, office and administration. After an agreed period, the team and its operations are transferred to your own entity. It suits companies that want a permanent team abroad without setting up a legal entity and recruiting from scratch on day one.

Which engagement model is cheapest?

The rate per person is usually lowest for staff augmentation and build-operate-transfer, and highest per unit of work for project delivery, because the vendor is pricing in delivery risk and management. The cheapest overall depends on whether you can manage the work well yourself. Low rates with weak direction produce expensive results.

Author

Etzal Group Team

Etzal Group Team, helping businesses grow with technology. Contact us.

Related service

Free consultation

Not sure where to start? We will map the right system for your business, free.