Software Outsourcing Glossary

Plain-language definitions for the core software outsourcing and nearshoring terms — engagement models, contract terms, and Serbia/timezone-specific terms.

Reviewed by Igor Gazivoda, Founder & CEO · Updated July 2026

What This Glossary Covers

This glossary defines the core terms used across the software outsourcing and nearshoring industry: engagement models like staff augmentation and dedicated teams, contract terms like notice periods and time & materials vs. fixed price, and region-specific terms like CET timezone overlap and IP Box. It's published by StepTo, a Belgrade, Serbia-based software company that has run nearshore engineering teams since 2014 with a 15-20-person team at $25-85/hr — but the definitions themselves describe how each term is used industry-wide, not just at StepTo.

Each definition is written to stand on its own, regardless of which provider or region you're evaluating. A handful of entries — marked with a separate "StepTo:" note — add how the term specifically applies to StepTo's own model; the definitions above those notes are general and vendor-neutral. Generic delivery terms like Agile, Sprint, and MVP aren't specific to any company at all, so they carry no such note.

Jump to a section

Engagement Models Contracts, Delivery & Process Serbia & Timezone Terms

Engagement Models

The different ways an outsourcing provider structures who does the work and who manages it — from a fully outsourced project to individual engineers embedded in your own team.

Dedicated Development Team

