staff augmentation or dedicated team: which format to choose
The difference between the formats is not in the rate, but in who is responsible for the result and who manages the people. We analyze three models instead of two, the legal framework of Chapter 53.1 of the Labor Code of the Russian Federation, the hidden costs of both options and the choice matrix.
The right question is not “which is cheaper”
Comparing formats almost always starts with the rate. This is the most useless entry into the problem: the stakes are comparable, but the results are not. The difference between staff augmentation and a dedicated team lies elsewhere: who is responsible for the results and who manages people. Everything else - cost, timing, risks, composition of documents - are consequences of this choice.
A practical sign: if you have an architect, a team lead and a clear backlog, but don’t have enough hands, you need hands, and this is staff augmentation. If you need a working product, but there is neither an owner of technical solutions nor a delivery process inside, buying hands will not solve the problem: there will be no one to manage people, and in six months you will receive code that no one can maintain.
Three formats, not two
Outsourcing is usually left out of the comparison, and this creates a false dilemma.
| Outsourcing | staff augmentation | Dedicated team | |
|---|---|---|---|
| What to buy | Service result | Specialist time | Delivery of results by the team |
| Who sets the tasks | The performer himself | Customer | The customer sets a goal, the lead performer sets tasks |
| Responsibility for quality | Executor | Customer | Contractor within the agreed scope |
| PrEA accreditation required | No | Yes | No, if control is on the executor's side |
| Composition flexibility | Low | High | Average |
| Where does the expertise live after the project? | From the performer | At the customer's | Divided if transfer is provided |
| When appropriate | The task is separable and measurable by the result | There are controls, but not enough hands | We need results, there is no internal management |
Here we examine what lies behind the rows of this table. A brief tabular comparison of the two latest formats is available on a separate page. "staff augmentation vs managed team".
Legal framework: why it is not a matter of taste
staff augmentation in Russia is a regulated activity, and this is the main difference from the everyday idea of “just hiring people through a contractor.”
- Agency labor is prohibited Article 56.1 of the Labor Code of the Russian Federation since 2016. The legal form is the provision of labor to workers (personnel) under Chapter 53.1 of the Labor Code of the Russian Federation.
- Only accredited private employment agencies have the right to provide personnel. Accreditation is issued by Rostrud; the record is public and verified against the registry. Working with an unaccredited supplier is a risk for the customer, not just the contractor.
- Chapter 53.1 limitations relate to the deadline for referral to one customer, payment terms and cases when referral is generally unacceptable. You should know them before signing the contract, and not after checking.
- Risk of retraining. If a “service” is purchased under a contract, but in fact the customer manages people, keeps track of their working hours and distributes tasks, the relationship can be reclassified with all the consequences for personal income tax and contributions.
RESTART is included in the register of accredited PrEA - details and details of entry in the news about accreditation, the document is available at Trust package.
Economics: why “cheaper” is deceptive
Comparing a contractor's rate to an employee's salary is a common mistake. A correct comparison includes what is not included in the salary.
- Selection Finding an engineer takes weeks and costs money regardless of the outcome. With staff augmentation, this risk and this cost are on the supplier’s side.
- Simple. A full-time employee is paid even when there are no tasks. The external composition changes under load.
- Replacement. The departure of a full-time specialist means again recruitment plus months of input. In a contract with a supplier, replacement is his responsibility and his deadline.
- Putting it into context. Exists in both cases and is almost always underestimated: the engineer reaches normal productivity in four weeks, and not on the first day.
- Contributions and benefits. The status of the supplier is important here: accredited IT companies have a lower premium rate than the standard, and this is reflected in the price. Calculation based on specific numbers - in analysis about the EoR model and the HQS threshold.
- Cost of exit. What will remain with you when the contractor leaves: documentation, access, knowledge of the system. If nothing, you will have to spend the savings twice.
Control: Where Both Formats Break Down
staff augmentation is breaking down, when the customer does not have a management resource. External engineers come, wait for tasks, receive them with a delay and in general form - and productivity drops by half when paid in full. The format requires a team lead, a clear backlog and a code review from the customer. This is not bureaucracy, this is a condition for efficiency.
Dedicated command breaks, when the customer buys the “result”, but does not provide access to subject area expertise. The team cannot guess the business rules; in the absence of the owner on the customer’s side, she will make decisions herself, and they will be wrong.
What is needed in both cases:
- a single task tracker - common, not “ours and theirs”;
- determination of task readiness, agreed upon before the start;
- review of code and architectural solutions with the participation of both parties;
- reporting rhythm tied to the result, not the clock;
- named person responsible on each side.
Risks and how to cover them
| Risk | How it manifests itself | What to do |
|---|---|---|
| Requalification of the contract | Claims for personal income tax and contributions, additional charges | Work with an accredited PrEA, comply with the framework of Chapter 53.1 of the Labor Code of the Russian Federation |
| Loss of knowledge | After the team leaves, there is no one to maintain the system | Documentation as part of acceptance, pair work with full-time engineers |
| Vendor dependency | Changing a contractor costs the same as a new project | Code and infrastructure in your repositories, standard stack, no “proprietary” solutions |
| Contractor access to data | External accounts with broad rights and no expiration date | Time-limited access, separation of environments, privilege control - see. material about PAM |
| Rotation of the squad | Every six months new people and new input into the context | Fix in the contract the minimum retention period and replacement procedure |
| Dilution of responsibility | Arguments about whose defect is at every release | Determination of readiness and acceptance criteria agreed upon before launch |
How to choose: short matrix
- I have my own team lead and backlog, but not enough hands → staff augmentation.
- We need results, there is no internal technical management → dedicated command.
- The task is separable and measurable by the result; immersion in the context is not necessary → outsourcing.
- Peak load for 3–6 months → staff augmentation: faster entry and exit.
- A long-term product that you will develop yourself → staff augmentation with a view to transferring knowledge, or a mixed team.
- It is critical to keep the expertise inside → staff augmentation or mixed composition; pure outsourcing leaves knowledge with the performer.
- Strict requirements for information security and data access → any format, but with separation of media and limited access; You need to look not at the format, but at the contract and technical implementation.
The formats are not mutually exclusive. Working combination: a dedicated team launches the product and transfers it to the staff, then the workload is covered by individual specialists in staff augmentation mode.
Supplier verification checklist
- There is a valid PrEA accreditation, the registration number is verified according to the Rostrud register - if we are talking about staff augmentation.
- It is clear what format is fixed in the contract, and it corresponds to the actual interaction.
- The procedure and time frame for replacing a specialist are described.
- It is recorded who owns the rights to the result.
- Code, infrastructure and documentation are maintained on your systems.
- The definition of readiness and acceptance criteria have been agreed upon.
- The contractor's access is limited in time and the list of systems.
- The conditions for termination and transfer of cases are specified before the start of work, and not after the conflict.
- It is clear what will remain with you after the team leaves.
How it works for us
Both formats are closed by our direction IT staff augmentation and dedicated commands. Legal basis - accreditation of a private employment agency (entry in the Rostrud register) and state IT accreditation (confirmed in August 2026); both statuses are in one legal entity, so the contractual outline is uniform.
If the task is closer to “make a product”, it is custom development and system integration. If you need to employ foreign specialists in the Russian environment - EoR model.
If you are not sure which format is yours, describe the situation and we will offer an option with justification: write to us.
Briefly about formats and responsibilities — outsourcing development and dedicated team.
Let's discuss your environment
Describe the task, current systems, constraints, and expected results. We will offer a practical first step: diagnostics, pilot, audit, roadmap or project team.
