Editorial photograph of an industrial tyre manufacturing operation running a multi vendor software framework
Multi Vendor · Customer Announcement · Prometeon

Prometeon Tyre Group selects Redress Compliance. Multi vendor software advisory and negotiation across the enterprise software estate.

One licensing conversation across Oracle, SAP, Microsoft, the hyperscalers and the rest of the estate, instead of eleven separate ones nobody is joining up.

Book a Multi Vendor Scoping Call Vendor Shield
500+Vendor engagements
11 practicesVendor coverage

Zero fee risk, if you want it: most negotiation engagements can be paid entirely from the savings we create. No savings, no fee →

Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent
Customer
Prometeon Tyre Group
Leading global truck and industrial tyre group.
Vendors
Multi vendor
Oracle, SAP, Microsoft and the wider estate.
Engagement
Vendor Shield
Always on multi vendor management posture.
Posture
100% buyer side
Independent. Industry recognized. 500+ enterprise clients.

Prometeon Tyre Group has selected Redress Compliance as its independent buyer side advisory and negotiation partner across the enterprise software estate. The scope covers Oracle, SAP, Microsoft, the hyperscalers, and the wider portfolio including Salesforce, IBM, Broadcom, ServiceNow, Workday, Cisco and the GenAI vendors.

The engagement runs under Vendor Shield, our always on multi vendor posture. The point is not to negotiate harder. It is to stop treating eleven vendor relationships as eleven unrelated events.

See the Vendor Shield program, the renewal program, the software spend assessment, and the benchmarking practice.

Five dimensions carry a multi vendor estate, and they interact.

  1. Oracle. Named users, database and technology licensing, applications, and whatever remains of an unlimited agreement.
  2. SAP. Named users, engine metrics, the FUE conversion, indirect access exposure, and the S/4HANA timetable.
  3. Microsoft. The Microsoft 365 SKU mix, Copilot, Azure commitments, and the enterprise agreement that ties them together.
  4. The hyperscalers. AWS and Google Cloud commitments, which increasingly overlap with what Microsoft is also selling.
  5. The rest of the portfolio. Salesforce, IBM, Broadcom, ServiceNow, Workday, Cisco and the AI platforms, each with its own renewal clock.

They compound. An Azure commitment changes your AWS leverage. An S/4HANA migration changes your Oracle database position. Handled separately, those connections are invisible.

About Prometeon

Prometeon Tyre Group is a leading global truck and industrial tyre manufacturer operating across EMEA, the Americas and APAC. It runs a substantial software estate supporting manufacturing, supply chain and operations across those regions.

Multi region manufacturing makes the licensing harder than headcount alone suggests. User populations vary by site, plant systems have their own integration requirements, and the same vendor is often bought differently in different countries.

The group engaged Redress Compliance ahead of its next renewal cycle, with the work covering the whole estate rather than a single vendor. See the Vendor Shield program.

Scope of engagement

Three phases, sequenced so that the commercial work rests on real deployment data rather than on assumptions.

  1. Scoping. Map what is deployed against what is licensed, vendor by vendor, and build the renewal calendar that shows every date in one place.
  2. Negotiation. Run the renewals in sequence, using the position established in scoping and the leverage each renewal creates for the next.
  3. Management. Keep the position current between events under Vendor Shield, so audits and renewals arrive expected rather than announced.

The third phase is the one buyers skip and the one that pays. An estate reviewed once decays; an estate tracked continuously arrives at each renewal with its own numbers ready.

VendorWhat drives the costWhat buyers usually miss
OracleNamed users, processor counts, and support on the full estateSupport billed on licenses that were shelved years ago
SAPNamed user tiers, engine metrics, and indirect accessIndirect access exposure created by systems nobody classed as SAP
MicrosoftThe Microsoft 365 SKU mix and Azure commitmentA uniform E5 estate where a minority actually needs E5
HyperscalersCommitted spend against forecast consumptionCommitments sized on optimistic forecasts that never arrive

Oracle

Oracle cost is driven by three things: how users and processors are counted, how much of the estate carries support, and what remains of any unlimited agreement.

Support is where the recoverable money usually sits. Maintenance is typically renewed across the whole estate as a matter of routine, including licenses that stopped being used several years ago.

