Dedicated Development Teams

A dedicated team is a standing group of engineers that works only on your product, shaped around what your product actually needs rather than around a fixed package. You own the roadmap and the priorities. We own the people: recruiting them, employing them, covering them when someone is out, and keeping them on your product long enough to know it properly. Every team gets a CodigoDelSur project manager, included at no extra cost. CodigoDelSur has run teams like this from Montevideo, Uruguay since 2007, for companies in the United States and the rest of the world.
The difference from staff augmentation is one line: with augmentation you hire individual engineers into a team you already run, with a dedicated team we assemble and coordinate the whole group for you. There is no fixed team template. Teams include senior developers, and in practice the most senior person on the team makes the technical calls day to day. QA and design are roles you choose rather than defaults we assume.

Is a dedicated team the right model for you?

Yes, if:

  • You own a product or a product area and you do not have the people to run it.
  • The work is continuous, not a project with an end date. A squad is worth building when it will still be needed in a year.
  • You want one team accountable for delivery, coordinated on our side, instead of assembling and chasing four individuals yourself.
  • You have a product owner on your side who can make decisions every week.

No, if:

  • The gap is one or two engineers inside a team that already works. You would be paying for coordination you are already doing well.
  • Nobody on your side can set priorities weekly. A squad with no decision maker burns money faster than any other model.
  • You need a fixed scope delivered for a fixed price. That is a product build, quoted per project.

How it works, from first call to first release

Five steps, and we tell you at each one whether you are still in the right conversation.
Discovery call, 45 to 60 minutes. What the product is, what state it is in, what you need shipped in the next two quarters, and who on your side owns the decisions. If what you describe is a one person gap or a fixed scope project, we say so here and point you at the model that fits.
Written team proposal. The shape of the team, role by role, with the reasoning for each one: why a QA and not another developer, why one backend and two frontend. It includes what the team should have shipped by the end of month three. You push back on it before anything is signed, and most clients do.
We assemble the team. Some people come off our bench and some are recruited against the proposal, and we tell you which is which role by role, not as an average. For every candidate you get a named CV with the projects they have worked on and the experience behind them, and you can interview all of them. You can turn down anyone we propose without giving a reason.
Contract, setup and kickoff. One standard services agreement, signed once for the whole team. We do not require a master agreement plus a statement of work unless your procurement process asks for it. We handle equipment, accounts, background checks where required and payroll, and a CodigoDelSur project manager is assigned to your team. The whole team starts together, not staggered, and from day one it is in your standup, your board and your Slack.
Delivery rhythm. Sprint planning and demo with your product owner, a written weekly summary of what shipped and what is blocked, and a monthly review of the team itself: what to change in its shape, not only in its backlog.

How long it takes to stand up a team

Each person follows the same timings as hiring a single engineer. What is different about a team is that it is limited by its slowest role, so the question that actually sets your start date is how many of the roles are already on our bench. We tell you role by role, before you sign anything.

StageTypical time
Signed off team proposal to first CVs, for a role we can fill from our bench1 business day
Signed off team proposal to first CVs, for a role we have to recruit5 business days
Signed agreement to a person's first day5 business days as standard, or as soon as the next business day for someone already on our bench, if you are ready
First day to first merged pull request3 to 5 business days
Signed agreement to the whole team workingWithin a week if everyone is already on our bench, about a week longer for each role we still have to recruit

What a dedicated team looks like

There is no standard package. A team is built from the roles your product needs, and these three are the starting points we argue from most often. The proposal in step 2 makes the case for a specific shape for you.

Typical teamRoles it usually hasUsed for
Mobile product team2 iOS, 2 Android, product designer, QA optionalA consumer app shipping to both stores on the same cadence, with design in the loop
Platform team2 frontend, 2 backend, part time DevOps, QA optionalA web platform with a real backend: integrations, billing, dashboards, internal tools
Full product teamProduct designer, 2 mobile, 2 backend, QA optionalA product with no in house engineering behind it, from first release to steady state

Every team gets a CodigoDelSur project manager, and that role is free. They are assigned to your team but not full time on your product: they handle staffing, delivery coordination, escalation and the weekly summary, and they are your point of contact on our side when something needs to change. The cost is already inside the hourly rate of the people on your team, so there is no line for it in the proposal and no percentage on top.

Every team has senior developers, and the most senior person makes the technical calls day to day. QA is optional, and we recommend it in almost every case. It is not bundled into the team by default, because we would rather you decide it than find it in the invoice. What we will tell you is what happens without it: your product owner becomes the QA.

