The CFO of a mid-sized European industrial group with eleven subsidiaries in six countries is looking at three proposals. The first, from a large BPO provider, offers to take over accounts payable, payroll and order-to-cash with a promised 20% cost reduction. The second, from a consulting firm, proposes a group shared service centre in a lower-cost EU location. The third comes from the group CIO, who wants an external development team to replace the order management system that every subsidiary has customised differently. The board asks which option to pick. The question itself is the problem.

BPO, shared service centres and IT outsourcing tend to land in the same folder, labelled “move it outside”, and are compared as if they were three versions of one decision. They are not. They answer three different questions: who should run a repeatable process, who should own that process across the group, and who should change the systems the process runs on. This article is for COOs, CFOs and the people who prepare their board papers, and it explains what BPO and shared services actually are, how they differ from IT outsourcing, and how to choose.

Our position is this: you can hand over a process, but you should keep the knowledge of your systems and the decisions about changing them. The most expensive mistake we see in these decisions is bundling process execution and software development into one contract. A provider paid per transaction has no reason to keep the system easy to change or easy to hand over. Many buyers see “process plus technology” as a convenient package. We see it as convenience you pay for the first time you try to switch providers.

What is BPO and what does a company actually buy?

BPO, or business process outsourcing, is the transfer of an entire business process to an external provider. Classic examples are accounts payable (from invoice receipt to payment), payroll, customer contact, collections, order processing, master data management and, in banking and insurance, application or claims handling. Gartner, as quoted in many industry sources, defines BPO as the delegation of one or more IT-intensive business processes to an external provider that in turn owns, administers and manages the selected processes based on defined and measurable performance metrics. There is also an international standard for providers, ISO/IEC 30105, which describes lifecycle processes for IT-enabled BPO services.

The key words in that definition are “measurable performance metrics”. A company buying BPO is not buying people or hours. It is buying outcomes: an invoice posted within two days, a call answered within thirty seconds, a payroll run without errors. The provider decides how many people that takes, where they sit and how the work is organised. That is the main difference from models in which the client receives specialists who join its own team.

Two consequences follow, and both are worth understanding before signing. First, a BPO provider earns the margin between the price per transaction and its own cost of delivering it. It therefore has a strong incentive to standardise, automate and move work to lower-cost locations. That is fine as long as the process is stable. Second, practical knowledge of how the process works gradually moves to the provider. After a few years the client has a contract, service levels and dashboards, but fewer and fewer people who understand why the process looks the way it does.

BPO should also be distinguished from contingent labour. In staffing or staff augmentation, the client directs the work and is accountable for the result. In BPO, direction of the work sits with the provider and the client manages the contract. If a “BPO” client assigns daily tasks to named provider staff, it is not really BPO any more; it is a poorly described staffing arrangement, and in some jurisdictions that distinction matters for employment law.

What is a shared service centre and how does it differ from GBS?

A shared service centre (SSC) is a unit owned by a group of companies that serves several entities or countries within that group. Instead of eleven finance teams in eleven subsidiaries, the group runs one centre that keeps the books for all of them. Employees are hired by the group, processes belong to the group, and the centre usually charges subsidiaries through internal transfer pricing.

Global business services (GBS) is the more mature form of the same idea. The ABSL report “Business Services Sector in Poland 2025” describes GBS as a model that, rather than running many shared service centres and managing suppliers independently, ensures full integration of global governance and serves all locations using all shared services and outsourcing across the enterprise. Put simply, GBS is not one more centre. It is one management layer over all centres and providers, with one process catalogue and one set of service levels.

The same report shows how these centres are put together in one of Europe’s largest shared services locations. Among surveyed SSC and GBS units in Poland, 56.3% ran a multi-function model (for example finance, IT and HR), 37.5% described themselves as GBS, and only 5.5% served a single function. More importantly for this article, 64.6% operated entirely in-house, 18.1% combined in-house teams with several BPO providers and 17.3% with a single BPO provider. Shared services and BPO are not mutually exclusive. Roughly a third of centres use both.

Deloitte has tracked this market for years. Its 2025 Global Business Services Survey, the 14th edition of what used to be called the Global Shared Services and Outsourcing Survey, was fielded in the third and fourth quarters of 2024 with leaders from more than 30 countries. It names India, the United States and Poland as the locations that have consistently ranked highest for GBS centres, with Mexico rising and Portugal entering the top ten.

How is IT outsourcing different from BPO if both mean moving work outside?