A model where a provider assembles a self-contained team — typically several engineers, plus on larger engagements a project or delivery lead — who work exclusively on one client's project for the length of the engagement. The team integrates with the client's existing tools and processes but carries more day-to-day autonomy than staff augmentation, and less ongoing client-side management overhead than a fully outsourced project. It sits between staff augmentation (individual engineers who join a client's own team directly) and full project outsourcing (the vendor manages the entire engagement, including planning).

StepTo: This is StepTo's core engagement model. StepTo's dedicated teams are direct-hire (see Direct-Hire Model vs. Bench Model below) and have run this way from Belgrade since 2014.

Direct-Hire Model vs. Bench Model

In a direct-hire model, the provider employs each engineer directly — payroll, benefits, legal employment — and assigns them full-time to one client for the length of the engagement. In a bench model, the provider maintains a pool of contractors or subcontracts through additional layers, assembling the actual delivery team only after a contract is signed, meaning the specific people doing the work may not be confirmed, or may be rotated, until later. Direct-hire generally means more continuity and clearer accountability, since the engineer isn't splitting time across other clients.

StepTo: StepTo uses a direct-hire model exclusively — engineers are StepTo employees assigned by name, not pulled from a shared bench.

IT Outstaffing

Functionally the same model as staff augmentation: a provider employs and pays engineers who work full-time embedded in a client's own team, under the client's management and processes, rather than under the provider's own project management. "Outstaffing" is the term used more often in Europe — particularly Eastern Europe — while "staff augmentation" is the more common US term for the identical relationship (see Staff Augmentation below for the full definition).

Managed Team

A team recruited and administered by an outsourcing provider — covering hiring, payroll, equipment, and typically a delivery or account manager — that works on a client's project as a cohesive unit rather than as individually sourced freelancers. The term overlaps heavily with Dedicated Development Team above; it's most often used to draw a contrast with marketplace platforms that match individual contractors without a provider managing the team as a whole.

Nearshoring

Outsourcing software development to a provider in a geographically close country — typically one in the same or an overlapping timezone — rather than a distant one (see Offshoring below). For US companies, nearshoring usually means Latin America; for Western European companies, it usually means Eastern Europe, including Serbia, Poland, Romania, Bulgaria, and Ukraine, all of which sit in or near the CET timezone. The tradeoff nearshoring optimizes for is real-time collaboration, sometimes at a higher rate than farther offshore alternatives.

StepTo: StepTo operates as a nearshore provider for European and US clients, based in Belgrade, Serbia (CET).

Offshoring

Outsourcing software development to a provider in a distant country, typically with limited timezone overlap with the client, chosen primarily to minimize hourly cost rather than to maximize real-time collaboration. Common offshoring destinations for US and Western European companies include India, Vietnam, and the Philippines. The tradeoff is the inverse of nearshoring: potentially lower rates, at the cost of communication that's largely asynchronous — often 0-3 hours of working-day overlap.

Outsourcing

The umbrella term for hiring an external company to perform software development work that could otherwise be staffed internally. It covers several distinct models with different levels of client control: project outsourcing (the vendor manages and delivers a defined scope end-to-end), staff augmentation/outstaffing (the vendor supplies individual engineers who work under the client's own management), and dedicated teams (a self-contained unit assigned to one client). "Nearshoring" and "offshoring" describe where the outsourcing happens geographically, not which of these models is used.

Staff Augmentation

An engagement model where a provider supplies individual engineers who join a client's existing team and report into the client's own management, tools, and sprint process, while the provider handles employment, payroll, and (where applicable) local tax and labor compliance. It differs from a dedicated team, which operates with its own internal management, and from project outsourcing, where the vendor manages delivery of a defined scope rather than just supplying headcount.

StepTo: StepTo offers staff augmentation as one of its core service lines, with a 3-month minimum engagement, a 30-day notice period, and a 30-day replacement guarantee.

Contracts, Delivery & Process

Terms that show up in the contract itself and in how the work actually gets planned and delivered, regardless of which engagement model you choose.

Agile

An iterative approach to software development that breaks work into short cycles with continuous feedback and re-prioritization, rather than committing to a single fixed plan upfront. Agile principles prioritize working software, ongoing customer collaboration, and adapting to changing requirements over rigid, front-loaded planning. It's the dominant methodology across the outsourcing industry today, usually implemented through a specific framework such as Scrum or Kanban.

MVP (Minimum Viable Product)

The smallest version of a product that includes enough functionality to be usable by real customers and to test a specific hypothesis, rather than building every planned feature before any release. The goal is validating real demand and gathering genuine usage feedback before committing further engineering investment — a general product-development concept, not specific to any single vendor or industry.

Notice Period

The amount of advance written notice a client must give a provider (or vice versa) before ending or scaling down an engagement — for example, reducing headcount on a staff augmentation contract. A clearly defined notice period, stated in the contract rather than agreed verbally, is one of the more commonly overlooked terms when evaluating a provider, and its absence is a recognized red flag.

StepTo: StepTo's standard terms are a 3-month minimum engagement and a 30-day notice period to scale down, with a 30-day replacement guarantee if an assigned engineer isn't the right fit.

Scrum

The most widely used framework for implementing Agile, organizing work into fixed-length iterations called sprints (commonly one or two weeks), with defined roles — product owner, Scrum master, development team — and recurring ceremonies: sprint planning, daily standup, sprint review, and retrospective. Not every Agile team uses Scrum specifically (Kanban is a common alternative), but it's the default framework across most of the software outsourcing industry.

Sprint

A fixed, time-boxed period — typically one to two weeks — during which a development team commits to completing a defined set of work, then reviews the outcome before planning the next one. Sprints are the basic planning and delivery unit in Scrum, used to keep progress visible and regularly reviewed rather than tracked against a single distant deadline.

Tech Stack

The complete set of programming languages, frameworks, libraries, databases, and infrastructure tools used to build and run a piece of software — for example, "React, Node.js, PostgreSQL, and AWS." When evaluating an outsourcing provider, genuine hands-on experience with the specific technologies a project requires is one of the more concrete, verifiable criteria available, as opposed to generic claims of broad technical capability.

Time & Materials (T&M) vs. Fixed Price

Two dominant billing models for software contracts. Fixed price sets one agreed total cost for a defined scope, which shifts the risk of scope-estimation errors onto the vendor — a vendor protecting thin margins may respond by cutting corners or billing anything not explicitly specified as a costly change order. Time & materials (T&M) bills for actual hours or resources used, shifting the risk of scope creep onto the client, but accommodates evolving requirements honestly since there's no fixed scope being protected. Many providers use a hybrid instead: phased engagements with milestone-based payment gates, combining T&M's flexibility within each phase with fixed-price-style accountability at each gate.

Serbia & Timezone Terms

Two terms that come up specifically when evaluating Serbia — or the wider CET timezone region — as a nearshore location.

CET (Central European Time) / Timezone Overlap

CET (UTC+1, UTC+2 during daylight saving) is the timezone used across most of continental Europe, including Serbia and Poland, closely adjacent to the CET+1/EET zone covering Romania, Bulgaria, and Ukraine. "Timezone overlap" measures how many working hours a remote team shares with a client's own business hours: full-day overlap with Western Europe, and roughly 6+ hours with the US East Coast (less with the US West Coast). More overlap enables real-time collaboration — standups, pairing, same-day answers — while offshore regions with 0-3 hours of overlap push most communication to asynchronous handoffs.

StepTo: StepTo's engineers work CET business hours from Belgrade, Serbia.

IP Box

A reduced corporate tax regime, offered by several countries including Serbia and Poland, that applies a lower effective tax rate to profit derived from qualifying intellectual property — such as copyrighted software — rather than the standard corporate rate. Serbia's regime taxes qualifying IP income at an effective rate as low as 3%, alongside a separate double R&D expense deduction. It's a country-level tax policy rather than something an individual vendor offers, but it can factor into a provider's cost base and long-term pricing stability.

StepTo: As a Belgrade-based company, StepTo operates under Serbia's IP Box regime.