Skip to content
COGNIVISE
Hiring and teams

How to hire a dedicated development team

There are three ways to add engineering capacity, and they are not interchangeable. This is how to work out which one you actually need, and what to ask before you commit.

Published Updated 5 min readView as Markdown
On this page · 10 sections
  1. 01What is a dedicated development team?
  2. 02Dedicated team, contractor or permanent hire: how they compare
  3. 03How do you hire a dedicated development team, step by step?
  4. 04What a dedicated team costs, and what the quote leaves out
  5. 05UK points to check
  6. 06Questions worth asking any supplier
  7. 07How to tell it is working
  8. 08When a dedicated team is the wrong answer
  9. 09Next step
  10. 10Frequently asked questions

What is a dedicated development team?

A dedicated development team is a group of engineers who work on your project through a supplier rather than on your payroll. They are not shared across other clients, and they normally include the roles a project needs rather than developers alone: designers, QA and DevOps as well.

The important part is not the label. It is that the supplier carries the hiring, the contracts, the replacement risk and the equipment, and you direct the work. If a supplier is offering you a "dedicated team" but rotating people between clients, it is staff augmentation with a better name.

Dedicated team, contractor or permanent hire: how they compare

Most companies arrive asking for one of these and need a different one. The difference that matters is how long the need lasts and who carries the risk.

One or two contractorsDedicated teamPermanent hire
Best whenA narrow, well-defined skills gapA plan that will run for quarters, with too few peopleThe role is indefinite and the knowledge should stay in your company
Speed to startFastestSlower than one contractor, faster than hiringSlowest: notice periods and recruitment
Who carries hiring and replacement riskYou or an agencyThe supplierYou
Easiest to stopYesWithin the notice period in the contractNo
Cost shapeDay ratePer person, per month or per daySalary plus employer costs

How do you hire a dedicated development team, step by step?

  1. Define what you need — The roles, the skills and roughly how long the work will run.
  2. Check that a dedicated team is the right model — Use the comparison above to rule out a contractor or a permanent hire.
  3. Shortlist suppliers and ask the questions below — Who is on the team, who owns the code and who you talk to when something is wrong.
  4. Read the contract points — Notice period, handover of work in progress, ownership of the code from day one, and UK GDPR where personal data is involved.
  5. Start with a small first piece of work — It tests how the team communicates before you commit to more. Agree what "done" means first.
  6. Review at set intervals — Agree in advance how the team can grow, shrink or stop.

What a dedicated team costs, and what the quote leaves out

Suppliers usually price a dedicated team per person, per month or per day. The total depends on the size of the team, how senior the people are and how long you commit.

Comparing suppliers on rate alone is how companies end up paying twice. The costs that do not appear on the quote are the ones that decide whether the engagement works.

  • Onboarding. A team that needs six weeks to become useful is more expensive than a team on a higher rate that needs two. Ask how the supplier plans to get people productive, and who on their side carries that.
  • Continuity. If the people who learned your system leave the account after three months, you pay the onboarding cost again. Ask what their turnover on a typical engagement looks like, and what happens contractually when someone is replaced.
  • Overlap. Distributed teams work well when enough of the day is shared to make decisions in. Four hours of overlap is usually workable. One is not.

UK points to check

  • Contract and notice. Agree the notice period, how work in progress is handed back, and that you own the code from the first day.
  • Personal data. If the team will handle personal data, ask where it is stored and who can access it, and make sure the contract covers UK GDPR.
  • Time zone. A team in the UK, or one that overlaps with UK hours, makes the four-hour overlap above easy to meet.

Questions worth asking any supplier

Who exactly is on the team?
Names, seniority and what else they are working on. If you cannot find that out before signing, you will not find it out afterwards.
Who owns the code?
It should be you, by default, in your own repositories and accounts, not handed over at the end of the contract as a deliverable you have to ask for.
What happens if this does not work?
Notice period, how work in progress is handed back, and whether the documentation to run it without them is part of the work or an extra.
Who do I talk to when something is wrong?
An engineer on the team, or an account manager relaying messages. The difference shows up in the first bad week.

How to tell it is working

Set this before the team starts, not after the first disagreement. The useful signals are boring ones: work reaching your users at a steady rate, the team asking questions that show they understand the business rather than just the ticket, and problems surfacing early instead of at the deadline.

Agree what "done" means for the first piece of work and who is responsible for deciding it. Most engagements that fail did not fail on capability. They failed because nobody wrote down what success looked like.

When a dedicated team is the wrong answer

If you do not yet know what you are building, a team will build the wrong thing efficiently. Planning first is cheaper: a few weeks of working out what is worth building often saves months of the wrong build.

If the work is a short, well-bounded task, one specialist will do it with less overhead. And if the knowledge genuinely needs to stay in your company for years, hire. It takes longer, so start now.

Still choosing between hiring, an agency and a dedicated team? In-house, agency or dedicated team: how to decide compares the three.

Next step

If you are weighing up a dedicated team, our dedicated development teams page explains how we set one up, and you can contact us to talk it through. If you are not yet sure which model fits, planning and technical advice is a short way to decide first.

Frequently asked questions

What is a dedicated development team?

A group of engineers, usually with design, QA and DevOps, who work only on your project through a supplier while you direct the work.

How is it different from staff augmentation?

Augmentation adds individuals to your team. A dedicated team is a group the supplier assembles and stays accountable for. See staff augmentation vs outsourcing.

How do I know it is working?

Look for steady delivery to your users, questions that show the team understands the business, and problems raised early. Agree what "done" means before the first piece of work starts.

What do dedicated team services usually include?

A group of engineers, often with design, QA and DevOps, assembled and managed by the supplier. The supplier carries the hiring, contracts, replacement risk and equipment, and you direct the work. Ask who is on the team and who owns the code before you sign.

Is a dedicated engineering team the same as a dedicated development team?

The label varies between suppliers. What matters is the same in both cases: the people are not shared with other clients, the roles match what the project needs, and the contract says you own the code from the first day.

More from the blog

Next step

Tell us what you are trying to build

Tell us what you need built, or who you need to build it, and we'll tell you plainly if we're the right people.