The difference is the subject of the contract. BPO is about running a process that should be stable, repeatable and measurable. IT outsourcing is about building, changing or maintaining software and infrastructure. With BPO you buy an operational outcome, a handled transaction. With IT outsourcing you buy skills and the capacity to change your systems.

IT outsourcing itself comes in several forms, and they differ mainly in who directs the work. In staff augmentation, specialists join the client’s team and work under its management. A dedicated team gives the client a complete set of roles working together on its product. In project outsourcing the provider delivers an entire project, from analysis to rollout. And in managed services the provider takes over operation of a system under an SLA. Our comparison of staff augmentation, managed services and outsourcing walks through those variants in more detail.

The easiest way to tell BPO and IT outsourcing apart is to look at what changes over time. In good BPO, the process looks roughly the same year after year, only cheaper and faster. In a good software engagement, the system looks different year after year, because business requirements, regulation and technology change. The first model rewards the provider for stability, the second for change. Those two incentives are hard to reconcile in a single contract.

What remains when the engagement ends is also different. After BPO you are left with a process description, service level history and data, while the people who did the work usually stay with the provider. After well-run IT outsourcing you are left with code, documentation, environments and, if the contract was written properly, the intellectual property in the software. That is an asset that belongs to you, and it is worth protecting from day one.

What does the market data say, and why does Poland keep appearing in it?

For a buyer, the size and maturity of the business services market matters for two reasons: it widens the choice of providers, and it tells you how hard it will be to staff a centre of your own. Poland is a useful reference point because it is one of the largest European locations for all three models.

The ABSL report “Business Services Sector in Poland 2026”, presented on 18 June 2026 at the ABSL Summit in Wrocław, counted 2,179 business services centres owned by 1,303 companies at the end of the first quarter of 2026. Employment was about 500,500 people, 7.8% of enterprise-sector employment, up 1.8% year on year. ABSL estimates the sector at 6.1% of Polish GDP, with service exports of USD 48.4 billion in 2025, up from USD 42.3 billion a year earlier, or about USD 96,700 per employee.

The split by centre type comes from the previous edition, covering the end of Q1 2025. SSC and GBS centres employed the most people: 172,396 in 495 centres, or 35.3% of the sector. IT centres followed with 157,600 people in 1,002 centres (32.3%), and BPO centres employed 81,785 people in 308 centres (16.7%). ABSL itself warns against direct comparisons between editions, because the methodology and centre database change, so treat these figures as a picture of structure rather than a precise trend.

One detail of the methodology is worth a CFO’s attention. ABSL counts as IT centres both units that provide IT outsourcing and those that develop software for external clients. In other words, the three models discussed here sit side by side in one statistical sector. That mirrors the labour market: the same process analyst can work in an SSC this year, at a BPO provider next year and at a software company the year after. If you build your own centre in a mature location, you compete for talent with hundreds of other centres in the same city.

The data also shows where the work is heading. The 2026 ABSL report says 63% of processes in Polish centres are mid-office functions and close to 60% of operations are knowledge-intensive, and nearly 85% of centre leaders said they were adopting generative AI. For a buyer the implication is simple: purely transactional work is increasingly automated, and people move to work that requires judgement. That changes the cost logic of all three models, as we discuss below.

Why do BPO, shared services and IT outsourcing answer three different questions?

Go back to the CFO from the opening. The three proposals look like competitors because each promises lower cost and better quality. But each answers a different question, which is why they cannot be compared fairly in one table with a single “savings” column.

BPO answers: who should run the process? It assumes the process is known, documented and stable, and that the company wants it run more cheaply or better than it can manage itself. The decision is about the operator, not about the design of the process.

Shared services answer: who should own the process across the group? It assumes the group runs the same process in many places and wants to standardise it, concentrate it and keep control of it. The decision is about organisational structure and where knowledge lives.

IT outsourcing answers: who should change the systems? It assumes the company needs software skills it lacks, or lacks in sufficient numbers, to build, modernise or fix its software. The decision is about the capacity to change.

These questions often arise together, because moving a process into an SSC or to a BPO provider almost always requires system changes: consolidating ERP instances, building document workflows, automating reconciliations, rebuilding reporting. That is exactly where the temptation to solve everything with one contract appears. The table below shows why it is risky.

