Most guides list "outsourcing models" as one flat list that mixes staff augmentation, fixed price and nearshore development as if they were alternatives. They answer different questions. A company can hire a nearshore dedicated team on a monthly retainer, or buy a fixed-price project from an onshore vendor, and each combination behaves differently in cost, control and risk.
A software development outsourcing model is the combination of an engagement model, a pricing model and a location model, and choosing well means matching each of the three to how clear your requirements are, how much management capacity you have and how long the work will last.
This article explains each layer, compares fixed price and time and material contracts, and shows which combinations work in practice, using .wrk projects as examples. It does not rank vendors, and it does not cover business process outsourcing outside software.
Key takeaways
- Every outsourcing arrangement combines three choices: an engagement model, a pricing model and a location model.
- Engagement models range from staff augmentation, where you manage the work, to project outsourcing and managed services, where the provider owns delivery.
- Fixed price works for stable, well-defined scope, while time and material suits evolving products where requirements change.
- Monthly retainers for a stable team suit long roadmaps and keep product knowledge in one place.
- Nearshore teams with four or more hours of daily overlap give most US and European companies the best balance of cost and collaboration.
- Buyers are moving toward outcomes: Deloitte found that 67% of organizations are adopting outcome-based outsourcing relationships.
The three layers of an outsourcing model
| Layer | The question it answers | Main options |
|---|---|---|
| Engagement model | Who manages the work and owns the result? | Staff augmentation, dedicated team, project outsourcing, managed services |
| Pricing model | How is the work paid for? | Fixed price, time and material, milestone-based, monthly retainer, capped time and material |
| Location model | Where is the team and how much does its working day overlap with yours? | Onshore, nearshore, offshore |
Deciding these one at a time keeps the discussion clear. A vendor offering "a nearshore model" has answered only one of the three questions.
Layer 1: engagement models
Staff augmentation
Individual specialists join your team, and your managers direct their daily work. The provider handles hiring, payroll, equipment and replacement. Responsibility for delivery stays with you.
When it fits: you have a working engineering process and need specific skills or more capacity. Our guide to what staff augmentation is covers the model in detail.
Dedicated team
A stable, cross-functional team works only on your product, usually with a lead, developers and QA. It can be managed by you, jointly or by the provider.
When it fits: ongoing roadmap work where product knowledge and stable velocity matter. See dedicated team vs staff augmentation for how the two compare.
Project outsourcing
The provider takes responsibility for delivering a defined scope, with its own delivery lead, plan, QA and reporting. You approve the scope, review progress and accept the result.
When it fits: a product, module or migration with a clear goal and an end date.
Managed services
The provider runs an ongoing function, such as application support, maintenance or infrastructure operations, against agreed service levels. You pay for the service, and the provider decides how to staff it.
When it fits: stable, well-understood work that needs to run reliably and that your team does not need to own day to day.
Layer 2: pricing models
Fixed price
You agree on a scope, a timeline and a total price before work starts. The provider carries the risk of underestimating, which it covers with a buffer in the price.
Works when: requirements are stable and detailed, such as a website rebuild, a defined integration or a first MVP with locked features.
Watch for: change requests. Every change to a fixed scope becomes a negotiation, so agree a change process and a rate for additional work in the contract.
Time and material
You pay for the hours or days the team actually works, usually against monthly invoices with timesheets. Scope can change from sprint to sprint.
Works when: the product is evolving, priorities shift and you want to adjust direction without renegotiating.
Watch for: open-ended spend. Use a monthly budget cap, sprint goals and regular reporting to keep costs predictable.
Milestone-based
Payment is tied to agreed deliverables, such as a working prototype, a completed migration phase or a passed acceptance test. It is common for larger programs that are too uncertain for a single fixed price.
Works when: the program can be split into phases with clear acceptance criteria.
Monthly retainer for a team
You pay a fixed monthly fee for a team of agreed size and seniority. This is the usual pricing for dedicated teams and staff augmentation.
Works when: you need continuous capacity over months or years and want predictable costs.
Capped time and material
A hybrid that bills actual time but sets a maximum for a phase or sprint. It gives you flexibility within a budget limit, and it is often used for discovery phases and first releases.
Fixed price vs time and material
| Fixed price | Time and material | |
|---|---|---|
| Scope | Defined and frozen before work starts | Can change sprint by sprint |
| Budget | Known upfront, with a risk buffer included | Known per month, total depends on scope decisions |
| Who carries estimation risk | The provider | You |
| Speed to start | Slower, because scope must be detailed first | Faster, because work can start with a backlog |
| Change handling | Formal change requests and repricing | Reprioritize the backlog |
| Best for | MVPs with locked features, migrations, rebuilds with clear specifications | Product development, integrations with unknowns, long roadmaps |
Many teams combine the two. A short fixed-price or capped discovery phase produces a detailed scope, and the build then runs on fixed price if the scope is stable or on time and material if it is likely to change.
Layer 3: location models
- Onshore: the team is in your own country. Collaboration is easiest, and rates are the highest.
- Nearshore: the team is in a nearby region with a large time-zone overlap, such as Central and Eastern Europe for Western European companies or Latin America for US companies. Rates are lower, and real-time collaboration still works.
- Offshore: the team is in a distant region with little overlap. Rates are the lowest, and the model depends on strong asynchronous processes and documentation.
Overlap matters more than distance. Central and Eastern European teams typically overlap two to five hours with US East Coast working hours and almost fully with Western Europe, which is enough for daily stand-ups, reviews and quick decisions.
Talent supply also shapes the choice. Eurostat reports that in 2023, 57.5% of EU enterprises that recruited or tried to recruit ICT specialists had difficulty filling those vacancies, with rates above 70% in Germany and Czechia. Outsourcing to a nearby region is often the fastest way around that shortage.
Not sure which combination fits your project? Tell us about your scope, timeline and team, and we will propose an engagement model, pricing and team setup.
Explore IT outsourcingCombinations that work in practice
The examples below come from .wrk projects. Each one shows a different combination of engagement model, budget structure and duration.
Project outsourcing at a fixed budget: a website modernization
Connell Guides, a UK publisher of study guides with a student subscription site, had a Drupal 7 platform hit by spam registrations, security vulnerabilities and weak mobile performance. The budget was fixed. A .wrk team of backend, frontend and a PM ran a security-first sprint, rebuilt the responsive layouts and set up analytics and subscription permissions. The project came in 18% under the original budget, bounce rate fell to about 4% and on-page engagement rose 14%. Read the Connell Guides case study.
Fixed-scope MVP, then a second phase: an EdTech startup
PrepClass needed a mobile app and an admin site in four weeks on a tight budget. Scope was locked in workshops, and .wrk delivered a working app and admin within three weeks of sign-off. A second phase added courses, analytics and Q&A once the first version proved itself with 15,000 active users and a 4.8 rating in two weeks. Read the PrepClass case study.
Phased project delivery on a hard deadline: a conference data platform
HIMSS, a US healthcare technology nonprofit, runs more than 20 conference and media websites. Its analytics service failed when a record 45,000 attendees arrived within seven days. .wrk replaced it with a central data platform and a collection microservice in one month, moving through data modeling, build, migration, load testing and parallel running. At the next conference, the system handled the same peak without disruption. Read the HIMSS case study.
A dedicated team over five years: a healthcare platform
A Canadian chronic pain platform has worked with the same .wrk team of a PM, backend, mobile, frontend, QA and DevOps engineers for more than five years. The ongoing engagement covered a move to microservices, SOC 2 certification, an alert engine with more than 30 alert types and a switch to two to three week release cycles. Read the healthcare platform case study.
Ongoing maintenance with one developer: a shared framework
After building a shared Drupal framework for HIMSS media sites such as Healthcare IT News and MobiHealthNews, .wrk assigned one developer to maintain it alongside its documentation. Annual redesigns that once needed months of team work now take one developer about a week, and redesign costs fell by 10 to 12 times. Read the HIMSS framework case study.
Staff augmentation for a specialist phase: data engineering
A US cybersecurity media company added two .wrk data engineers to its marketing operations team. Working under the client's direction, they restructured the Snowflake warehouse and normalized CRM fields to between 93% and 99.7% coverage. Read the data platform case study.
How to choose your outsourcing model
Three questions narrow the choice quickly.
- How clear are the requirements? If they are detailed and stable, consider fixed price or milestones. If they will change, use time and material or a retainer.
- How much management capacity do you have? If your managers can direct more people, staff augmentation is efficient. If not, choose a dedicated team with its own lead or project outsourcing.
- How long will the work last? For a few weeks or months with an end date, project outsourcing fits. For a year or more, a dedicated team keeps knowledge in one place.
| Your situation | Engagement model | Pricing model |
|---|---|---|
| Clear MVP with locked features and a deadline | Project outsourcing | Fixed price |
| Large migration with distinct phases | Project outsourcing | Milestone-based |
| Evolving product with a long roadmap | Dedicated team | Monthly retainer |
| Skill gap inside a working team | Staff augmentation | Monthly retainer or time and material |
| Unclear scope, need to explore first | Project outsourcing for discovery | Capped time and material |
| Stable system that must keep running | Managed services | Fixed monthly fee with service levels |
Where outsourcing models are heading
Buyers are shifting from paying for effort to paying for results. In Deloitte's Global Outsourcing Survey 2024, 67% of organizations said they are adopting outcome-based relationships, up from 45% two years earlier, while 29% still used a traditional staff augmentation model. Cost reduction was named as a driver by 34% of respondents, down from 70% in 2020, while access to talent was cited by 42%.
In practice, this means more contracts with clear deliverables, acceptance criteria and service levels, even when the team is billed monthly. A good provider can report against outcomes in any of the models above.
Frequently asked questions
What are the main software development outsourcing models?
The main engagement models are staff augmentation, dedicated teams, project outsourcing and managed services. They are combined with a pricing model, such as fixed price, time and material, milestones or a monthly retainer, and a location model: onshore, nearshore or offshore.
What is the difference between fixed price and time and material?
In a fixed price contract, scope and price are agreed upfront, and the provider carries the estimation risk. In time and material, you pay for the time actually worked, which allows the scope to change as the project evolves.
Which outsourcing model is best for a startup?
Startups building a first version usually do well with a fixed-scope MVP on fixed price or capped time and material, followed by a dedicated team on a monthly retainer once the product needs continuous development.
What is an outsourcing engagement model?
An engagement model defines who manages the work and who is responsible for the result. In staff augmentation, you manage the specialists. In project outsourcing and managed services, the provider owns delivery.
Is nearshore or offshore outsourcing better?
Nearshore suits teams that need daily real-time collaboration, while offshore suits well-documented work that can run asynchronously at lower rates. For most US and European product teams, nearshore offers a better balance of cost and communication.
To sum up
An outsourcing model is three decisions: who manages the work, how it is priced and where the team sits. Match the engagement model to your management capacity, the pricing model to how stable your requirements are and the location to how much real-time collaboration you need.
.wrk has delivered more than 140 projects since 2011 for US and European companies through staff augmentation, dedicated teams and full-cycle project outsourcing, with fixed-scope, milestone and retainer pricing.
Planning to outsource a product, module or migration? Share your scope and timeline, and we will propose the right model, team and pricing.
Explore IT outsourcing