Dedicated development team: composition, monthly cost and when it pays off

It is Thursday and the board meets next week. The CTO of a mid-sized logistics software company in Munich has an 18-month roadmap on the table: a new customer portal, integrations with three carriers and a driver app. She has three developers, one of whom spends half of every week firefighting on the legacy platform. Recruiting two senior engineers has been running since May; it produced one offer, which the candidate turned down for a competing one in Berlin. The board’s question sounds simple: “Do we add five contractors, or do we take a whole team from a vendor? And what does that cost per month?”

It is a good question asked the wrong way. The choice is not about headcount. It is about who manages the work day to day and how long the work will last. Those two answers decide whether a dedicated development team is the best purchase in the engineering budget or the most expensive way to solve a problem two contractors could have handled.

This article is written for the CTO facing that decision. We show who sits in a dedicated team, how to calculate its monthly cost from day rates in a way a CFO can check, what moves the price up and down, and when the model pays off and when it does not. Every calculation uses ARDURA Consulting’s published rate card for engineers based in Poland, so you can verify the numbers and replace them with your own.

What exactly is a dedicated development team?

A dedicated team is a cohesive, self-organising unit that works only on your product or on a defined area of it. It has its own tech lead or scrum master, its own rituals and its own internal coordination. You set the roadmap, the priorities and the definition of done; the team runs its own day-to-day work. Instead of steering five individuals, you steer one unit.

That separates it from staff augmentation, where individual specialists join your existing team and work under your direct management. The two are not rivals but points on one spectrum: the more roles and the longer the horizon, the more it pays to move coordination inside the team. A side-by-side comparison is on our page staff augmentation vs dedicated team.

A dedicated team also differs from project outsourcing in who owns the outcome. In a fixed-scope project the vendor commits to a defined result and carries the estimation risk. A dedicated team delivers capacity: a stable group that spends many months building whatever you decide matters most. Scope can change every sprint, and you pay for the team, not for a feature list.

That difference has budget consequences. The monthly cost is predictable, but you decide what it is spent on. If the backlog is chaotic, the team will efficiently build chaos. So the first question before buying is not “what does it cost” but “do we have someone who will own the product”.

Who is in a typical dedicated team?

Composition depends on what the team has to build, but three configurations recur. The rule behind all of them: the team should contain every skill needed to ship a working feature to production without waiting on people outside it. The 2020 Scrum Guide describes a Scrum Team as small enough to remain nimble and large enough to complete significant work within a sprint, typically ten or fewer people. That is a good ceiling for a dedicated team as well.

Minimum team, three people. A tech lead who writes code and makes architecture calls, one developer and a QA engineer. Enough to evolve one well-bounded module or integration. It is also the threshold at which ARDURA Consulting talks about a dedicated team at all: our pricing page sets a minimum of three specialists and three months.

Product team, five people. A tech lead, two backend developers, a frontend developer and a QA engineer with test automation. Usually the right starting point for a new web product or a large workstream inside an existing system. Small enough that communication does not eat the day, large enough that one person’s holiday does not stop delivery.

Extended team, seven people. The product team plus a second frontend or mobile developer and a DevOps engineer, sometimes a part-time project manager. This makes sense when the product has several interfaces, its own cloud infrastructure and frequent releases. Beyond seven or eight people it is usually better to split into two teams with their own areas than to keep adding to one.

None of these configurations includes a vendor-side product owner. That is deliberate. The person who decides what matters more must sit in your organisation and know your business. A vendor can supply a business analyst or project manager to take load off that person, but should not take over priority decisions.

How do you calculate the monthly cost step by step?

The calculation has three steps: the day rate of each role, the team’s daily total and the number of billable days per month. We use the rates from ARDURA Consulting’s pricing page, which publishes net ranges per 8-hour day, fully loaded: salary, taxes, insurance, equipment and management overhead, with no recruitment fees.

Step one: role rates. According to the rate card a senior backend developer costs €335–485 per day, a senior frontend developer €315–445, a senior QA engineer (test automation) €335–465, a senior DevOps engineer €370–520 and a backend architect or tech lead €485–650.

Step two: the daily total. A five-person product team (lead, two senior backend, one senior frontend, one senior QA) costs from €485 + 2 × €335 + €315 + €335 = €1,805 to €650 + 2 × €485 + €445 + €465 = €2,530 per day.

Step three: billable days. A calendar month usually has 20–22 working days, but only days actually worked are billed, without holidays and sick leave. The worked example on our pricing page assumes 108.5 billable days per person over six months, roughly 18 a month. We use that as the planning assumption. It gives a five-person team at about €32,500–45,500 per month. For a conservative scenario at 21 billable days, the range is €37,900–53,100.