CriterionBPOShared services / GBSIT outsourcing
Question it answersWho runs the process?Who owns the process across the group?Who changes the systems?
What the contract coversOperational outcome (transaction, case, ticket)Internal service to group entitiesSkills, a team or a software project
Who employs the peopleProviderThe groupProvider (people work for or on behalf of the client)
Who directs the workProviderCentre managementClient (staff augmentation) or provider (project)
How it is pricedPer transaction, per FTE or per outcome, with SLA creditsTransfer pricing, cost allocationDaily or hourly rate, project price, team subscription
What it rewardsStability and low unit costStandardisation and controlChange and software quality
Where knowledge ends upMoves to the providerStays in the groupIn the client’s code and documentation, if the contract ensures it
Typical time to startMonths (process transition)Months to years (centre build)Weeks (specialists) to months (project)
Main riskLoss of process knowledge and provider lock-inFixed cost and insufficient scalePoor code quality and no knowledge transfer

When does BPO make sense, and when does it just move the problem?

BPO works best for processes that are large, repeatable, well documented and not a source of competitive advantage. Payroll, accounts payable, first-line customer contact and data entry are the textbook cases. A provider running the same process for dozens of clients has scale, tooling and experience a single company will not build more cheaply.

BPO moves the problem instead of solving it when the process is chaotic. If every subsidiary posts invoices differently, exceptions are handled by email and nobody can draw the process end to end, the provider will take over the chaos along with the process. It will price it high, rightly, because it has to hire people to handle the exceptions. A year later the client is paying the provider for a mess that was previously invisible in its costs because it was spread across departments.

The old rule still applies: fix it, then outsource it. In practice that means several weeks of work before you issue an RFP. Document the process, count volumes, measure current turnaround and error rates, and catalogue the exceptions. Without that data you cannot set meaningful service levels, and without service levels you cannot hold a provider to outcomes.

The second warning sign is a process that changes often. If regulation, products or sales channels force changes every quarter, each change under BPO means a contract amendment, a new price and a transition period. A BPO contract is built for stability. Applied to a moving process, it becomes a change-request machine.

The third warning sign is a process customers experience directly and that differentiates you. Complaint handling at a premium brand can be outsourced, but its quality will then be measured by the provider’s metrics rather than by what customers feel. Sometimes that is enough. Sometimes that is exactly where your advantage sits.

When does an in-house shared service centre pay off, and when is it too early?

A shared service centre makes sense when three conditions hold at once: the group runs the same processes across many entities or countries, the volume is large enough to sustain a team with proper cover and management, and the group wants to keep control of the process and the knowledge behind it. If any of these is missing, an SSC becomes an expensive fixed cost.

There is no single headcount above which a centre pays back, and we would be wary of anyone quoting one without knowing your processes. The answer depends on factors you can calculate for a specific group: the number of entities and systems, how standardised the processes already are, labour cost in current locations compared with the centre location, the cost of office space, a leadership team and tooling, and the cost of the transition period when processes run in two places. Build the estimate in three scenarios over several years, because the first two years of a centre rarely show full savings.

Deloitte’s data illustrates the spread of outcomes. In the 2025 Global Business Services Survey, about 55% of organisations with a global GBS leader role reported average savings above 20%. Read the other way, close to half of such organisations, often large and mature ones, do not reach that level. A centre does not save money by existing. It saves money when processes have been standardised, not merely relocated.

For a mid-sized group with a handful of entities, the realistic alternative is a hybrid: standardise processes and systems within the existing structure without building a separate centre, and use a BPO provider for selected processes. That avoids a large upfront investment and keeps the SSC option open as the group grows. We covered when a captive centre makes sense for technology work in GCC vs staff augmentation. That article addresses a different decision, but many of the arguments about scale and fixed cost carry over.

Why should you not hand over system development together with the process?

This is the core of the argument. Moving a process into an SSC or to a BPO provider almost always requires system work: integrations, automation, new document workflows, reporting. BPO providers increasingly offer a package in which they take over the process together with the technology, sometimes on their own platform. To a board it looks attractive: one contract, one provider, one price per transaction.

The problem is incentives. A BPO provider is paid for the cost and quality of transactions. It is not paid to keep the system easy to change, well documented and transferable to someone else. If anything, the opposite holds: the harder it is to move the process and its systems to a competitor, the safer the contract. This is not a charge against providers’ integrity. It is the ordinary economics of a contract in which one party controls both delivery and the tools.

The consequences usually show up after a few years. The company wants to change providers or bring the process back in-house and finds that automations run on the provider’s platform, business logic lives in scripts nobody on its side understands, and historical data sits in a format that first needs translating. The exit cost turns out to exceed the savings of recent years. Vendor lock-in that prevents change is one of the warning signs listed on our Software Rescue service page, and it is the same pattern.

