For the people accountable for business-critical processes and applications

The Path to Successful Modernisation

For the people accountable in banks, insurers and large enterprises who have to modernise a business-critical process or an established business application — and who want to establish, before they invest, what really has to change.

Typically: unstable legacy applications, knowledge that sits with individuals, landscapes of Excel, Access and VBA, pressure from a platform decision, manual re-keying between systems, or a migration that is due.

Three clearly bounded planning stages. Transparent prices. No obligation to have Agile-IS deliver the implementation afterwards.

A structured analysis narrows several options down to a clear, prioritised modernisation path.

The path is particularly useful when …

The path is for people who face a real modernisation decision and want to avoid putting the wrong solution in place too quickly.

  • an important business process no longer works reliably
  • an established business application is unstable or technically at risk
  • knowledge and business logic depend on individual people
  • several routes to a solution are being discussed
  • migration, automation or a rebuild are on the table
  • internal IT or conventional projects cannot help fast enough
  • budget and decision lack a reliable basis
  • the next step has to be defended internally

Scope and pricing

As far as your modernisation decision needs to go.

Three stages that build on one another — from a robust view of the current state through to preparing the internal alignment.

  1. 01

    Clarity

    What really needs to be modernised?

    We make visible how the business process, knowledge, responsibilities and applications work together today, where the critical dependencies lie and which risks affect the process.

    Target state

    A robust view of the current state

    Fixed price €3,000 plus VAT

    For situations where it first has to be established reliably what actually needs modernising.

    • the current situation and the core problem
    • the relevant risks and dependencies
    • the need to modernise
    • a robust results document
  2. 02

    Direction

    For most initiatives

    Which modernisation path is viable?

    Building on the current-state assessment, we develop and evaluate possible modernisation paths. We consider business impact, technical viability, risk and organisational requirements together.

    Target state

    Ready for decision

    Fixed price €7,500 plus VAT

    You then know which modernisation paths are viable and can justify a preferred direction internally.

    • includes Clarity
    • a viable target state
    • modernisation options and their evaluation
    • a recommendation and a modernisation roadmap

    Includes the Clarity stage.

  3. 03

    Alignment

    How can the chosen path be aligned across the organisation?

    We make the chosen modernisation path specific enough for internal alignment and prepare it for subsequent implementation.

    Target state

    Ready for internal alignment and implementation

    Fixed price €12,500 plus VAT

    The preferred path is made specific enough for the necessary business, technical and organisational alignment to be conducted on a sound basis.

    • includes Clarity and Direction
    • the technical and organisational conditions
    • the dependencies and preconditions
    • preparation for alignment with IT and governance

    Includes the Clarity and Direction stages.

You do not have to have picked a stage yet. In the conversation we check how far the decision has already come and what is actually needed.

Not sure yet whether there is any need to modernise at all? Start the Initial Assessment

Avoid modernising the wrong thing.

Fixing the solution too early does not only put budget behind the wrong direction. It also ties up the people, the time and the attention that a second attempt often struggles to mobilise again.

  • the old problem is merely carried over to a new platform
  • a technology decision is made before the problem is clear
  • an unnecessarily large project is triggered
  • an application is renewed in isolation from the business process
  • important business logic is lost during the replacement
  • budget is requested without being able to explain the benefit reliably
  • a quick repair only extends the existing dead end

The process

How modernisation planning works.

The basic structure stays the same. How deeply we go into the target state, the options and internal alignment depends on the stage chosen.

  1. 01

    Preparation

    Existing information, documentation and the current situation are placed in context together.

  2. 02

    Survey

    The business process, the reality of its users, the knowledge, the roles and the application are recorded systematically.

  3. 03

    Analysis

    The core problem, the risks, the dependencies and the actual need to modernise are worked out.

  4. 04

    Consolidation

    The findings are consolidated, to the depth of the planning stage chosen, into a view of the current state, a basis for decision or a path ready for alignment.

  5. 05

    Result and next step

    The results are discussed together and the sensible next step is agreed.

Two typical perspectives

Keeping an important application running while the situation grows more unstable?

When the technology, the business logic and the knowledge sit with a handful of people, modernisation planning first creates transparency about what actually has to be done, and a robust basis for the internal decision.

Need to modernise an important process without triggering an uncontrollable programme?

We sort out the problem, the risks and the routes to a solution, and build the basis on which you can defend the next modernisation step internally.

Who this approach is for

When this approach works well

  • There is a specific business process or an established business application.
  • The pressure is real.
  • Someone in the business owns the topic.
  • Users and knowledge holders can be involved.
  • There is willingness to change.
  • The next step is meant to be justified in the business and internally.

This approach does not fit when …

  • only a small technical repair is wanted
  • the preferred solution is already fixed beyond discussion
  • no users or knowledge holders may be involved
  • there is no internal owner
  • only a free solution concept is expected
  • only a price for a predetermined delivery is needed

For your internal alignment

Stages, results and prices at a glance

Download the compact overview of the Path to Successful Modernisation. It sets out the three planning stages, their target states, what each includes and what each costs — ready to pass on to managers, budget holders or purchasing.

  • all three planning stages at a glance
  • what is included, and transparent prices
  • a basis for internal alignment

Frequent questions

Questions about the Path to Successful Modernisation

What does modernisation planning cost?

The three planning stages are priced individually: Clarity €3,000 plus VAT, Direction €7,500 plus VAT, Alignment €12,500 plus VAT. Each later stage includes the one before it, so the amount named is the full price of that stage and not a surcharge.

Do I have to begin with Clarity?

No. If a robust view of the current state already exists, you can begin directly with Direction or Alignment.

Which stage fits my situation?

That depends on how far the decision has already come: Clarity builds a robust view of the current state, Direction leads to readiness for decision, Alignment prepares the chosen path for internal alignment. In a 20-minute conversation we work out together which stage your situation actually needs.

See the Planning Stages

Can I pass the results on internally?

Yes. The results are meant for internal alignment and can be passed on to managers, IT, governance and budget holders. For the alignment that happens before you commission anything, the service overview is ready — it sets out the three planning stages, what each includes and what each costs.

Does a technical solution have to be decided already?

No. The path exists precisely to avoid premature technology decisions. Which solution makes sense follows from understanding the problem and the target state.

Is the path suitable for a single line-of-business application?

Yes. What matters is that the application supports a business-relevant process and that the situation cannot be solved by an isolated technical repair.

Who should be involved internally?

At minimum the person accountable in the business, plus people who know the actual workflow and the application. Further roles from IT, governance or management are involved depending on the situation.

Do we receive a finished requirements specification?

No. You receive a robust basis for decision-making and modernisation. A detailed specification written before the problem is sufficiently clear would fix the solution too early.

Does Agile-IS have to carry out the implementation afterwards?

No. The results form a basis for decisions you can use independently. If Agile-IS does take on the implementation, work can continue without repeating the fundamental clarification.

What happens after the Alignment stage?

It ends with a specific, aligned modernisation path. That can be targeted stabilisation, step-by-step modernisation, a migration, a new application, or an organisational change first. Implementation is then the modernisation itself.