“We have five contractors. Why is nothing reaching production?”
Because you did not rent a team. You rented five timesheets. Three vendors, three replacement clauses, no shared Definition of Done, and the Scrum Master is the product owner after hours. Brooks described this failure in 1975. In 2026 we buy it on a T&M invoice and call it “scaling”.
What most briefs miss: staff augmentation (body leasing, one contractor) vs team leasing (a dedicated squad, IT team outsourcing). This is not a fight about synonyms. It is a fight about who owns cadence, code review and knowledge when the only person who understands the pipeline disappears on a Friday.
The sentence missing from the sales slide
A team is not a headcount on a kick-off call. A team is a unit that carries its own cognitive load: it ships an increment, reviews it and returns to production without opening a ticket with three account managers. If that unit does not exist, you have staff augmentation with a group discount. Not team leasing.
1. What you are actually buying
Three models get sold from the same deck. They diverge in sprint one.
| Model | What is on the invoice | Who owns DoD and cadence | SLA unit |
|---|---|---|---|
| Staff augmentation / body leasing | An hour of one person inside your team | You. The contractor joins your stand-up, your Git, your on-call. | The person: availability, role replacement, skills |
| Team leasing / dedicated team | A squad of 4–8, usually with a TL or SM | Vendor operationally. You keep the “what” and the “why”. | The unit: increment, composition, replacement without killing the stream |
| Fixed price / work package | An outcome, not an hour | Vendor end-to-end | Scope, date, acceptance. Scope must be closed. |
| Perm hire / direct B2B | FTE or a direct contract | You, 100% | Employment or B2B. Time-to-fill is yours. |
Staff augmentation works when you already have a team and you are missing one gap: a senior Java, Fiori, SRE. Team leasing works when there is nobody to drop that person into — no lead, no QA, nobody who will say “we are not merging this”. Adding a fourth developer into a vacuum is the most expensive way to keep a ticket in “in progress”.
Hourly bands and TCO vs payroll are a separate map: IT body leasing rates in Poland 2026. This article does not repeat the rate card. It counts the point where headcount stops being a team.
2. Anatomy of a fake team
A typical Q3 2026 brief: “we need 2 backend, 1 frontend, 1 QA, preferably from Monday”. HR fires four job ads or four RFPs to three software houses. Six weeks later you have four names. On the board slide that is “a product squad for hire”. In Jira it is four independent queues.
What breaks first:
- Communication channels. Brooks, The Mythical Man-Month (1975): channel count is n(n−1)/2. 4 people = 6 channels. 5 = 10. 8 = 28. Add 3 vendors and 3 account managers. That is not collaboration. That is a network nobody moderates.
- Mismatched replacement SLAs. Vendor A replaces backend in 5 days. Vendor B has no frontend on the bench. Vendor C invoices QA in a different window. The stream stalls on the slowest contract, not the weakest engineer.
- No owner of DoD. Each contractor ships “their tickets”. Nobody ships the increment. Code review eats the client’s senior, who was only supposed to “keep an eye on architecture”.
- Unstable priorities by construction. DORA 2024: unstable organisational priorities cut productivity and raise burnout — an effect even a good lead does not cancel. Five briefs from five departments are unstable priorities baked into the purchase.
The architectural takeaway
Team Topologies (Skelton and Pais, 2019) distinguishes a stream-aligned team from “people on one Slack channel”. Cognitive load is carried by the team, not the individual. If you pour four contractors into a stream with no platform, no DoD and no lead, you bought load, not throughput. DORA 2024 adds a second layer: AI lifts individual productivity and can still chew delivery stability. In a fake team that split shows up in two sprints: a lot of commits, not much release.
3. What the research says, not the deck
You do not need another outsourcing definition. You need the boundaries where the model snaps.
- Size. Scrum Guide 2020: a development team is typically 10 or fewer. Above that — too much complexity to manage empirically. Team Topologies and the two-pizza team: 5–9. DORA 2025 talks about a real team as a group of 5–12 people who deliver a shared outcome every day — not an HR org-chart cell.
- Throughput vs stability. DORA 2024 (~39k respondents): elite vs low is an order of magnitude, not a percentage — including ~182× more frequent deploys and ~127× shorter lead time (2024 clusters). Those numbers describe teams, not a sum of freelancers. You cannot assemble them from five separate timesheets.
- User-centric vs feature factory. DORA 2024: user-centric teams build a better product, burn out less and produce more. Team leasing with one SM and one backlog has a chance of being user-centric. Five contractors on five tickets are a feature factory by definition.
- Time. JobHunt, 1 September 2026: 21,211 active IT ads in Poland, average ad lifetime 50 days. Five perm roles opened in parallel are still five funnels and a quarter before the squad sits in one stand-up. The funnel split (frontend full in 48 h, SAP empty at 28–33k PLN B2B) is in IT recruitment 2026.
Operational conclusion: squad time-to-start is not “5 × time-to-start of one person”. It is max(time-to-start of the rarest role) + stitching cost. In team leasing, stitching is in the price. In staff augmentation you pay it with an internal lead you never added to TCO.
4. Two line-ups, two outcomes
🛠️ From the floor: five timesheets vs one stream
Variant A — fake team. Fintech, new KYC onboarding. Brief: 2 Java, 1 React, 1 QA, “we have an SM”. Three vendors, staggered start over 3 weeks. After sprint 4: React waits on the API, QA tests mocks, the client SM owns two other streams. Velocity counted in tickets looks healthy. In production — one increment a month. Cost: ~5 × 200 PLN/h × 160 h ≈ PLN 160k/month plus three account managers plus a client lead at 30% FTE that Excel does not see.
Variant B — team leasing. Same scope, different purchase: 1 TL/SM + 2 Java + 1 React + 1 QA, one contract, one stand-up, role replacement in 5 business days (2 profiles). Squad start in 12 days from the bench. First increment on a test environment in sprint 2, not 5. Hourly rate comparable. The difference: one invoice, one DoD, one person allowed to say “this does not enter the sprint”.
That is not process magic. It is the removal of an integration tax that variant A hid in the lead’s calendar.
5. Squad recipes that actually ship
There is no single “team for hire”. There are a few recipes that stay inside 5–8. Below are line-ups that start in 2026 — not a slide that stuffs full-stack + AI + SAP + DevOps into one team.
| Stream | Line-up (5–6) | When this recipe | What not to add |
|---|---|---|---|
| Feature / product | TL or SM + 2 backend + 1 frontend + 1 QA | New module, 3–9 months, you have a PO on your side | A second SM, an “architect at 0.2”, a sixth mid “just in case” |
| Platform / DevOps | 2 DevOps/SRE + 1 platform backend + 1 TL | CI/CD, observability, cluster FinOps — not “we’ll bolt Kubernetes onto the feature team” | A frontend engineer. A platform does not need React to ship a pipeline. |
| SAP / ERP | 2 consultants + 1 ABAP/Fiori + 1 SM | Build/run, when the perm ad sits empty | A Java mid “we’ll train them on Fiori”. That variant costs a year and one failed go-live. Landings: SAP, Dynamics. |
| AI / RAG in production | 2 LLM/RAG + 1 backend + 1 data + 1 SM | Index, evaluation, token cost — not a notebook PoC | A “Python developer” who was also going to “cover RAG”. The market split; an LLM rate is not CRUD. AI, RAG. |
Order of magnitude for a 5-senior squad at ~200 PLN/h on the client side: 5 × 160 h × 200 = PLN 160k net/month. An SM/TL in the line-up is cheaper than a client SM at 40% FTE plus three vendors. Bands by stack: 2026 rate map.
6. Decision matrix: squad, one person, outcome or payroll
| Situation | What to buy | Why |
|---|---|---|
| A 1–2 role gap in an existing team; you have a lead and a DoD | Staff augmentation | Do not smash the cadence with a second team. You are adding a skill, not a structure. |
| A new stream, 4+ people, no spare SM/TL | Team leasing | One SLA, one backlog, one kick-off. Time-to-start is measured on the line-up, not the job ad. |
| A module with a hard spec, scope you can close, 3–6 months | Fixed price | You buy an increment, not an hour. A living scope kills this model in sprint 2. |
| A core team for 24 months, a profile with supply (frontend, common backend) | Perm hiring or direct B2B | A 10–25% margin stops paying back after ~12 months on an easy profile. On SAP/Fiori — rarely. |
| You want 12 people as “one team” | Two team-leasing squads, or a squad + staff augmentation | That is not a large team. That is two teams with a hidden handoff. Split the stream before Brooks splits you. |
If the brief says “hire developers” and in practice you need one role, do not stretch it into team leasing. The page that sells that path directly: software-developer outsourcing. Team leasing starts where headcount needs its own nervous system, not an extra stand-up in your calendar.
7. Anti-patterns that never make the proposal
- A “team” of 5 CVs that have never shipped a sprint together. That is staff augmentation on a group invoice. Ask: how many sprints has this line-up delivered as a line-up, not as a skill list.
- Team leasing, then scattering people across three internal squads. You bought a unit and dismantled it. Cognitive load returns to your leads; the vendor SLA stops being measurable.
- Four people with no lead “because we have an SM”. You have an SM on two other streams. That is not an SM. That is a hope.
- One vendor per role. Java from firm A, React from B, QA from C. Integration is your project — nobody named it in the SOW. Contracts, IP and hidden margins: the contract guide.
- No knowledge-transfer clause in the SLA. After 90 days the only person who knows the pipeline moves to another contract. Bus factor 1 was in the price. It was not in the agreement.
- 12 people, one daily. The daily runs 35 minutes, priorities drift, DORA calls that instability. Two squads of 6 with an explicit contract between streams is cheaper.
8. How we put this together
Commoditech has done IT contracting from Poland since 2012. We do not sell a “team” when the brief asks for one senior. We do not sell five seniors with no lead when the brief asks for a stream.
- Margin 10–25%, open-book, counted per role. The line-up does not get a “bundle discount” that hides mark-up. Margin FAQ.
- First CVs in 24–48 h from the bench; squad start usually 8–15 days. Gaps that are not on the bench go to direct search — and that shows up in the date, not in a slide.
- A 2-week trial per person. If the skills do not stand up in a sprint, you do not pay for hope.
- Replacement SLA: 5 business days, 2 profiles. In team leasing we replace a role in the line-up, not “someone similar on a different ticket”.
- IP transfers with the monthly timesheet. Not after a “final protocol” nobody will sign in sprint 7.
Paths from this matrix:
- IT team leasing — line-up, one SLA, one stream.
- IT staff augmentation — one role into an existing team.
- Java, React, DevOps, SAP, AI / LLM — when you know which skill is missing and you have somewhere to put it.
- A brief — stream or gap, seniority, start date, working mode, who the PO is. Without that, every table lies.
9. FAQ
What is the difference between team leasing and staff augmentation?
Staff augmentation rents one person into your team: your stand-up, your Git, your DoD. Team leasing rents a squad of 4–8 with its own cadence, one SLA and one invoice. You keep the goal and increment sign-off. The vendor keeps composition, code review and role replacement. If you task each person separately, it is still staff augmentation — whatever the proposal title says.
How many people should a rented IT team have?
5–8, rarely 9. Scrum Guide: typically 10 or fewer. Below 4, staff augmentation plus a lead you already have is usually enough. Above 9 you have two teams. DORA 2025 describes a real team as 5–12 people delivering a shared outcome daily — not a line on an org chart.
Is team leasing more expensive than several separate contractors?
The hourly rate is similar, because the 10–25% margin sits on the role. A line-up with SM/TL is more expensive on the invoice and cheaper in TCO when it removes 3 vendors, 3 onboardings and a client lead at 30–40% FTE. Five staff-augmentation seats from three firms is not a volume discount. It is an integration tax that never made the SOW.
Who manages the team — client or vendor?
Client: roadmap, priorities, the “what” and the “why”, sign-off. Vendor: composition, cadence, quality, replacement. DORA 2024: unstable priorities burn productivity regardless of talent. If every stakeholder tasks a different person in the line-up, the team disappears. You are left with five queues.
How fast does a squad start in 2026?
Bench: CVs in 24–48 h, squad start 8–15 days. Mixed line-up (bench + 1–2 market roles): 3–4 weeks. Five perm hires at a 50-day ad lifetime (JobHunt, September 2026) is a quarter to a full line-up — assuming SAP/Fiori answers the ad at all.
What about IP, NDA and rotation in team leasing?
Same as staff augmentation, except the unit is the line-up. IP with the timesheet, not a final protocol. NDA on the squad, not on “whoever happens to commit today”. Rotation: replace a role in the line-up, do not restart the stream. Clause detail: contracts, margins, IP.
10. Sources
- Frederick P. Brooks Jr. — The Mythical Man-Month, Addison-Wesley, 1975 (and later editions). Communication channels n(n−1)/2; adding people to a late project makes it later.
- Matthew Skelton, Manuel Pais — Team Topologies, IT Revolution, 2019. teamtopologies.com. Stream-aligned team, cognitive load, inverse Conway.
- Scrum Guide 2020 — team size typically 10 or fewer.
- DORA — Accelerate State of DevOps 2024 (Google Cloud; ~39k respondents). User-centric teams, stable priorities, AI vs throughput/stability. Elite/low clusters: see 2024 discussion (incl. ~182× more frequent deploys).
- DORA 2025 — team archetypes; a real team as a group of 5–12 people collaborating daily on a shared outcome (not an HR cell).
- JobHunt.pl — Polish IT market 2026. Snapshot 1 September 2026: 21,211 ads, average ad lifetime 50 days.
- Commoditech — 2026 body-leasing rates, IT recruitment 2026, contracts and IP, 10–25% margin.