The remedy is simple to describe, though it takes discipline. Separate the contract for running the process from the contract for developing the systems. A BPO provider or an SSC can run the process. The systems it runs on should remain yours: code in your repository, documentation held by you, intellectual property assigned to you, and change decisions taken by a named person on your side. Development can be done by your own IT team, by that team reinforced with external specialists, or by a provider delivering a software project. What matters is that its contract rewards quality and transferability of the software, not cost per transaction.

A fair objection: what about providers that offer the process as a service on their own platform, where the platform is part of the product? That can make sense for fully standard processes, such as payroll in a single country, where the market offers several interchangeable platforms. Before you choose it, check three things: whether you can export all data at any time in a readable format, whether the contract describes the exit process with timelines and a price, and whether there are at least two other platforms you could realistically move to. If any answer is missing, the platform is not part of the service. It is a lock.

How are responsibilities split in each model?

Most disputes with providers come from the parties understanding responsibilities differently. Before signing, go through a short list of areas and write one name or one role next to each.

Process design. In BPO the provider proposes improvements, but the final shape of the process should be approved by a process owner on the client side. In an SSC, centre management is responsible, usually together with process owners in the entities. In IT outsourcing the business process is an input to the project, not its subject.

Execution. In BPO the provider executes; in an SSC the centre does. In IT outsourcing “execution” means building or changing software, and who directs that work depends on the model: the client in staff augmentation, the provider in a project.

Quality and service levels. In BPO service levels are in the contract and carry service credits. In an SSC they work as internal service level agreements between the centre and the entities. In IT outsourcing quality is measured differently: production defects, lead time for changes, test coverage, the condition of the codebase.

Systems and data. This is the area most often left vague in BPO contracts. State explicitly who owns the data, who holds the rights to software and configuration, and in what timeframe and format the provider will hand everything over when the contract ends.

Change. Who can request a change to the process or the system, who prices it and who approves it. In a well-designed model, any change to a system goes through a person on the client side, even if the provider implements it.

If you are evaluating IT providers for the systems side of such a programme, our IT outsourcing vendor evaluation scorecard gives a structured way to compare them.

Moving a process into an SSC or to a BPO provider is not just an operational decision. It has legal consequences that should be reviewed with counsel before plans are announced to staff.

Transfer of employees. In the EU, the Acquired Rights Directive (2001/23/EC) protects employees when an undertaking or part of one is transferred, and national laws implement it. In the UK, the Transfer of Undertakings (Protection of Employment) Regulations 2006 (TUPE) explicitly cover “service provision changes”, meaning outsourcing, insourcing and a change of contractor, so employees doing the work may transfer automatically to the new provider along with their terms. Whether a given handover triggers these rules depends on the facts, so get the assessment before signing rather than after the first claim.

Data protection. A BPO provider processing customer or employee data is usually a processor under Article 28 of the GDPR. That requires a data processing agreement with the elements Article 28 lists and control over the provider’s sub-processors. If part of the work is performed outside the European Economic Area, international transfer rules apply as well. In the United States, sector rules such as HIPAA for health data impose comparable contractual requirements on service providers.

Financial services. Since 17 January 2025, EU banks, insurers and investment firms have been subject to the Digital Operational Resilience Act, Regulation (EU) 2022/2554. Among other things it requires a register of contractual arrangements with ICT third-party service providers, assessment of concentration risk and exit strategies for services supporting critical or important functions. Banks also apply the EBA Guidelines on outsourcing arrangements (EBA/GL/2019/02). For these firms an exit strategy is not good practice but an obligation, which is a strong argument for keeping the process and the systems in separate contracts.

Transfer pricing in shared services. An SSC charges group entities, so its fees must meet the arm’s length principle under the OECD Transfer Pricing Guidelines and local rules. That is a topic for tax advisers, but it belongs in the cost model from the start.

How do you compare the cost of each model fairly?

The most common error is comparing a provider’s price with the current payroll of the department to be moved. That calculation leaves out half the costs on both sides.

For BPO, calculate the provider’s price under several volume scenarios, the transition cost (documentation, training, parallel running), the cost of the retained team that manages the contract and quality on your side (BPO does not work without it), the cost of changes that will happen during the contract, and the exit cost a few years out. The last item is the one most often missing and the one that most often surprises.

For shared services, calculate the build cost (premises, hiring, leadership, tooling), the transition period when processes run in two places, the cost of standardising processes and systems, which is the precondition for savings, and the annual fixed cost of the centre. Compare it with today’s cost not in year one but over several years, with an honest estimate of how quickly the centre reaches full productivity.

