Technology transformation

The requirements definition for an ERP system is one of the most critical phases of the project, as it determines what the future solution must enable, what is expected from the vendor — and what the overall scope includes or excludes. We lead a business‑driven workshop model where requirements are clearly prioritized and documented.

Selecting and tendering an ERP system is often a significant investment — and one of the most risk‑prone phases of the entire project. When done well, it saves money, time and frustration; when done poorly, it can lead to years of pain, business risks and unpredictable costs. We help ensure that the request for proposal and comparison criteria are clear and comparable, that market dialogue and information requests support the right requirements, and that the final selection and contract negotiations lead to a cost‑effective solution and a vendor that fits your processes and organizational culture.

A carefully prepared procurement contract — including its appendices — is the foundation of successful collaboration in both private and public procurement. Yet it often ends up playing a secondary role during requirements definition and tendering, even though the contract itself ultimately defines the rules for the entire future cooperation. We step in to ensure that the contract structure and appendices are clear, the terms are aligned with the tender and the chosen delivery model, and that the contract becomes a practical tool for day‑to‑day governance rather than merely a signed document.