The labels in this category describe a small number of genuinely different arrangements, and the thing that distinguishes them is not remoteness but who carries delivery risk and who ends up owning the knowledge. Reading a proposal for that, rather than for the label, tells you what you are actually buying.
Extended development team: your risk, their people
An extended team is people who work as part of your team under your direction, participating in your standups and your process. You keep delivery risk, you keep architectural control, and you gain capacity. It works when you already have functioning engineering leadership and fails when you do not, because you are adding people to a system that cannot absorb them. Make continuity contractual: named individuals, notice before replacement, vendor funded handover.
On demand software development: flexibility priced as a premium
On demand arrangements promise people quickly and release them easily, which is genuinely useful for bounded surges and expensive as a steady state, because you pay a premium for flexibility and repay onboarding on every rotation. It also tends to produce shallow domain knowledge. Use it for spikes with a defined end, not as the default way of staffing continuing work.
The build-operate-transfer model is designed to end
In this model a vendor recruits and runs a team for you, then transfers the entity and the employees to you at an agreed point. It suits a company that genuinely wants its own team in another location but lacks the local presence to start one. The thing to scrutinise is the transfer: what triggers it, what it costs, whether the individuals are contractually willing to transfer, and what happens if they decline. A transfer clause nobody has priced is not a plan.
What extended teams and every remote arrangement need in writing
Who legally employs the people, since directing daily work makes classification live and the IRS assesses substance over labels. An express written copyright assignment, since commissioned software is not automatically a work made for hire under 17 USC 101. Which jurisdictions data may be stored and accessed from. And whether releasing source code abroad engages export control, which under 15 CFR 734.13 treats a release to a foreign person as an export.
Questions people ask about remote development team
What is the difference between an extended team and outsourcing a project?
An extended team works under your direction and leaves delivery risk with you, in exchange for capacity and control. Project outsourcing transfers the risk and gives you people who leave when it ends, taking what they learned.
Is an on demand developer worth it?
For bounded surges with a defined end, yes. As a steady state it is expensive: you pay a premium for flexibility, repay onboarding on every rotation, and accumulate little domain knowledge.
What should we scrutinise in a build-operate-transfer deal?
The transfer: what triggers it, what it costs, whether the individuals are contractually willing to transfer, and what happens if they decline. An unpriced transfer clause is not a plan.