For IT outsourcing, calculate the cost of the team or project, the cost of management on your side (product owner, architect, someone accountable for acceptance), the cost of knowledge transfer at the end of the engagement and the cost of maintaining the system in later years. As a reference point, ARDURA’s 2026 benchmark puts a senior backend developer from Poland in a staff augmentation model at about EUR 335 to 485 per eight-hour day, net of VAT. A fuller breakdown of software project costs is in our custom software development guide.

All three calculations share one item that rarely makes it into the spreadsheet: the cost of lost knowledge. In BPO it is real and grows every year. In an SSC it is low, because knowledge stays in the group. In IT outsourcing it depends on the contract: if code, documentation and IP are on your side and the provider transfers knowledge regularly, the cost is small. If not, it grows much as it does in BPO.

Account for automation too. If, as ABSL reports, 63% of processes in mature centres are mid-office work and most leaders are adopting generative AI, a per-transaction price fixed in a five-year BPO contract may look expensive by year three compared with the cost of an automated process. The contract should include a gain-sharing mechanism for automation or periodic price reviews.

How do you make the decision, and what should you ask before talking to providers?

Instead of asking “BPO, shared services or IT outsourcing?”, ask the three questions from this article separately for each process in scope.

Who should run the process? If it is stable, documented, large and not a differentiator, consider BPO. If it is chaotic, fix it first. If it changes often or carries your advantage, keep it in-house or in an SSC.

Who should own the process across the group? If the group runs the same process in many entities, has the scale and wants control, consider an SSC. If scale is small, start by standardising within the current structure.

Who should change the systems? Whatever the answers to the first two, decide who will build and evolve the software the process runs on. Make it a separate decision, with a separate contract and the rule that code, data and knowledge stay on your side.

Before talking to a BPO provider, have answers to a few control questions. Do we have a process description and measured baseline service levels? Who on our side will manage the contract? What is the exit plan, with timelines and a price? Who owns data, configuration and automations? How does the contract treat gains from automation?

Before an SSC discussion: how many entities and systems will the centre cover, what is the standardisation plan, who will lead it, and what is the downside scenario over several years?

Before talking to an IT provider: who on our side makes scope decisions, where will code and documentation live, how will knowledge be transferred, and what happens if a specialist does not fit the team? Our IT outsourcing page sets out the engagement models and terms we work with, such as a two-week specialist replacement guarantee and a 30-day notice period.

Where does a software development partner fit in this picture?

To be clear about what ARDURA does not do: we do not provide BPO and we do not run shared service centres. We do not take over finance, HR or customer service processes, and we do not offer managed services as a standalone service.

Our place is the third question: who changes the systems. A company moving processes into an SSC or to a BPO provider usually needs integration across several systems, automation, new workflow applications or modernisation of the legacy software the process has run on for years. That is software work, and we help in three ways.

First, we provide specialists and teams from Poland who work under the client’s management, through staff augmentation; a good fit when you have an IT team and need to reinforce it for the transformation, which is also the logic behind IT nearshoring to Poland. Second, we deliver whole projects through our software development services, from analysis to rollout, with code and documentation handed to the client. Third, through Software Rescue we take over and stabilise projects that have stalled with another provider. Once a project is complete we can take over maintenance under an SLA, but only for a system we built or rescued ourselves.

That split is consistent with the argument of this article: a BPO provider or an SSC runs the process, and system development is done by a team whose contract rewards quality and transferability. If you want to know the condition of the system behind a process before you move it, you can start with an independent technical due diligence; ARDURA’s Code Health Audit starts from EUR 4,500 and takes one to two weeks.

What are the key takeaways?

BPO, shared services and IT outsourcing are not three versions of the same decision. BPO answers who should run a process. Shared services answer who should own it across the group. IT outsourcing answers who should change the systems. Comparing them in one table with one “savings” column leads to poor decisions.

Remember five things. First, BPO buys outcomes and works best for stable, documented processes that do not differentiate you; fix a chaotic process before handing it over. Second, an SSC makes sense for repeatable processes across many entities at sufficient scale, and savings come from standardisation, not relocation. Third, the market is large and mature: Poland alone had 2,179 business services centres and about 500,000 employees at the start of 2026, according to ABSL, so you have a choice of providers but also competition for talent. Fourth, calculate the full cost of each model, including contract management, transition and exit. Fifth, and most important: do not hand over system development together with the process. Code, data, documentation and change decisions should stay on your side.

If you are moving processes and need a team to build or modernise the systems they will run on, see how we work in IT outsourcing, or book a call. We start by establishing who on your side owns decisions about the systems and how knowledge will stay with you after the engagement ends.