Two caveats before this goes to the board. First, dedicated teams are priced as a monthly team rate with a volume discount, so the sum of individual rates is an upper bound, not the final price. Second, rates are locked for the duration of the engagement, so the monthly line in your budget does not move mid-year unless you change the composition.

What do the three typical configurations cost?

The same method applied to the three configurations above gives the ranges below. All amounts are net, calculated from the senior and lead rates on the rate card, at 18 billable days a month, before the team discount.

Configuration	Composition	Daily cost (EUR)	Monthly cost at 18 days (EUR)	Best for
Minimum, 3 people	Tech lead, senior backend, senior QA	1,155–1,600	approx. 20,800–28,800	One bounded module, an integration, continuing an existing product
Product, 5 people	Lead, 2 × senior backend, senior frontend, senior QA	1,805–2,530	approx. 32,500–45,500	A new web product, a large workstream in an existing system
Extended, 7 people	Product + senior DevOps + second senior frontend	2,490–3,495	approx. 44,800–62,900	Several interfaces, own infrastructure, frequent releases
Variant: mid-level instead of senior	E.g. one senior backend replaced by mid-level	approx. 95–150 less per day per role	approx. 1,700–2,700 less per role	When the lead has time to mentor and tasks are well specified

The last row uses the ranges on our staff augmentation page: mid-level engineers cost €240–335 per day, seniors €335–485. The saving is real only if the tech lead actually has time to guide a less experienced engineer. Otherwise you pay less per day and more per feature.

How should you read the table in a budget? The gap between the bottom and the top of the range for a five-person team is about €13,000 a month, more than €150,000 a year. It does not come from vendor whim but from who exactly you get: a senior with five years in a mainstream stack sits near the bottom, a senior with your industry background and a rarer technology near the top. Take both ends to the board and explain what decides where you land. A budget planned at the floor and invoiced at the ceiling is the fastest way to lose your CFO’s trust.

A second practical point: cost the whole horizon with a ramp, not just one month. If the team starts with three people, grows to five after two months and to seven from month six, the annual budget is clearly lower than twelve times the full team. That schedule is also closer to how ready-to-build work actually accumulates.

For a reference point outside nearshoring: freelancermap’s Freelancer-Kompass 2026 puts the median hourly rate of IT freelancers at €95. Five freelancers at that median, eight hours a day and 18 days a month, come to about €68,400 per month, and that buys five individual contracts, not a team with a lead, shared rituals and a vendor who replaces people when they leave. The table figures are a starting point for a conversation, not a quote: the final rate depends on technology stack, project complexity and engagement duration.

What else do you need to budget beyond the team’s rates?

The day rate covers the specialist and the vendor, not the costs on your side, and those are often underestimated. Put them on a separate budget line.

Your own people’s time. For a five-person team the product owner is realistically half to a full role: backlog refinement, acceptance, decisions, conversations with the business. Add an architect or the CTO for reviews of key decisions, especially in the first weeks. If that time does not exist, the team will consume it anyway, as waiting.

Tools and licences. Accounts in your repository, issue tracker and cloud environments, IDE and testing tool licences. In the worked example on our pricing page, tools and workspace on the client side come to about €5,400 for three seniors over six months. Yours may be more or less, but not zero.

Infrastructure for the team. Extra test environments, CI pipelines, test data. A new team that releases often needs environments that may not have existed before.

Onboarding. For the first two or three weeks the team learns the domain, the code and your processes. You pay full days and get partial output. That is normal and unavoidable, but plan your first milestone with it in mind. Good onboarding shortens it; we describe how in our remote IT specialist onboarding playbook.

The broader view of total cost, including hidden costs on the buyer’s side, is in our article on what IT outsourcing to Poland really costs in 2026. Apply the same logic to a dedicated team: compare the cost of delivered work, not the rate.

Which billing model fits a dedicated team?

Dedicated teams are usually billed in one of three ways: time and materials per person for days worked, a fixed monthly team rate, or a team subscription with defined capacity. Each splits risk between you and the vendor differently.

Time and materials is the simplest and most transparent: you pay for days worked at agreed rates, invoiced monthly. The risk that work takes longer sits with you, but you keep full scope flexibility. It is the default when the roadmap is alive.

A fixed monthly team rate simplifies budgeting and usually includes a discount for committing to the whole team. At ARDURA Consulting dedicated teams are priced exactly this way. Ask how holidays and absences are handled: does the rate include cover, or does it drop pro rata?

A capacity subscription means buying a set number of days or points per month and settling unused capacity under the contract’s rules. It works when demand fluctuates but you want to keep the same people.

Which of these actually moves risk to the vendor and which only appears to is broken down in our article on whether a team subscription, time and materials or fixed price really shares risk. For a dedicated team the rule is simple: the more volatile the scope, the less sense it makes to pretend there is a fixed price for an outcome.

When does a dedicated team pay off?