Named user and processor counting rules reward precision and punish estimation. Getting the count right is unglamorous work that consistently outperforms arguing about the discount. See the Oracle advisory practice.

SAP

SAP has two cost engines. Named user licensing, which is visible and argued about, and engine and indirect access licensing, which is far less visible and considerably more expensive when it goes wrong.

Indirect access is the risk that matters. Any system that reads or writes SAP data can create a licensing obligation, and the systems that do this are frequently not thought of as SAP at all.

An S/4HANA move changes the whole picture, including the FUE conversion that decides what your existing entitlements are worth. That conversion is negotiable and is often treated as arithmetic. See the SAP advisory practice.

Microsoft

Microsoft cost concentrates in the Microsoft 365 SKU mix, the Copilot rollout, and the Azure commitment, all wrapped in an enterprise agreement that makes them look like one decision.

They are not one decision. A uniform E5 estate is a licensing convenience rather than a security posture, and segmenting the population by what it actually uses is usually the largest single lever available.

Copilot deserves the same discipline. Coverage targets are a vendor metric, and measured productivity uplift is a buyer metric. See the Microsoft advisory practice.

Vendor Shield

Vendor Shield is the always on posture that runs between the events. It covers renewals, audits and migrations across the whole estate rather than one vendor at a time.

Four things run continuously. Renewal dates tracked far enough ahead to matter. Audit readiness kept current so a letter is answered from evidence. Migration positions held so vendor timetables do not become yours. And benchmark data kept fresh so every quote can be tested.

The value is timing. A renewal you saw coming twelve months out is a negotiation, and one you noticed ninety days out is a price acceptance. See the Vendor Shield program and the renewal program.

Where the common advice on multi vendor software management is wrong

The common advice is to consolidate onto fewer vendors, on the logic that scale buys discount and fewer relationships mean less overhead. We disagree, at least as a default. Consolidation hands a single vendor knowledge of your whole estate and removes the alternatives that make any negotiation work. The buyers who do best are not the ones with the fewest vendors, they are the ones who know their own numbers across all of them and can move a workload if they need to. Deliberate, managed plurality is leverage. Consolidation is convenience, and you pay for it at every renewal that follows.

Editorial photograph of a procurement team reviewing a multi vendor software renewal calendar
The renewal calendar is the cheapest artefact in multi vendor management and the one almost nobody maintains. Vendors keep theirs.

Why Prometeon selected Redress Compliance

Independence. Redress Compliance takes no income from any software vendor. We do not resell, do not implement, and hold no partner or referral agreements with any publisher in this estate.

That matters because most licensing advice available to a buyer comes from an organization that earns more when the buyer spends more. Our only commercial relationship is with the buyer.

The practice covers more than five hundred enterprise clients across eleven vendor practices, which is what makes benchmark data possible. See the benchmarking practice.

What to do next

If you run a multi vendor estate, these are the steps that matter, in order.

  1. Build one renewal calendar covering every vendor, with dates, values and notice periods in a single view.
  2. Reconcile entitlement against deployment for your three largest vendors before touching the others.
  3. Identify which renewals fall within six months of each other, because those are the ones that create leverage for one another.
  4. Find your indirect access exposure on SAP and your support on shelved Oracle licenses. Those two account for a large share of recoverable spend.
  5. Check whether overlapping cloud commitments across Microsoft, AWS and Google are being counted as one position or three.
  6. Put the estate under continuous review so the next renewal starts from your data rather than the vendor's.

How we engage

  • Multi vendor scoping. A six week engagement that maps the estate vendor by vendor, builds the single renewal calendar, and sets the commercial moves for the next cycle. Vendor Shield program.
  • Renewal negotiation. We run the renewals across Oracle, SAP, Microsoft, the hyperscalers and the wider portfolio, in the order that builds leverage rather than the order they happen to fall. Renewal program.
  • Audit defense. Position, evidence and response when any vendor in the estate opens a compliance review. Audit defense kits.
  • Vendor Shield. Always on cover between the events, so renewals and audits arrive expected. Vendor Shield.
  • Run the numbers. The software spend assessment sizes the estate against what is actually deployed.
  • Benchmarking. The benchmarking practice tests every quote against what comparable buyers actually pay, drawn from more than five hundred enterprise clients. Reference cases include the Cox Enterprises Workday renegotiation and the wider case studies library.
