How PUMA Built One Governed Business Partner Platform on Pega
PUMA × Saltech at PEGA Innovate Munich 2026
At PEGA Innovate Munich 2026, Jonas Gubo, who leads Digital Governance at PUMA, and Gergő Koppány, Lead Developer at Saltech, took the stage together. They told the story of ARGOS: how PUMA turned fragmented, manual business partner processes into one governed platform on Pega, and went live in 94 PUMA entities in half a year.
Watch the full session below. Further down you’ll find the key ideas and what other organisations can take from them.
The challenge: many systems, unclear ownership
When Jonas joined PUMA’s master data governance team, he found the same business partner data being kept in several local systems. Work was duplicated, every new regulation added complexity, and nobody could clearly say who owned which data. Address changes and supplier setups were done by hand, with no quality gates.
There was also a timing problem. Business partners were often onboarded only when an invoice arrived, which meant delayed invoice processing and frustrated teams.
The solution: ARGOS, built on Pega
PUMA named the solution after Argus, the Greek watchman with a hundred eyes who sees everything. That was exactly the goal: full visibility over business partner data.
ARGOS grew into three connected products:
ARGOS EBP handles business partner onboarding with built-in governance, compliance and automation, integrated with PUMA’s SAP S/4HANA landscape.
ARGOS Contract is a new contract management platform. It moved onboarding to where it belongs: the moment a contract is created.
ARGOS Data Hub is a central place for business partner and contract data, available inside and outside Pega.
The first product went live in 2023 and was rolled out market by market. For the contract platform, PUMA chose a big-bang approach instead and went live in 94 entities within half a year.
How it works: one global core, local flexibility
PUMA is a decentralised organisation, so the solution had to work globally without ignoring local needs. The key architectural decision was to use Pega’s layer cake model:
Processes, rules and guidelines are defined once in a shared global layer.
Regions and countries specialise only what really differs, such as approval thresholds, required documents or compliance steps.
The second principle is Pega as the orchestrator. The process and the business rules live in Pega, while data and services come from connected systems such as SAP S/4HANA, Adobe Sign, Refinitiv, CDQ and AI services. Because the integration logic is kept separate from the business logic, a service can be swapped for a better one without touching the core process. As Jonas put it: “We don’t care if there’s a better AI version tomorrow. We just swap it out.”
The result is automated processes, full traceability, clear ownership, one central hub and better data quality.
Lessons learnt
Build with business users, not just for them. Involve end users early and show them working results often.
Use standard Pega capabilities wherever practical. It keeps maintenance low and makes upgrades painless.
Lean beats oversized. A small, experienced team that works as an extended workbench of the client moves faster than a large one.
Put communication and change management at the core. Explain the why and the how again and again. PUMA even has a working student dedicated to it.
What’s next
The next step is invoice management, so that business users can follow the whole journey from contract to onboarding to payment in one interface.
