English 
Português
Every company that outsources a system eventually hears the same question from its vendor: “Do we fix the scope, or do we set up a squad?” The answer shapes your investment, the way you track delivery and how much of your own team’s time the work will require.
This guide explains how a fixed-scope project and a dedicated squad work inside a software factory, what each model typically costs, which mistakes to avoid and how to decide with seven objective questions.
Quick answer
Choose a fixed-scope project when scope, acceptance criteria and deadline are known and stable, and you want cost predictability. Choose a dedicated squad when the product evolves continuously, priorities change and the team needs to build up business knowledge. If you are unsure, start with a discovery phase: it shows whether the scope is mature enough to be fixed.
What is the difference between a fixed-scope project and a dedicated squad?
A software factory is a model in which the vendor is accountable for delivery (process, team and quality) under an SLA, meaning a formal service-level agreement on timeline and quality. Inside it, there are two main ways to engage.
In a fixed-scope project, price, timeline and scope are agreed before work starts for approved deliverables, and changes go through a formal change request. In a dedicated squad, an exclusive team works continuously on a backlog that you prioritize, for a fixed monthly fee. The first buys predictability; the second buys speed and continuity.
| Fixed-scope project | Dedicated squad | |
|---|---|---|
| What you buy | A defined set of deliverables | Ongoing capacity from an exclusive team |
| Who sets priorities | The contracted scope | You, through the backlog |
| How you pay | Total project price, in milestones | Fixed monthly fee |
| If scope changes | Formal change request, with impact on time and cost | The team reprioritizes every sprint |
You will also see time and materials (open scope), where you pay for the hours actually spent. It works as a flexible variant of the fixed-scope model and is often the billing basis for squad contracts. This guide compares the two models most companies actually put on the table.
One important caveat: a software factory is not a synonym for fixed scope, and a dedicated squad is not the same as staff augmentation. With staff augmentation, professionals join your team and follow your management. In a software factory squad, the vendor remains responsible for managing the team and for delivery. For a broader comparison, see Software Factory vs Outsourcing.
How NextAge works
At the NextAge Software Factory, the same multidisciplinary team (project manager or Scrum Master, architect, Product Owner, front-end, back-end and mobile developers, DevOps, UX/UI designer and QA) can work on a fixed scope or as a dedicated squad with a fixed monthly fee and SLA. The choice of format comes after discovery.
How does a fixed-scope project work, and when is it the best choice?
A fixed-scope project is the best choice when you know exactly what must be delivered, by when and against which acceptance criteria. In this format, the vendor takes on the productivity risk within the agreed scope, and you follow milestones rather than daily routines.
When it makes sense
- Requirements are clear and unlikely to change during execution.
- Acceptance criteria can be written before the start.
- Timeline and budget have already been approved internally.
- The work has a beginning, middle and end (a system integration, an app with well-defined features, a migration with a known scope).
- You do not have an internal team available to lead development.
Advantages
The main advantage is predictability: total investment and timeline are known from the start, which makes budget approval easier. There is also less management effort on your side, since governance happens through milestones and acceptance criteria.
Risks and how to reduce them
The central risk is fixing an incomplete scope. Software involves many decisions that only surface during construction, and each change becomes a renegotiation of time and cost, which creates contract amendments and friction. Four practices reduce this risk:
- Run a discovery phase before fixing the scope.
- Write objective acceptance criteria.
- Define a formal change request process.
- Reserve a budget margin for changes.
A study by McKinsey and the University of Oxford shows why this discipline matters. Across 5,400 IT projects, large projects (above US$ 15 million) ran on average 45% over budget and 7% over time, and delivered 56% less value than predicted; each additional year of duration added 15% to cost overruns (McKinsey, 2012). Among the cases in the same study, a public-sector organization defined its scope in an initial six-month phase, required board approval for any change and set a cost-overrun buffer below US$ 2 million. That is the well-executed version of a fixed-scope project: scope validated upfront, controlled changes and a financial reserve. Note that the study covers large projects and does not compare fixed-scope contracts with squads.
Is fixed scope the same as waterfall?
No. Fixed scope is a way of contracting (defined price and scope); waterfall is a way of executing (sequential phases). A software factory can deliver a fixed scope in two-week sprints, with a demo at the end of each cycle and formal change control. The difference lies in how the contract handles change, not in how the team works.
How NextAge reduces this risk
Discovery maps goals, users, processes, integrations and risks before development starts. The result is a clear scope, a prioritized backlog and a realistic estimate of timeline and investment.
How does a dedicated squad work, and when is it the best choice?
A dedicated squad is the best choice when the product has no “end date”: it evolves, receives new demands and shifts priorities as the business learns. Instead of buying a deliverable, you buy the ongoing capacity of a team that knows your product.
What a squad looks like
A squad usually brings together 4 to 10 professionals, with roles such as tech lead, front-end and back-end developers, QA, UX/UI designer, DevOps and Product Owner or business analyst. Size and composition depend on complexity and workload.
When it makes sense
- The digital product is in continuous evolution with a long roadmap.
- Priorities change every cycle, driven by the market and by usage.
- There is a backlog or technical debt that the internal team cannot absorb.
- Business knowledge (complex rules, integrations) must accumulate inside the team.
A market rule of thumb is to consider a dedicated team when the horizon exceeds roughly six months. It is a reference, not a rule.
Advantages
Knowledge stays with the team, which reduces the cost of relearning the product with every new project. Flexibility is high: the backlog is reordered every sprint without renegotiating the contract. And speed tends to be higher, because there is no rescoping phase for each change.
Talent market conditions reinforce the case for flexible capacity. According to the Brasscom report of May 2026 on Brazil’s tech labor market, 82% of companies plan to grow their IT teams over the next two years, and more than 50% of new openings will be mid-level or above. The same report shows that between December 2023 and December 2025, 55.6% of the increase in tech professionals came from contractors and informal work, and 44.4% from formal employment, and it points to the high cost of formal hiring as part of the bottleneck. In short, the challenge is not only finding people, but hiring experienced profiles at the pace the business needs.
Risks and how to reduce them
The risks are an ongoing monthly cost without clear goals, a backlog without priorities and dependence on the vendor. To mitigate them, agree on KPIs from the start, hold a quarterly results review, require documentation and repository access, and include exit and transition clauses.
How NextAge works
In one NextAge project, a fashion and luxury marketplace operating in 12 countries had more than 1,400 cataloged bugs and an internal team focused on new products. NextAge set up an agile squad, with senior QAs and developers, working in sprints and reporting directly to the CTO. The outcome: 100% of critical bugs resolved, 89% of the total backlog cleared and a 12% increase in checkout conversion. See the case and other results.
Fixed-scope project vs dedicated squad: side-by-side comparison
In short, fixed scope buys predictability; a squad buys speed and continuity.
| Criterion | Fixed-scope project | Dedicated squad |
|---|---|---|
| Best for | Clear, stable requirements; work with a beginning, middle and end | Evolving product; shifting priorities |
| Cost predictability | High, as long as scope does not change | High per month; the total depends on duration |
| Scope flexibility | Low: changes become change requests | High: reprioritized every sprint |
| Who sets priorities | The contracted scope | You, via the backlog, with the tech lead’s support |
| Speed to start | Requires discovery and detailed scope first | Fast start after proposal approval |
| Main risk | Incomplete scope: amendments and friction | Ongoing cost without goals; backlog without priorities |
| Product knowledge | Concentrated in the project; requires handover at delivery | Builds up in the team over time |
| Governance | Milestones and acceptance criteria | Two-week sprints, demos, KPIs and board access |
| Exit | Natural at the end of delivery; support is optional | Contractual notice; require documentation and client-owned repository |
How much does each model cost?
The cost of each model depends on scope, integrations, platforms, team seniority and tech stack. That is why the most useful comparison is not “project price vs squad monthly fee”, but total cost: price, cost of changes, cost of delay and management effort.
As a market reference for 2026, according to NextAge (in Brazilian reais; confirm the US dollar equivalent before publishing):
- Software factory project: tickets between R$ 80,000 and R$ 500,000, depending on complexity.
- Squad of 5 people (two mid-level developers, one senior, one QA and one tech lead): R$ 57,000 to R$ 95,000 per month through outsourcing.
These values vary with composition and project; use them as a starting point for conversations with vendors. For a breakdown by profile, see How much does a development squad cost.
How to choose: 7 questions to decide
Answer each question with A or B.
| # | Question | Answer A: fixed-scope project | Answer B: dedicated squad |
|---|---|---|---|
| 1 | Could you sign a document today that captures scope and acceptance criteria? | Yes, and they should not change | No, or they will change with use |
| 2 | What is the time horizon? | A single delivery, up to about 6 months | More than 6 months, or ongoing |
| 3 | How often do priorities change? | Rarely | Every month or every sprint |
| 4 | Who decides priorities every week? | No one available; I prefer to delegate delivery | I have a PO or product manager (or accept the vendor’s) |
| 5 | What happens after go-live? | Simple maintenance | Constant evolution |
| 6 | What does the budget look like? | An approved, fixed ceiling | Recurring monthly funding |
| 7 | How much business knowledge must the team accumulate? | Little | A lot (complex rules, integrations) |
How to read the result: 5 or more A answers point to a fixed-scope project. 5 or more B answers point to a dedicated squad. If answers are split (3 to 4 of each) or you answered “not sure” to question 1, start with a discovery phase and consider the hybrid path described next.
Is there a middle ground? The hybrid path
Yes, and it is the most common path for products that start with a well-defined first delivery and later need to evolve. The hybrid path combines both models in sequence:
- Discovery: map goals, users, processes, integrations and risks, and leave with a prioritized backlog and an estimate of timeline and investment.
- Fixed-scope project for the first delivery (MVP or first release), now with a mature scope.
- Dedicated squad to evolve the product, ideally with the same professionals, to preserve the knowledge built so far.
- Managed support (AMS) when the system becomes critical and stable.
The logic of keeping the same engineers when switching models also appears among international vendors such as Connext, which describes moving from a fixed-price phase to a dedicated team without losing knowledge of the system. A practical warning: a vendor that sells only one model tends to recommend that model. Ask whether it accepts moving from one to the other within the same contract.
How NextAge works
NextAge’s process has five stages: Discovery; architecture and design (with clickable prototypes); development in two-week sprints, with a demo at each cycle; validated quality, with dedicated QA and automated testing through the Quality Center; and deployment with Application Managed Services. If you are unsure about the model, the recommendation is to start with Discovery: talk to a specialist.
How to hire well, whichever model you choose: a 10-item checklist
- Accountability and SLA: who is responsible for delivery, and under which agreement on timeline and quality?
- Change management: how does scope change (change request, in a fixed-scope project) or how is work prioritized (squad)?
- Code ownership: intellectual property, source code and documentation belong to you from day one, with repository access.
- Team composition: seniority, tech lead, replacement policy and who bears the onboarding cost.
- Transparency: two-week sprints, demos, board access and a dedicated point of contact.
- Agreed metrics: critical bugs, test coverage, deliveries per sprint, lead time and cost per delivery.
- Quality: dedicated QA, automated tests and code review.
- Security and data protection built into the development lifecycle.
- Exit and transition: termination clauses, model migration and knowledge transfer.
- Use of AI in the process: at which stages it is used and what gain has been measured.
How NextAge answers this checklist
NextAge offers a delivery SLA, keeps intellectual property, repository and documentation with the client, and lets you start small and scale based on results. Deliveries happen every two weeks, with review meetings, access to the project board and a dedicated point of contact.
6 common mistakes when choosing a model
- Fixing the scope without discovery. The usual result is an incomplete scope, amendments and friction.
- Hiring a squad without anyone to prioritize the backlog. The team lacks direction and the monthly cost loses its purpose.
- Deciding on the lowest price alone. The McKinsey study recommends looking beyond unit price when negotiating with vendors, because rework, delays and team turnover weigh on the final cost.
- Treating fixed scope as a synonym for waterfall or for “no changes”. Changes happen; what differs is how the contract handles them.
- Not planning the transition. Without documentation and a client-owned repository, knowledge stays locked with the vendor.
- Confusing a dedicated squad with staff augmentation. If you have to manage the people and train replacements, what you bought was staff augmentation.
How does AI change this decision in 2026?
Artificial intelligence is now part of the development process, and it belongs in any vendor comparison, regardless of the contract model. The relevant question is no longer just “how much does it cost?” but “how much does this team deliver per dollar invested?” When evaluating a partner, ask at which stages AI is used (code review, testing, documentation, pipelines), what gain has been measured and how it shows up in timeline and cost.
How NextAge works
The NextFlow AI methodology combines specialists and artificial intelligence at every stage of development and, according to NextAge, delivers up to 40% faster, with automated documentation. NextAge also builds AI agents integrated into clients’ systems.
Frequently asked questions
What is the difference between a fixed-scope project and a dedicated squad?
In a fixed-scope project, price, timeline and scope are agreed before work starts for approved deliverables. In a dedicated squad, an exclusive team works continuously on a prioritized backlog for a fixed monthly fee. The first favors cost predictability; the second favors flexibility and speed for evolving products.
When should I choose a fixed-scope project?
When requirements, acceptance criteria and deadline are clear and stable, the work has a beginning and an end, and the budget is approved. Typical examples are system integrations, an app with well-defined features or a migration with a known scope. If the scope is not yet mature, run a discovery phase before fixing it.
When should I choose a dedicated squad?
When the product evolves continuously, priorities change every cycle and the team needs to build up business knowledge. It is common for digital products, platforms with a long roadmap, accumulated backlogs and technical debt. A market rule of thumb is to consider a squad when the horizon exceeds about six months.
Is fixed scope the same as waterfall?
No. Fixed scope is a contracting model, with defined price and scope; waterfall is an execution method with sequential phases. A software factory can deliver a fixed scope in two-week sprints, with demos and formal change control. The difference lies in how the contract handles change.
How much does a dedicated squad cost?
It depends on composition, seniority and tech stack. As a NextAge reference for 2026, a squad of five (two mid-level developers, one senior, one QA and one tech lead) costs R$ 57,000 to R$ 95,000 per month through outsourcing.
How much does a fixed-scope project cost?
The value depends on scope, integrations, platforms and complexity, so it is estimated after a discovery phase. According to NextAge, software factory projects typically have tickets between R$ 80,000 and R$ 500,000, depending on complexity.
Can I start with a fixed-scope project and move to a dedicated squad?
Yes, it is a common path: discovery defines the scope, a fixed-scope project delivers the first version and a dedicated squad then evolves the product, ideally with the same professionals to preserve knowledge. Agree on this possibility in the contract from the start, with clear transition rules.
Will my company own the source code?
At NextAge, intellectual property, source code and documentation belong to the client, as set out in the contract. With any vendor, confirm this in writing and require repository access from day one, so you do not depend on the vendor if you ever switch.
What is the difference between a dedicated squad and staff augmentation?
In a software factory’s dedicated squad, the vendor is responsible for managing the team and for delivery, under an SLA. With staff augmentation, professionals join your team and follow your management. If you have to manage the people and train replacements, what you bought is staff augmentation.
Conclusion
No model is better in absolute terms. A fixed-scope project is the right choice when the scope is stable and predictability matters most; a dedicated squad is right when the product evolves and speed matters. Between the two, the hybrid path (discovery, fixed-scope project and an evolution squad) is usually the safest for those still maturing their scope.
If you want to decide with data from your own situation, start with discovery: it shows what can be fixed, what should stay open and which format makes the most sense. Start with Discovery or talk to a NextAge specialist.
Related reading