Vendor Shield

The always on multi vendor management posture across the broader enterprise software estate.

Vendor Shield covers renewals, audits and migrations across the whole estate. It runs for more than five hundred enterprise clients across eleven vendor practices: Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco and the GenAI vendors.

Used across more than five hundred enterprise clients. Independent. Buyer side. Built for IT procurement leaders running the broader enterprise software estate.

No spam. We will only email you about this download. Privacy.
Run the software spend assessment against your broader enterprise software estate in under five minutes.
Open the Tool →
500+
Enterprise clients
11 practices
Vendor coverage
5 dimensions
Multi vendor scope
20+ yrs
Combined experience
100%
Buyer side
500+
Enterprise clients advised
11
Vendor practices covered
100%
Buyer side, no vendor income

Source: Redress Compliance advisory engagement file.

We selected Redress Compliance for the independent buyer side result across the broader enterprise software estate. The approach anchors the broader enterprise software estate against our actual user, our actual asset, and our actual broader vendor rather than the publisher's preferred broad vendor.

Chief Information Officer
Prometeon Tyre Group
Further Reading
Vera AI · 30 day free trial
Vera reads your contracts the way an auditor does.
  • Your agreements decoded into plain English before the auditor interprets them for you
  • Coverage grid: liability caps, IP protections, and SLAs checked in one pass
  • A defensible position paper generated in minutes, not weeks
Start the free Vera AI trial →30 day free trial · no card needed

From the same practice.

Vendor Shield →
Vendor Shield
Multi Vendor · Program
Vendor Shield Program
The always on multi vendor management posture.
22 min read
Renewal Program
Multi Vendor · Program
Renewal Program
The renewal program across the broader vendor.
18 min read
Multi Vendor Audit Readiness
Multi Vendor · Article
Multi Vendor Audit Readiness Checklist
The cross vendor audit defense.
16 min read
Software Spend Assessment
Multi Vendor · Assessment
Software Spend Assessment
The software spend assessment against the broader enterprise software estate.
12 min read
Vendor Benchmark Program
Multi Vendor · Program
Vendor Benchmark Program
Subscription benchmarking across tier 2 and tier 3 vendors.
14 min read
Editorial photograph

Software contracts are negotiations dressed as quotes.

Twenty years on the buy side. 500+ enterprises. $2B in client savings.

Multi vendor intelligence, monthly.

Oracle signals, SAP signals, Microsoft signals, broader hyperscaler signals, broader Salesforce signals, broader IBM signals, and the broader enterprise software licensing leverage signals across the multi vendor practice.

Cover of the Software Licensing Financial Services white paper from Redress Compliance

White Paper · Multi Vendor

Software Licensing Financial Services

Read it free.

Read the white paper
Negotiating a renewal? Read the paper before you counter. Upload the contract or renewal quote to Vera AI and get a clause by clause read in plain English: which terms are off market, where the money hides, and paste ready replacement language to send back. Free, no signup needed. Decode your contract free with Vera AI →

Frequently asked questions

Why did Prometeon select Redress Compliance?

Prometeon Tyre Group selected Redress Compliance for independent buyer side advisory across its multi vendor enterprise software estate. The firm holds no reseller margin or vendor partner status, so the advice serves Prometeon only. That independence was central to the decision.

Which vendors does the Prometeon engagement cover?

The engagement covers Prometeon's estate across the major enterprise vendors, including Oracle, Microsoft, SAP, and Salesforce. It spans renewal strategy, audit defense, and cost optimization. The scope reflects a typical multi vendor manufacturing estate.

How is the multi vendor engagement structured?

The engagement runs as an always on advisory subscription through the Vendor Shield program. It covers negotiation, benchmarking, and audit defense across the vendor portfolio continuously. The model keeps a buyer side position in place year round, not just at renewal.

What results does multi vendor advisory target?

Multi vendor advisory typically targets 15 to 35 percent savings against vendor proposals across the portfolio, alongside reduced audit risk. Actual results depend on contract timing and estate complexity. The savings come from benchmarking and disciplined negotiation.

Is Redress Compliance independent?

Yes, Redress Compliance is 100 percent buyer side across all eleven major vendor practices, with no reseller margin or partner status. The advice optimizes the buyer's position, not vendor revenue. That independence underpins every engagement.