Services

Technology advisory

An analysis of the process and the systems that support it, ending with a recommendation: reorganise the process, connect the systems or build a new one. Also when the conclusion is ‘do not build yet’.

Let's talk about your project See the work

Scopes

Scopes of this service

  1. Systems diagnosis and review

    A description of what your systems do today, what slows work down and what can be put to use, ending with a scope recommendation on which you can base the implementation decision.

    See the scope
  2. Technology strategy

    A direction for the company's systems over several years, written so that the board knows which systems stay, which are replaced, in what order and what it pays for.

    See the scope
  3. Feasibility study

    An answer before a large expense: whether the planned system or automation can be built in the assumed time and budget, on what data and with what constraints.

    See the scope
  4. Technology due diligence

    A report on the state of the systems, code, data, licences and IT team of the company you are buying, with the risks and the cost of putting things in order, before the deal is signed.

    See the scope
  5. Step-by-step implementation plan

    Implementation stages arranged so that each one ends with something that works in the company, with the people on your side, the board's decisions and the conditions for moving to the next.

    See the scope

Situations

What clients come to us with

A process the rest of the company waits for

An order, an application or a settlement stalls on one person and on data retyped by hand. Sales and finance wait, and the cost of that waiting appears in no report.

Every company in the group works differently

The same work follows a different path and a different tool in each company. Each company keeps its own staff to handle it, and comparing results means assembling data by hand.

Unclear whether to change the process or the system

Work moves too slowly and everyone can see it, but nobody knows whether to change the way of working or the tool. The spending decision is waiting for an independent assessment.

Scope

What we do

  1. Process map

    With the people who run the process, we write down who does what, in which system and how long it takes. The result is a map of the places where work waits or is done twice.

  2. Review of the systems already in use

    Before anyone proposes a new system, we look inside the ones you have: data, connections, limitations. The result is a description of the current state: what can be reused, what should be replaced and what only needs different settings.

  3. Recommendation with a scope

    We compare three options on cost, time and risk: reorganising the process, connecting the systems or building a new one. The result is a recommendation of one option with a scope of work and an order of stages. It is the basis for the implementation offer with a team, schedule and price.

  4. New process flow

    When the recommendation is ‘do not build yet’, we write down the new process flow: who does what and in what order. The result is a process description to put into practice without a new system.

Technologies and standards: ERP and CRM systems, Jira and Azure; we describe processes in BPMN and Visio.

Outcome

What you get

  • A process map showing where work stalls and where it is done twice
  • A description of the current state of the systems with a list of limitations
  • A recommendation with a scope of work and an order of stages
  • A description of the new process flow without a new system

Process

How the work proceeds

  1. We talk to people and check the systems

    The people who carry out the process and are responsible for it show us the work day by day; in the systems we check the data and connections. Result: a list of places where work stalls and a description of the current state.

  2. We compare the options

    We set the cost, time and risk of the three options side by side in one table. Result: a recommendation of one option with a justification the management board can assess without help from the IT department.

  3. We hand over the recommendation

    We discuss the recommendation with you and the management board; you know the scope, deadline and price of the analysis before it starts. If you order the implementation, the founders lead it personally and stay with the system after launch. Result: the scope and order of stages as the basis for the offer.

Regulations

Regulations and scope limits

If your company is subject to the Polish National Cybersecurity System Act (KSC) or runs an information security management system, the recommendation takes these requirements into account from the start: where the data sits, who has access to it and how incidents are handled. A review of supplier contracts can be included in the scope of the analysis.

What we don't do

  • Penetration testing and round-the-clock security monitoring (SOC).
  • Legal opinions: these are issued by the law firm we work with.

Work

Team experience in this area

Situation

The companies of a banking group handled tickets and tasks by their own rules, with no common standard.

What the team did

Our team agreed a common way of working with the companies, translated it into the tool's configuration and rolled it out across the group.

Outcome

The whole group works in one tool to one standard, so tickets and tasks from every company are visible and reported in one place.

How we start

  1. A conversation about the problem

    You describe the process or system that no longer keeps up and what has to change. The conversation costs nothing.

  2. Analysis under an NDA

    We examine the process and the systems and hand over a recommendation with a scope of work. You know the scope, deadline and price of the analysis before it starts.

  3. Offer

    You receive the scope, team, schedule and price of the implementation. You decide whether we go ahead.

The cost of the analysis is credited towards the implementation if you order it.

Let's talk about your project

Phone: +48 455 406 404 E-mail: contact@aliaxit.com

© 2026 ALIAX IT sp. z o.o. · ul. Boczna 28, 64-115 Wilkowice · KRS 0001102190 · NIP 6972399808 Privacy policy ·