Teams scale in both directions during an engagement. Adding a person takes the same time as filling any role from the bench. Removing one takes two weeks of written notice, so you are not locked into a size that stopped making sense two quarters ago. A full time engineer on your team works for your product and nothing else. If you take someone part time, that person is assigned to a maximum of two projects.

What it costs and how billing works

Rates run from $50 to $99 per hour in US dollars, by role and seniority, and a team is billed as the sum of the people in it. Every role in the proposal is priced and visible, instead of a percentage buried in a rate. There is no platform fee, management fee or recruiting fee, and the project manager assigned to your team is not billed at all: that role is already inside the hourly rate of the people on the team.

Volume discounts apply to the whole team: 5 percent for teams of 5 people or more, and 10 percent for teams of 7 or more.

The minimum commitment is two weeks, one sprint. Not three months, not six, not a year. Most companies that sell dedicated teams ask you to commit for a quarter or more before you have seen anything ship, and that is a pricing decision dressed up as a delivery requirement. After the first sprint it runs continuously with two weeks of written notice on either side, and you can change the size of the squad inside the same agreement. If you would rather start with one or two engineers and grow into a squad, that is the staff augmentation model and it is a perfectly good way in.

Invoicing is per sprint, for hours worked, in dollars, and terms are Net 14. If your accounting team would rather receive one invoice a month, we bill monthly instead, on the same terms. Third party licences and cloud spend are yours. Travel to your office is billed at cost and only when you ask for it.

Three teams we have run

DroneDeploy, drone mapping and reality capture. A CodigoDelSur team worked on the flight side of the DroneDeploy platform: automated flights, pre flight and in flight safety checks, map data exploration and flight logs used for compliance, insurance and fleet maintenance, across iOS, Android and web with the DJI SDK. This is the kind of product where a squad pays for itself, because the domain takes months to learn and you do not want to relearn it every time someone rotates off. In July 2026 DroneDeploy was acquired by Procore for 845 million dollars. Read the DroneDeploy case study.

Grubhub, restaurant ordering and payments. From 2018 to 2022 a CodigoDelSur team built and maintained white label ordering apps that let individual restaurants launch their own branded app with ordering, payments, delivery and loyalty. More than 100 restaurant apps came out of that pipeline, across iOS, Android and backend, with Braintree for payments. A single engineer cannot hold a product line like that. A standing team with its own release process can. Read the Grubhub case study.

MoviePass, subscription and ticketing. Between July 2022 and December 2025 a CodigoDelSur squad covering iOS, Android and design worked on the MoviePass subscription platform: film discovery, theater search, showtimes, credits and subscription management, plus the beta release cycles. Three and a half years on one product, with design inside the team rather than handing specs over a wall. Read the MoviePass case study.

Dedicated team, staff augmentation or full-cycle product development

Three different products get sold under the same word, "outsourcing". They are not interchangeable and picking the wrong one is the most expensive mistake in this category.

Staff augmentationDedicated teamFull-cycle product development
Who owns the roadmapYouYouShared, we run discovery
Who manages day to dayYour engineering managerYou, with a CodigoDelSur project manager coordinating on our side at no extra costOur project manager
What you getIndividual engineers inside your teamA team shaped around your product, staffed and coordinated by usA product, from discovery to store release
You need to haveTechnical leadership with spare capacityA product owner and a clear roadmapA budget and a problem worth solving
Typical size1 to 4 people4 to 12 peopleScoped per project
Minimum commitmentTwo weeks, one sprintTwo weeks, one sprintQuoted per project
Best whenThe work is defined and you are short on handsYou own a product area and want it staffed and coordinated as one teamYou need the thing to exist and you do not have an engineering org

When a dedicated team is the wrong answer for you

Do not build a team to fill a two person gap. If the engineering team you already have works, adding two senior engineers on the staff augmentation model is faster, cheaper and less disruptive than standing up a separate group next to it. We will tell you that on the first call rather than in the proposal you are comparing against three others.

Do not build a team you cannot feed either. The failure mode of this model is not technical, it is a backlog that nobody prioritizes: five people waiting on decisions produce less than one engineer with a clear ticket, and it costs five times more. If your product owner has an hour a week, start smaller.

And if what you need is a defined thing built for a defined price, with one company accountable for the result, that is full-cycle product development, quoted per project. We do all three models, which is precisely why we have no incentive to sell you this one.

Where "taking over an existing project" and "short-term work" fit

Neither of those is a fourth model. They are situations, and both are handled inside the two models above. If you already have an application and you want to switch providers, we review the existing codebase and start working on top of it, either with engineers embedded in your team or with a dedicated team taking the product over. If the work is short, the two week minimum means you can run it as a single sprint with one or two people and stop there, without committing to anything longer. We spell this out because these are the two things buyers ask for by name, and neither of them changes how the engagement is structured or priced.