A dedicated team pays off when four conditions hold at once. Missing one does not rule the model out, but it should turn on an amber light.

The work lasts longer than a quarter. A cohesive team needs time to gel and learn the domain, which is why we recommend at least three months. The best value usually appears at six to twelve months and beyond: onboarding cost spreads over a long period, and the team builds product knowledge that stays in the unit instead of leaving with individuals.

You need a whole workstream, not single roles. If you are missing one DevOps engineer, buy a DevOps engineer. A dedicated team makes sense when you need the whole thing delivered: backend, interface, tests and release.

You lack the time or people to manage more individuals day to day. This is the most overlooked argument. Five people in staff augmentation are five people to whom you or your lead assign work, run stand-ups and clear blockers. A dedicated team with its own lead takes that coordination away. If your team lead is already overloaded, that difference is worth more than any rate discount.

You have a product owner. Self-organising does not mean directionless. Someone must decide what matters most and accept the results.

A well-built team also scales: when the roadmap grows, you add people to a cohesive unit instead of starting again. Our banking team case study describes that pattern, with specialists joining in several waves against a hard regulatory deadline.

When are staff augmentation, a project or direct hiring better?

A dedicated team is not the answer to every capacity problem. In four situations other models are cheaper or safer.

You are missing one or two skills. You have a strong team and need a specific capability, say Kubernetes or an SAP integration. IT staff augmentation gives fast access to that skill while you keep full control. The minimum is one specialist for one month.

The work is short and well defined. A migration, a tightly scoped MVP, a one-off integration. A fixed-price project moves estimation risk to the vendor and does not require you to build a months-long relationship with a team.

The role is stable for years. If you know you need the person for three years or more and the market lets you hire them, a permanent hire is usually cheaper per productive hour. In the example on our pricing page the break-even against a direct B2B contract is around nine months. We say so openly, because a vendor who claims an external team is always cheaper is calculating something different from you.

There is no product owner. Before you buy a team, hire or appoint the person who will direct it. Without that, every external model is expensive.

Models can be combined. A common, low-risk path is to start with one or two augmented specialists, validate the fit, and then grow the same group into a self-organising team.

How does a dedicated team compare with building one in-house?

An honest comparison has four components on the in-house side, and you need all of them before you set them against a vendor’s rate.

Full employer cost. Gross salary plus employer contributions, benefits, equipment and office. Western European employer costs are well above Polish ones, so run this with your own payroll data rather than ours.

Recruitment cost and time. In the worked example on our pricing page, recruitment calculated as 20% of annual salary comes to about €36,800 for three seniors, and the page gives an average time to hire of two to four months. For a five-person team time matters more than the fee: by the time you hire the fifth engineer, the first may be looking for a new job. Our article on staff augmentation vs direct hire total cost walks through the full comparison.

Exit cost. If the team is needed for a programme rather than forever, include notice periods and, in some jurisdictions, severance and consultation obligations. With a vendor team you pay only for days worked and end the contract with the agreed notice.

Management cost. An in-house team needs a lead, HR processes, career paths and reviews. With a dedicated team, the vendor does that work.

In the example on our pricing page, which uses Polish employment costs, a six-month project with three seniors costs about €177,200 in-house and about €132,600 through ARDURA Consulting, a difference of roughly 25%. That result applies to a six-month horizon. The longer the horizon and the more stable the roles, the more the advantage shifts towards hiring. A serious decision therefore contains both scenarios and a date on which to recalculate.

What do the first weeks of a dedicated team look like?

Starting a team has four stages, and you should know their length before promising the board a first milestone.

Agreeing composition and profiles, a few days. You describe the product, the stack, the way you work and what you expect from the lead. Together with the vendor you set the composition and seniority of each role. Write down which roles are key and cannot change without your consent.

Selecting and vetting candidates. At ARDURA Consulting the standard delivery process takes two weeks: requirements and shortlisting, technical interviews and skill verification, then contract and onboarding. Every candidate passes our 5-stage vetting process, and you interview and approve each one before the engagement starts. Teams usually start with the lead, with the others joining over the following days or weeks.

Onboarding, two to three weeks. Access, environments, an architecture walkthrough, first small tasks. The lead learns the domain fastest because they talk to your product owner.

Steady state, from month two. The team has a sprint rhythm, a shared definition of done and predictable throughput. Only from here does it make sense to measure performance against plan.

So plan the first milestone for the end of month two at the earliest. A vendor who promises full output from a five-person team in week one is promising something that cannot be delivered.

What should the dedicated team contract cover?

A team contract differs from a single-specialist contract because you protect the continuity of the team as a whole, not only the availability of people. Seven clauses matter most.

Composition and key roles. The list of roles, their seniority and the named key people, above all the lead. Changing a key person requires your consent, or at least notice and an overlap period.

