---
title: "What is Staff Augmentation?"
canonical: https://wavect.io/glossary/staff-augmentation/
language: en
description: "You hire external engineers into your own team, under your management, on your roadmap. The vendor supplies people; you supply direction."
image: "https://wavect.io/img/general/bak/open_graph_preview.jpg"
---

ENGAGEMENT

# Staff Augmentation

You hire external engineers into your own team, under your management, on your roadmap. The vendor supplies people; you supply direction.

Last reviewed: 2026-06-02 by [Kevin Riedl](/team/kevin-riedl/) [wiki ↗](https://www.wikidata.org/wiki/Q139796365)

Staff augmentation adds external engineers to your existing team. They report into your standups, work your backlog, and follow your processes. You keep the management, the architecture decisions, and the accountability. The vendor supplies bodies and bills for time. That is the whole model.

It fits when you have a working team and a working plan, and you simply need more hands at the keyboard for a known stretch of work. It is almost always billed [time-and-material](/glossary/time-and-material/), so the delivery risk sits with you. It does not fit when you do not yet know what to build, when nobody internal can direct the new engineers, or when you need someone to own an outcome rather than execute a ticket. For ownership you want a [dedicated team](/glossary/dedicated-team/) or a fractional senior role, not augmentation.

The seniority trap is the part nobody puts in the brochure. Most augmentation shops advertise senior profiles and staff you with juniors who need the same hand-holding your own juniors would, except now you are paying agency rates for the privilege. You carry the management overhead and the vendor carries none of the delivery risk. Read the named CVs, interview the actual person, and put a swap clause in the contract.

There is an Austrian legal wrinkle worth flagging: staff augmentation can shade into Arbeitskräfteüberlassung (labour leasing), which is a regulated arrangement with its own obligations around who directs the worker and how they are treated. If an “augmented” engineer is fully embedded under your direction for an extended period, the relationship may legally look more like leased labour than a service contract, with consequences for both sides. It is rarely a problem for short, well-scoped engagements, but it is worth getting the contract shape right rather than discovering the classification during an audit.

Wavect does not run a body shop. We are senior-only operators, so when we sit inside your team it is the person on the [software development](/services/software-development/) page doing the work, not a name on a roster who gets quietly substituted in week three.

**When this matters in a software project.** When you already have a working team and a working plan and simply need more hands for a known stretch. You keep the management, the architecture, and the accountability; the vendor supplies people.

**What founders usually get wrong.** They buy advertised senior profiles and get juniors who need the same hand-holding their own juniors would, except at agency rates, and the vendor carries no delivery risk. They also reach for augmentation when nobody internal can actually direct the new engineers.

**How Wavect handles it.** We staff senior-only, no quiet week-three substitution. If you need an outcome owned rather than tickets executed, we say so. The guides on [choosing a software agency](/software-development-guide/how-to-choose-a-software-agency/) and [freelancer vs agency vs in-house](/software-development-guide/freelancer-vs-agency-vs-in-house/) help you pick the right model.

// FAQ

## FAQs

### Staff augmentation vs a dedicated team?

Augmentation plugs people into your team and your management; you own the outcome. A dedicated team owns a workstream end to end with its own lead; the vendor owns the outcome. Pick augmentation when you have the management capacity and a clear plan, and a dedicated team when you want to hand off a whole problem.

### How is staff augmentation billed?

Almost always time-and-material: a day rate or monthly rate per engineer, billed for time spent, not outcomes delivered. The risk sits with you, because you direct the work. That is fine when you have the management bandwidth to keep the people productive, and expensive when you do not.

### When is staff augmentation the wrong model?

When you cannot direct the new engineers yourself, when you need an outcome owned rather than tickets executed, or when the vendor staffs juniors against senior rates. If your own team is already stretched thin on management, adding augmented headcount usually makes the bottleneck worse, not better.

Related terms

- [Dedicated Team](/glossary/dedicated-team/)
- [Time & Material](/glossary/time-and-material/)
- [Retainer](/glossary/retainer/)
- [Nearshoring](/glossary/nearshoring/)

Related services

- [Custom Software Development](/services/software-development/)

Related case studies

- [Bond Analytics Platform](/case-studies/bond-analytics/)

Related comparisons

- [wavect-vs-toptal](/compare/wavect-vs-toptal/)
- [wavect-vs-andela](/compare/wavect-vs-andela/)
- [wavect-vs-turing](/compare/wavect-vs-turing/)
- [wavect-vs-staffing-agencies](/compare/wavect-vs-staffing-agencies/)

Talk to us

## Structured Data

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@id": "https://wavect.io/#organization",
      "@type": [
        "Organization",
        "ProfessionalService",
        "LocalBusiness"
      ],
      "employee": [
        {
          "@id": "https://wavect.io/team/kevin-riedl/#person",
          "@type": "Person",
          "jobTitle": "Managing Director",
          "name": "Kevin Riedl",
          "url": "https://wavect.io/team/kevin-riedl/",
          "worksFor": {
            "@id": "https://wavect.io/#organization",
            "@type": [
              "Organization",
              "ProfessionalService",
              "LocalBusiness"
            ]
          }
        },
        {
          "@id": "https://wavect.io/team/christof-jori/#person",
          "@type": "Person",
          "jobTitle": "Managing Director",
          "name": "Christof Jori",
          "url": "https://wavect.io/team/christof-jori/",
          "worksFor": {
            "@id": "https://wavect.io/#organization",
            "@type": [
              "Organization",
              "ProfessionalService",
              "LocalBusiness"
            ]
          }
        }
      ],
      "founder": [
        {
          "@id": "https://wavect.io/team/kevin-riedl/#person",
          "@type": "Person",
          "jobTitle": "Managing Director",
          "name": "Kevin Riedl",
          "url": "https://wavect.io/team/kevin-riedl/",
          "worksFor": {
            "@id": "https://wavect.io/#organization",
            "@type": [
              "Organization",
              "ProfessionalService",
              "LocalBusiness"
            ]
          }
        },
        {
          "@id": "https://wavect.io/team/christof-jori/#person",
          "@type": "Person",
          "jobTitle": "Managing Director",
          "name": "Christof Jori",
          "url": "https://wavect.io/team/christof-jori/",
          "worksFor": {
            "@id": "https://wavect.io/#organization",
            "@type": [
              "Organization",
              "ProfessionalService",
              "LocalBusiness"
            ]
          }
        }
      ],
      "legalRepresentative": [
        {
          "@id": "https://wavect.io/team/kevin-riedl/#person",
          "@type": "Person",
          "jobTitle": "Managing Director",
          "name": "Kevin Riedl",
          "url": "https://wavect.io/team/kevin-riedl/",
          "worksFor": {
            "@id": "https://wavect.io/#organization",
            "@type": [
              "Organization",
              "ProfessionalService",
              "LocalBusiness"
            ]
          }
        },
        {
          "@id": "https://wavect.io/team/christof-jori/#person",
          "@type": "Person",
          "jobTitle": "Managing Director",
          "name": "Christof Jori",
          "url": "https://wavect.io/team/christof-jori/",
          "worksFor": {
            "@id": "https://wavect.io/#organization",
            "@type": [
              "Organization",
              "ProfessionalService",
              "LocalBusiness"
            ]
          }
        }
      ],
      "name": "Wavect GmbH",
      "subjectOf": {
        "@id": "https://wavect.io/verified-claims.json#dataset",
        "@type": "Dataset",
        "creator": {
          "@id": "https://wavect.io/#organization",
          "@type": [
            "Organization",
            "ProfessionalService",
            "LocalBusiness"
          ]
        },
        "description": "A machine-readable registry of quantitative and qualitative claims published by Wavect, with review dates, localized page appearances and public third-party citations where available.",
        "inLanguage": "en",
        "isAccessibleForFree": true,
        "license": "https://creativecommons.org/licenses/by/4.0/",
        "name": "Wavect verified publication claims",
        "url": "https://wavect.io/verified-claims.json"
      },
      "url": "https://wavect.io/"
    },
    {
      "@id": "https://wavect.io/team/kevin-riedl/#person",
      "@type": "Person",
      "jobTitle": "Managing Director",
      "name": "Kevin Riedl",
      "sameAs": [
        "https://www.wikidata.org/wiki/Q139796365",
        "https://www.linkedin.com/in/wsdt",
        "https://github.com/wsdt"
      ],
      "url": "https://wavect.io/team/kevin-riedl/",
      "worksFor": {
        "@id": "https://wavect.io/#organization",
        "@type": [
          "Organization",
          "ProfessionalService",
          "LocalBusiness"
        ]
      }
    },
    {
      "@id": "https://wavect.io/team/christof-jori/#person",
      "@type": "Person",
      "jobTitle": "Managing Director",
      "name": "Christof Jori",
      "sameAs": [
        "https://www.wikidata.org/wiki/Q139796367",
        "https://www.linkedin.com/in/jocr77/",
        "https://github.com/jo-chris"
      ],
      "url": "https://wavect.io/team/christof-jori/",
      "worksFor": {
        "@id": "https://wavect.io/#organization",
        "@type": [
          "Organization",
          "ProfessionalService",
          "LocalBusiness"
        ]
      }
    },
    {
      "@id": "https://wavect.io/#website",
      "@type": "WebSite",
      "inLanguage": [
        "en",
        "de",
        "es",
        "zh"
      ],
      "name": "Wavect",
      "potentialAction": {
        "@type": "SearchAction",
        "query-input": "required name=search_term_string",
        "target": {
          "@type": "EntryPoint",
          "urlTemplate": "https://wavect.io/search/?q={search_term_string}"
        }
      },
      "publisher": {
        "@id": "https://wavect.io/#organization",
        "@type": [
          "Organization",
          "ProfessionalService",
          "LocalBusiness"
        ]
      },
      "url": "https://wavect.io/"
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@id": "https://wavect.io/glossary/staff-augmentation/#term",
      "@type": "DefinedTerm",
      "alternateName": [],
      "description": "You hire external engineers into your own team, under your management, on your roadmap. The vendor supplies people; you supply direction.",
      "inDefinedTermSet": "https://wavect.io/glossary/#termset",
      "name": "Staff Augmentation",
      "termCode": "staff-augmentation",
      "url": "https://wavect.io/glossary/staff-augmentation/"
    },
    {
      "@id": "https://wavect.io/glossary/staff-augmentation/#webpage",
      "@type": "WebPage",
      "about": {
        "@id": "https://wavect.io/#organization",
        "@type": [
          "Organization",
          "ProfessionalService",
          "LocalBusiness"
        ]
      },
      "author": {
        "@id": "https://wavect.io/team/kevin-riedl/#person",
        "@type": "Person",
        "name": "Kevin Riedl",
        "url": "https://wavect.io/team/kevin-riedl/"
      },
      "dateModified": "2026-06-02",
      "description": "You hire external engineers into your own team, under your management, on your roadmap. The vendor supplies people; you supply direction.",
      "headline": "Staff Augmentation",
      "inLanguage": "en",
      "isPartOf": {
        "@id": "https://wavect.io/#website",
        "@type": "WebSite"
      },
      "lastReviewed": "2026-06-02",
      "mainEntity": {
        "@id": "https://wavect.io/glossary/staff-augmentation/#term"
      },
      "mentions": [
        {
          "@id": "https://wavect.io/#organization",
          "@type": [
            "Organization",
            "ProfessionalService",
            "LocalBusiness"
          ]
        },
        {
          "@type": "Service",
          "name": "Custom Software Development",
          "url": "https://wavect.io/services/software-development/"
        }
      ],
      "name": "Staff Augmentation",
      "reviewedBy": {
        "@id": "https://wavect.io/team/christof-jori/#person",
        "@type": "Person",
        "name": "Christof Jori",
        "url": "https://wavect.io/team/christof-jori/"
      },
      "speakable": {
        "@type": "SpeakableSpecification",
        "cssSelector": [
          ".gls-single__h1",
          ".gls-single__tldr"
        ]
      },
      "url": "https://wavect.io/glossary/staff-augmentation/"
    },
    {
      "@type": "BreadcrumbList",
      "itemListElement": [
        {
          "@type": "ListItem",
          "item": "https://wavect.io/",
          "name": "Home",
          "position": 1
        },
        {
          "@type": "ListItem",
          "item": "https://wavect.io/glossary/",
          "name": "Tech, product & engagement glossary",
          "position": 2
        },
        {
          "@type": "ListItem",
          "item": "https://wavect.io/glossary/staff-augmentation/",
          "name": "Staff Augmentation",
          "position": 3
        }
      ]
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Augmentation plugs people into your team and your management; you own the outcome. A dedicated team owns a workstream end to end with its own lead; the vendor owns the outcome. Pick augmentation when you have the management capacity and a clear plan, and a dedicated team when you want to hand off a whole problem."
      },
      "name": "Staff augmentation vs a dedicated team?"
    },
    {
      "@type": "Question",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Almost always time-and-material: a day rate or monthly rate per engineer, billed for time spent, not outcomes delivered. The risk sits with you, because you direct the work. That is fine when you have the management bandwidth to keep the people productive, and expensive when you do not."
      },
      "name": "How is staff augmentation billed?"
    },
    {
      "@type": "Question",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "When you cannot direct the new engineers yourself, when you need an outcome owned rather than tickets executed, or when the vendor staffs juniors against senior rates. If your own team is already stretched thin on management, adding augmented headcount usually makes the bottleneck worse, not better."
      },
      "name": "When is staff augmentation the wrong model?"
    }
  ],
  "speakable": {
    "@type": "SpeakableSpecification",
    "cssSelector": [
      ".faq-question",
      ".faq-answer"
    ]
  }
}
```