When you need more engineering capacity, or someone to keep an application running, there are three common ways to buy it. Picking the wrong model is a frequent source of frustration, so it helps to understand the differences before you sign anything.
The three models
Each model answers a different question about who manages the work and who carries the risk.
- Staff augmentation: individual people join your team and your management. You decide the tasks; the provider supplies skills.
- Dedicated team: a ready-made team, usually with its own project management and QA, works on your product on a monthly basis. The provider is accountable for delivery.
- Fixed-scope project: a defined outcome for an agreed price and timeline, delivered by the provider's own team.
How they compare
Staff augmentation gives you the most day-to-day control and the least management help. It works well if you already have strong technical leadership and just need extra hands.
A dedicated team gives you predictable monthly cost, built-in delivery management and the flexibility to change direction as priorities change. You trade a little control for much less coordination effort.
A fixed-scope project gives the most cost certainty, provided the scope is genuinely clear. It is less suitable when requirements will change, because every change becomes a negotiation.
When each one fits
A rough guide:
- Choose staff augmentation when you have the managers and architects, and need to add specific skills quickly.
- Choose a dedicated team when your roadmap is long, your needs will evolve, and you want one accountable team without hiring.
- Choose a fixed-scope project for a well-defined build, a migration, an assessment or an upgrade.
- Choose a maintenance and support agreement when software is live and needs steady upkeep rather than new features.
Questions to ask any provider
Before you sign, ask:
- Who manages the team day to day, and who reports to me?
- Which roles are included: project manager, tech lead, QA, DevOps?
- How is cost calculated, and what are the notice periods for scaling up or down?
- How is knowledge documented, so I am not dependent on specific people?
- What reporting will I get, and how often?
- Who owns the code and the work product?
You can combine them
The models are not exclusive. Many successful engagements begin with a fixed-scope assessment, move to a dedicated team to build and grow the product, and then settle into a maintenance and support agreement once the system is stable.
If you would like to talk through the right shape for your situation, see our dedicated teams service or book a free consultation.