Frequently asked questions

What is the difference between a dedicated team and staff augmentation?

Assembly and coordination. In both models the engineers work only on your product and you own the roadmap. With staff augmentation you add individual engineers into a team you already run. With a dedicated team we build the group around what your product needs, staff every role in it, and assign a project manager on our side to coordinate it at no extra cost. Augmentation is usually the better answer for one to three people when your own team is working well. A dedicated team is the better answer when you own a product area and want the whole group staffed and run as a unit.

What time zone does the team work in, and how much overlap will I get?

Our teams work 10:00 to 19:00 Uruguay time, which is UTC minus 3. That covers the entire US East Coast working day, five to six hours of live overlap with the West Coast, and three to four hours with the United Kingdom, in their afternoon. The hours are set that way on purpose, to widen the West Coast overlap without pushing anyone into a night shift. This matters more for a team than for one engineer: sprint planning, demos and standups have to sit in normal working hours on both sides, because a team that meets at 7am or 9pm stops meeting by month three.

Can I interview the team, and can I choose who is on it?

Yes, all of them. You get a named CV for every candidate, with the projects they have worked on and the experience behind them, and you can interview each one with your own process. We propose the shape of the team and argue for it, and you can turn down anyone we put forward without giving a reason. What we ask in return is that you tell us early rather than in month two.

What happens if someone on the team is not working out, or leaves?

We replace the person at our cost and the squad keeps delivering. There is no charge for the search and no penalty for asking. The outgoing and incoming engineers overlap for ten business days, and those ten days are not billed: during the handover you keep paying exactly what you were paying before. Context transfers inside the team instead of landing on you. This is the structural advantage of a dedicated team over hiring directly: the person leaving is our retention problem, and the rest of the team, which already knows your codebase, keeps delivering while we solve it.

Who owns the code and the intellectual property?

You do, exclusively. Source code, application logic, APIs, integrations, data models, configurations, UI and UX designs, documentation and derivative works are assigned to you with full title guarantee, as they are created, not conditional on final payment. We warrant that what we deliver does not infringe any third party's intellectual property. For our own pre existing components that were not built specifically for you, you get a non exclusive, irrevocable, royalty free licence to use, copy and modify them, so nothing the team brings with it can be used to lock you in later. Every CodigoDelSur employee signs a non disclosure agreement and an intellectual property assignment as a condition of employment, and the team works inside your repositories and your cloud accounts, so in most engagements the code never lives anywhere else.

What is the minimum commitment and how do I end it?

Two weeks, one sprint, under a single standard services agreement. We do not layer a master agreement plus a statement of work on top of that unless your procurement team requires it, and if they do, we sign it. After the first sprint the engagement runs continuously with two weeks of written notice on either side to reduce the squad or end it, and the agreement gives you the right to terminate for convenience, without cause, on fourteen days written notice. There is no annual lock in and no termination fee, and you can change the size of the team inside the same agreement without renegotiating it.

Who does the technical onboarding, and what do I have to do?

Your team owns product and codebase onboarding, and our project manager coordinates everything around it. What we need from you is access and one person who knows the product. Week one is codebase, domain and accounts, run with whoever on your side has the context. Everything else is on us: equipment, accounts, background checks (where required), payroll, time off coverage and performance management. Your ongoing commitment after that is a product owner in sprint planning and the demo, and someone who can unblock decisions during the week. If you cannot commit that, this is not the right model, and it is better to find that out now.

How much does a dedicated team cost?

Each person is billed between $50 and $99 per hour in US dollars, by role and seniority, and the team costs the sum of the people in it. Every role is priced and visible in the proposal, there is no management fee or platform fee on top, and the project manager assigned to your team is free: that role is already inside the hourly rate. Teams of 5 people or more get a 5 percent discount, and teams of 7 or more get 10 percent. The minimum commitment is two weeks, one sprint, so you can see a team ship before committing to a quarter of it. Invoicing is per sprint, Net 14, or monthly if that suits your accounting team better.

Talk to us about a team

Tell us what the product is and what you need shipped in the next two quarters, and we will come back with a proposed team, role by role, with the reasoning for each one and what it should have delivered by month three. If a smaller engagement is the honest answer, that is what you will get instead.

CodigoDelSur has been building software from Montevideo, Uruguay since 2007. More than 250 clients, more than 300 applications shipped, products used by more than 300 million people. Get in touch, or see the full portfolio.