Replacement and cover. What happens when someone is not the right fit or leaves. At ARDURA Consulting every engagement starts with a 2-week satisfaction guarantee: if the specialist does not meet your expectations within the first 2 weeks, we replace them at no cost, and if a specialist leaves during the engagement, we guarantee a replacement within 5 business days. Make sure terms like these are in the contract, not only on a website.

Scaling up and down. How much notice you give to add or remove people. Per our pricing page, you add specialists with 2 weeks notice and reduce the team with 30 days notice, with no penalties for scaling.

Billing model and rate. Team rate or role rates, how long they are fixed, and how holidays and absences are settled.

IP and code ownership. Assignment of intellectual property rights, and repositories on your side from day one.

Confidentiality and security. NDA, access rules, GDPR data processing terms.

Exit and knowledge transfer. What the team documents continuously and what it hands over at the end. This is the clause most often skipped and the most expensive when missing. If you are a regulated financial entity, the EU’s Digital Operational Resilience Act (DORA, Regulation 2022/2554) already requires ICT contracts to include service level descriptions, termination rights and, for critical functions, exit strategies with a transition period, so align the team contract with your DORA register.

What mistakes drive up the cost of a dedicated team?

Most money lost on dedicated teams is lost not on the rate but on six recurring mistakes.

A team without a product owner. Covered above, but it is mistake number one. A team that waits for a decision every other day costs the same as a team that works.

Starting too big. Seven people on day one, before there is a backlog for seven. Start with three or five and add people when work is waiting for them.

Churn inside the team. Every change of person means more weeks of onboarding. Ask the vendor about specialist retention and how it is measured. ARDURA Consulting’s specialist retention rate is 99%.

No shared definition of done. The team thinks a task is finished when the code is merged; you think it is finished when the feature runs in production with tests. The gap usually shows at the first major release.

Measuring attendance instead of outcomes. Timesheets tell you how much the team worked, not what it delivered. Agree a few measures from the start, for example lead time from request to release, defects after release and sprint predictability, and review them monthly with the lead.

Treating the team as a ticket queue. When the team only receives finished tasks without business context or a seat in planning, it stops thinking about the product. You lose the main advantage of the model, product knowledge accumulating in a stable unit. Invite the lead to roadmap reviews and user conversations; it costs a few hours a month and pays back in better technical decisions.

How do you choose a dedicated team vendor?

Ask six questions before you sign. The answers quickly separate vendors who build teams from vendors who sell a stack of CVs.

Who will lead the team, and can I speak to them before we start? The lead determines the quality of the whole team. That conversation matters more than reviewing five CVs.

How do you vet candidates, and do I approve each person? A good vendor has a documented technical vetting process and lets you run your own interview.

What happens when someone leaves? Ask for a concrete replacement time and handover rules, in the contract.

How does billing work? Team rate or role rates, what is included, how holidays are counted, whether any extra fees exist.

How do you measure the team’s quality of work? Look for specific measures and regular reviews, not promises of commitment.

How do we exit? Notice period, knowledge transfer, access to code and documentation. A vendor who will not discuss this before the start will not make it easy at the end.

Also notice what a vendor does not say. If the proposal has nothing on the team lead, on who owns the relationship on the vendor side or on how the engagement is reviewed, you are probably buying five separate contracts under one label. At ARDURA Consulting a dedicated account manager monitors the engagement and gathers feedback, so a fit problem is addressed before it turns into a replacement. Whatever vendor you choose, ask for that person’s name and the cadence of review meetings. More on the wider model is collected in our staff augmentation hub.

How should you make the decision and present it to the board?

Back to the CTO in Munich. She has an 18-month roadmap, three people and a lead with no time to manage five more contractors. It is a textbook case for a dedicated team: the work lasts more than a quarter, covers a whole stream from backend to mobile app, and the binding constraint is not money but coordination time.

She should go to the board with three numbers and one condition. The first number is the monthly team cost from day rates: for five people roughly €32,500–45,500 before the team discount. The second is the cost of building the same team in-house, including recruitment and the months it takes. The third is the cost of delaying the roadmap by a quarter if she does nothing. The condition is naming a product owner inside the company who will direct the team.

Remember five things. First, you buy a dedicated team to move coordination inside the team, not to get more people. Second, you can calculate the monthly cost yourself: each role’s rate times billable days, about 18 a month. Third, the model pays off for work longer than a quarter, covering a whole stream, with overloaded management. Fourth, for a single role staff augmentation is better, for a short scope a project, and for a stable role over years a permanent hire. Fifth, the contract must protect team continuity: composition, replacement, scaling and exit.

If you are facing this decision, compare both models on our staff augmentation vs dedicated team page, check the rates on our pricing page or book a call about team composition. We will cost your configuration and tell you plainly if it is better to start with two specialists than with a whole team.