Home/Outsourcing advice

Outsourcing advice: tender, contract and transition

Tender documents for z/OS operations at a fixed price. The better the preparation, the fewer questions from bidders — and the fewer expensive surprises once operations start.

The starting point

You are comparing bids built on different assumptions

The most common mistake in a mainframe tender happens before it is published: the volume baseline is missing or vague. Every bidder then calculates on its own assumptions — and the bids are formally comparable but substantively not.

What follows is familiar to anyone who has been through it: renegotiations, change requests for services you assumed were included, and a price that after two years is no longer the one you signed.

The point many overlook: a provider billing by MIPS or MSU has no economic incentive to reduce your consumption. The contract has to resolve that conflict of interest — otherwise you pay for optimisation that never happens.

Why consolidation pays for the provider

Software pricing on the platform is tiered degressively: the first capacity units are expensive, and as volume grows the price per unit falls markedly. A provider consolidating several customers onto one machine therefore reaches terms a single operator cannot.

That effect is real and can make outsourcing genuinely worthwhile. The decisive question is how much of it reaches the customer — and that is purely a matter of contract.

Services

What we take on

Available individually or as continuous support from the first analysis through to steady-state operation with the new provider.

Volume baseline and current state

Measured capacity consumption, load profile across the day, batch windows, sysplex topology, subsystem and software landscape. That is the basis on which bidders can calculate properly at all.

Contract and cost review

Assessment of existing framework agreements including volumes and the optimisation and savings potential. This often already shows whether outsourcing is the right lever at all.

Tender documents

Requirements specification, service cut, SLA targets and evaluation matrix — at a fixed price. On request including preparation of bidder questions and answers.

Bid evaluation

Structured assessment of the responses against the criteria agreed beforehand, surfacing of assumptions and gaps, preparation of the negotiation rounds.

Contract clauses

The points that make the difference later: transparency on consumption, audit rights, rules on subcontracting, benchmarking and a workable exit clause.

Transition and operation

Support through handover and the first months of operation — that is where it becomes clear whether the commitments made are actually lived.

Process

The phases of a tender

Requirements and scope

What is to be outsourced, what stays in house? Define the service cut, the requirements and the objectives, and align them internally.

Outcome: agreed service cut and target picture

Survey the market

Which providers qualify, and which service cuts fit their portfolios? A cut no provider actually offers produces expensive special pricing.

Rule of thumb: invite five, at most seven providers

Prepare the documents

Requirements specification with volume baseline, contractual and legal framework, evaluation and selection criteria, schedule and deadlines. The emphasis is on the what, not the how.

This is the fixed-price part of our work

Publish and answer questions

A defined window for bidder questions; answers go to all participants so that everyone competes on equal terms.

Good documents show in the small number of questions

Review and score the bids

Comparison against the criteria defined in advance: fulfilment of requirements, value for money, experience, future viability. Bidder assumptions are surfaced and recalculated.

Outcome: a traceable ranking rather than a gut feeling

Negotiate and sign

Presentations by the shortlisted providers, clarification of contract detail, price negotiation and final adjustments to the proposed solution.

This is where the clauses that must hold later are set

Transition and steady state

Takeover of the existing installation, handover, establishment of reporting and verification of the committed service levels in live operation.

Optionally with recurring analysis to verify the effect

Regulation

For financial firms the contract has not been an open field since 2025

DORA has applied directly since 17 January 2025 and prescribes specific contractual content for outsourcing. A mainframe tender drafted without these points will need renegotiating later.

For all outsourcing contracts

  • A complete service description including the rules on subcontracting
  • The locations where services are provided and data processed, with notification on change
  • Access and return rights for data on termination or insolvency
  • Assistance with ICT incidents at no additional cost
  • Termination rights with minimum notice periods; cooperation with supervisory authorities

Additionally for critical functions

  • Precise quantitative and qualitative performance targets
  • Comprehensive access, inspection and audit rights — for you and for the regulator
  • Provider participation in threat-led penetration testing
  • Contingency planning and reporting duties on material changes
  • An exit strategy with adequate transition periods — documented, tested and reviewed regularly

Subcontracting

Since 22 July 2025 a regulatory technical standard on subcontracting applies in addition: the contract must state explicitly which services may be subcontracted, material changes in the subcontractor chain must be notified in advance, and you need a right to object or terminate.

What is shifting in 2026

The ninth amendment to the German MaRisk removes ICT services from the previous outsourcing module — they will be assessed under DORA alone. The duplicate register keeping falls away; the level of requirement remains. The amendment was not yet final at the time of writing; we verify the current status within the project.

Pitfalls

Where mainframe tenders regularly become expensive

  • Too much “how”, too little “what”. Requirements should describe outcome, quality and volume — not prescribe the solution.
  • Excessively detailed current-state surveys. What matters is volume data a provider can calculate with, not meticulous documentation of every component.
  • Too many bidders. Each additional participant costs review effort without improving the quality of the decision.
  • Unusual service cuts. Anything that fits no provider portfolio is priced as a special case — with a risk premium.
  • Capacity instead of consumption. Pricing should be based on used, not installed capacity.
  • No transparency on consumption. Without contractually guaranteed reporting you cannot verify what you are paying for.
  • A soft exit clause. Without a defined handback process the next provider change is practically not negotiable.
  • Benchmarking without rules. If the comparison mechanism is not agreed in the initial contract, it will not be agreed later.
On benchmarking: established practice is to commission the benchmarker jointly and split the cost evenly — that safeguards neutrality. Results typically fall within a band of roughly ten to fifteen per cent; where deviations are minor, the contract is usually not adjusted. Both should be settled in advance, otherwise the dispute is about the method rather than the numbers.

Context

Why the topic is gaining momentum

20 %of respondents run the mainframe outsourced — up from 9 % the year beforeArcati Mainframe User Survey 2025
62 %report a skills gap in the mainframe environmentArcati Mainframe User Survey 2025
70 %have difficulty finding mainframe staffKyndryl State of Mainframe Modernization 2025
46 %of new hires arrive without mainframe skillsKyndryl State of Mainframe Modernization 2025

All figures come from user surveys with self-selected participants and small samples; the jump from 9 to 20 per cent within one year is more likely a sampling effect than an established market trend. And there is countervailing evidence: other surveys report a markedly higher share of younger specialists. The story of the dying mainframe generation is not uncontested.

FAQ

Questions about mainframe outsourcing

What does “tender documents at a fixed price” mean?

Preparation of the requirements specification including volume baseline, service cut, SLA targets and evaluation matrix is delivered at a price agreed in advance, not on a time and materials basis. The scope is defined in the initial conversation. Further support through negotiation and transition is agreed separately.

Do you represent a particular provider?

No. We are neither a provider of mainframe operations nor a licence reseller, and we receive no commission from providers. That is precisely why we can assess the bids independently.

Is outsourcing worthwhile for us at all?

That is the first question, not the last. It can be answered once your own consumption and costs are properly measured. Sometimes the calculation shows that targeted optimisation in house delivers more than outsourcing — that is a result too, and we will say so.

We have already outsourced. Can you still help?

Yes, and often that is the more rewarding case. Typical starting points: checking billed volumes against actual consumption, preparing a benchmarking exercise, tightening transparency and exit clauses at contract renewal, or preparing a change of provider.

How does this relate to your performance analysis?

Very directly. The volume baseline of a tender is exactly the output our performance and cost analysis produces anyway. Commissioning both together means paying for data preparation only once — and entering negotiations with evidence rather than estimates.

Measure before you tender.

We look at your starting position and tell you which documents you need and what already exists.

Discuss a tender See the cost analysis