Hiring, agency or dedicated team: choosing how to add capacity
The short answer
Hire in-house when the work is permanent and core. Use a fixed-price project when requirements are stable and you want a defined outcome. Use a dedicated team when the work is continuous but the requirements move — you keep control of priorities without a recruitment cycle.
Key takeaways
- Requirements stability is the deciding variable, not the hourly rate.
- In-house is cheapest over years and slowest to start.
- Fixed-price punishes changing requirements; that is the trade you are making.
- Whatever you choose, insist knowledge is documented as it is created.
These three get compared on hourly rate, which is the least useful axis. Compare them on how stable your requirements are, and on where the knowledge ends up.
The comparison
| In-house | Fixed-price project | Dedicated team | |
|---|---|---|---|
| Time to start | 2–4 months | 2–4 weeks | 1–2 weeks |
| Cost per hour | Lowest over years | Highest | Middle |
| Control of priorities | Full | Limited to scope | Full |
| Handles changing needs | Well | Badly | Well |
| Scale down | Hard | Automatic | 30 days |
| Knowledge retained | Yes | Only if documented | Only if documented |
Choosing
- Permanent and core
- Hire. Nothing beats an in-house team over a three-year horizon, and the two-to-four month lead time is worth absorbing for work that defines the business.
- Stable requirements, defined outcome
- A fixed-price project, with a written scope and a change process everyone agrees to before it is needed.
- Continuous work, moving requirements
- A dedicated team. You set priorities weekly; there is no recruitment cycle, notice period or payroll.
- A skill needed six weeks a year
- A specialist on retainer. Do not create a role for it — you will not fill it well and you will not keep them busy.
Making an embedded team work
Non-negotiables
- One backlog, in your priority order. A separate backlog produces a separate product.
- In the rituals — stand-ups, planning, retrospectives. A team excluded from planning is a vendor with a nicer name.
- Real overlap hours, agreed before starting.
- Two-way code review — they review yours, you review theirs. Fastest knowledge transfer there is.
- Documentation as a condition, not a hope.
The arrangement that works best is a small in-house core owning the product knowledge, augmented for delivery capacity — the core keeps the context, the capacity flexes with the roadmap. More on Dedicated Teams and in staff augmentation vs outsourcing.