Turnkey core modernization: What does it mean and what are the key questions to ask before signing?
Modernizing a core system involves intervening on an infrastructure that supports critical business processes and that may have been evolving along with the organization for decades.
The complexity of this transformation means that the decision doesn't end with defining what to modernize or what strategy to follow. It's also necessary to determine under what model the project will be executed and what responsibilities the technology partner will assume.
What's interesting is that there's a market context conducive to core modernization, immersed in a dynamic of changing orientations. As the report highlights. Kyndryl 2025 State of Mainframe Modernization Survey Report, he 80 of the surveyed companies modified their modernization strategy, and 88 are implementing or planning to add GenAI to the mainframe..
In this context, the modernization of the core turnkey model emerges, a model that should clearly establish what responsibilities the partner assumes regarding the scope, deliverables, and financial dimension of the project.
However, using the term "turnkey" is insufficient to determine how responsibilities will be distributed, what will happen in the event of deviations, or how progress will be measured. Before signing, it is essential to understand exactly what lies behind that promise.
With that objective, we analyzed what a turnkey modernization project entails for us, and why the first months of assessment These are key factors, and we'll discuss how responsibilities are distributed between the organization and its technology partner. We'll also share the role of milestones and the billing model, and what questions to ask before choosing a provider and starting the transformation.
“Turnkey” means different things depending on the supplier
In a conventional technology project, there can be a relatively simple delineation between the tasks of the supplier and those of the client. In the core modernization, That border is much more complex.
The project intervenes on systems that continue to function, These systems support critical processes and maintain multiple dependencies built up over the years. What we must keep in mind is that many of these relationships only become fully visible when the assessment work begins.
Therefore, talking about a turnkey project should involve much more than simply committing to specific profiles, working hours, or activities. From our perspective, it implies assume responsibility for the scope, delivery, and financial dimension of the project, working under a partnership logic.
This does not eliminate customer involvement. On the contrary, it requires a close relationship between both parties. The difference is that the partner It doesn't just provide technical expertise: it assumes responsibility for the agreed-upon path and its outcomes. In a transformation that can extend over years, that difference is fundamental.
First 90-120 days: why you won't see results in this period
One of the most difficult moments can occur, paradoxically, at the beginning. During the first 90 to 120 days, a significant part of the work is concentrated on the assessment, with interviews, information analysis, surveys, review of programs and dependencies, process evaluation and construction of the roadmap.
From the outside, the project may seem to be progressing slowly because there aren't yet any major production results to show. But that stage is precisely the one that It allows for reducing uncertainty and building a solid foundation for the development of the project..
In legacy environments It is common to find programs that have not been modified for many years, configurations whose origin is difficult to reconstruct, batch processes that consume resources without sufficient visibility, or dependencies that were not documented.
Attempting to artificially accelerate this process may mean shifting that uncertainty into the execution phase.
The initial analysis allows us to replace assumptions with evidence and build a roadmap for the following months or years. In this sense, one of the first issues of expectation management that should be resolved before starting is very concrete: the first few months may produce a lot of knowledge and few visible results, but That knowledge is an essential part of the future outcome..
What does it mean to be responsible for scope, delivery, and finance?
A turnkey core modernization shouldn't be evaluated solely by the amount of code migrated, programs recompiled, or components modified. The ultimate goal is... the impact that this transformation has on the business.
This necessitates establishing from the outset what improvements are desired and how they will be verified. Consumption, performance, costs, processing times, delivery speed, or the capacity to evolve certain services can all be part of that equation, depending on the project.
So we have three types of responsibilities:
- Responsibility for the scope of the project involves establishing what will be transformed and under what criteria.
- Accountability for delivery involves agreeing on verifiable results and milestones, rather than just measuring effort.
- Financial responsibility requires establishing an economic framework that allows for the management of a long-term project with greater predictability.
The three dimensions are interconnected. An ambiguous scope makes it difficult to evaluate deliverables, and poorly defined deliverables make controlling investment even harder. Meanwhile, a financial scheme completely decoupled from results can create incentives that don't necessarily align with business objectives. A turnkey model needs to connect these variables.
Semi-fixed billing with milestones: how it works in practice
Modernization projects have a particular characteristic: they require predictability, but they are developed in environments where not everything can be known before starting. Therefore, the challenge lies in avoiding two extremes: attempting to finalize every detail of a multi-year transformation in advance, or working without sufficient certainty about costs and expected results.
The model we propose seeks to resolve this tension through semi-fixed billing. associated with delivery milestones and previously agreed steps. In this way, the project establishes a framework of scope, responsibilities, and objectives, while progress is organized through deliverables that allow for the progressive verification of results.
This dynamic becomes especially important when modernization is carried out gradually. Instead of transforming the entire core in a single intervention, components can be modernized, tested, deployed to production, and the coexistence of the old and new environments maintained for a period of time. Each stage also provides information for the following ones.
The contractual model and the technological model, therefore, should not be considered independently: if the transformation is progressive, the billing by milestones and the way of committing to deliveries also need to follow that logic.
The client also has responsibilities
Turnkey doesn't mean delegating the project and waiting for the final result. One of the central conditions that Pablo Reitano, Head of Delivery IT Patagonia, The key to a successful modernization lies in the client organization actually having its team available.
That means Assign people capable of making decisions, providing business knowledge, and taking ownership of the transformation. It also requires sponsorship at different levels.
He C-level support It allows for maintaining strategic priorities and unlocking decisions. But transformation happens every day in operations, so it also needs leaders capable of guiding the project at that level.
Executive committees, tactical units, and operational teams allow for monitoring different dimensions and timeframes of the program. A good partnership model, then, doesn't dilute responsibilities; it makes them explicit. Shared responsibility means knowing from the outset what commitments the partner assumes and what commitments the organization itself needs to assume for the project to move forward.
Questions to ask a supplier before signing
Before accepting a turnkey core modernization proposal, it is advisable to turn general promises into concrete answers.
We share a series of key questions that will bring greater clarity to the project:
1. What exactly does “turnkey” mean for the supplier? It is necessary to understand what responsibilities are assumed and which will remain in the hands of the client.
2. How is the scope defined and eventually reviewed? In systems with decades of history, discoveries will emerge during the assessment. The project should consider how these will be managed.
3. What happens during the first 90-120 days? It is important to know what deliverables the assessment will have and how they will translate into an executable roadmap.
4. How are milestones established? They should represent verifiable progress and not simply elapsed time.
5. How is the result measured? In addition to technical metrics, there should be tactical and strategic indicators that allow observation of the overall impact of modernization.
6. What happens if a detour appears? A long-term project needs review, decision and escalation mechanisms.
7. What involvement will the internal team need? It is necessary to know the profiles, expected dedication, and decisions that will remain under the responsibility of the organization.
8. Who governs the project? It is advisable to define from the beginning the operational, tactical and executive responsibilities, the frequency of follow-up and mechanisms to resolve problems.
9. How does billing relate to deliveries? Understanding this relationship allows us to assess what part of the risk each participant actually assumes.
10. What happens while the core continues to function? The strategy must explicitly include operational continuity, testing, coexistence between components, and mechanisms to reduce risks.
A contract does not replace a partnership
Core modernization can extend over long periods of time, during which discoveries, context changes, technical decisions, and business needs will arise that do not yet exist at the time the project begins.
No contract can anticipate all these variables, which leads to the conclusion that a turnkey core system modernization proposal is not simply about comparing scope, price, and schedule. It also involves understanding how responsibilities will be distributed when unforeseen events arise. That's where the concept of partnership truly comes into play.
Modernizing the core is not simply executing a technology project; it's about a Business transformation with a large technological component, which must advance while the organization continues to operate.
Before choosing who will accompany you on this journey, then, there is a question worth answering precisely: if something changes or goes astray along the way, who is responsible for bringing the project back towards the goal?
Checklist for evaluating a modernization proposal
Before making a decision, and if your organization still needs to determine its starting point, Schedule an assessment with our team to analyze the current state of your core and build a modernization plan.
