Skip to content

535 040 361511 275 531

Book an IT review

Map the process first, then automate and choose a system.

Before you buy a tool, let's find out where your business really loses time. The audit ends with a list of processes to change, estimated savings and a plan for the year ahead.

Three ways in, depending on what you want to know.

  • Free IT review

    PLN 0 60 minutes online

    Backups, network, access and security. A three-priority scorecard.

    Details
  • Process mapping

    from PLN 1,800 1-3 days

    For a business that knows which process hurts and wants to map it before automating it or implementing a system.

    3-process package: PLN 4,500; 5-process package: PLN 7,000.

  • Operational audit

    from PLN 3,500 2-5 days

    For a business that wants to know what to automate and what it will save before buying anything.

    Businesses with over 50 employees: from PLN 6,000.

Net prices.

How the operational audit works.

Three stages, from talking to your people to a plan you can present to the management board.

  1. Interviews with managers and staff, observing processes in action, an inventory of the tools in use.
  2. Diagrams of key processes, identification of manual work, measurement of time spent and bottlenecks.
  3. Digital maturity assessment on a 1-5 scale, a prioritised list of processes to automate, the estimated return on each recommendation and a 6-12 month plan.

What you get at the end.

  • PDF report
  • editable process diagrams
  • priority matrix
  • savings estimates
  • presentation for the management board

IT audit or process audit? First, the right question.

Both begin with a conversation, but end with a different kind of decision.

The infrastructure audit answers questions about backups, accounts, updates, network, servers and security features. The operational audit shall monitor the flow of information and work between people and systems. It shows where the data is prescribed, the decisions are waiting for a message, and the report depends on one person.

If the problem is downtime, lack of documentation or uncertainty as to whether the data can be restored, we start with infrastructure. If the company works but wastes time on manual activities and inconsistent sheets, it is appropriate to map the process. When both areas merge, we separate them in the report and do not sell one broad audit without borders.

How to prepare a company, to make the audit a useful result.

There is no need to create documentation specifically for the auditor. You need people who know work in practice.

Before starting, we determine the sponsor on the company's side, owners of the processes investigated and people performing daily activities. We ask for examples of forms, reports, exports or anonymous documents if they are needed to understand the flow. Technical access is provided only if it comes from an agreed scope.

The most values are real cases: order except, invoice correction, lack of data in the report or task that returns between departments. We don't judge employees. We're looking for places where the process forces manual bypasses, doesn't show the owner or leaves a trail to determine the state of the case.

Priorities after the audit, Not a wish list without order.

Each recommendation is assessed in terms of impact, risk, cost and readiness of the organisation.

First, we separate the actions required to reduce significant risks from improvements that save time. Then we point out the dependency: automation should not precede the order of the data, and the new desktop BI will not solve the dispute over the definition of the indicator. The plan shows the order and the responsible, not just the tool names.

The estimate of benefits is based on observation and data provided by the company. If there is no reliable measurement of the starting state, we save the assumption and method of checking it. We do not declare a percentage of savings or return on investment without grounds. The recommendation may also read: not automate, but simplify the procedure.

What happens to the report, When you don't choose NexaIT to implement.

The materials are created so that a decision can be made and the work transferred to any contractor.

The report, diagrams and priority matrix are sent to the client in an agreed format. We describe the current state, the proposed course, exceptions, owners and reception criteria. Passwords and other access data do not enter the report; we store them and transmit them in accordance with a separate security procedure.

You can implement the recommendations yourself, with the current supplier or with NexaIT. If we are preparing an implementation offer, it is a separate document with scope, schedule, responsibility and price. The audit shall not create an obligation to order the next stage and shall not hide the cost of implementation in the general wording.

Confidentiality and access, only to an agreed extent.

Conversations, demonstrations of work and anonymous examples are often sufficient to map the process.

Before the audit, we indicate the data we really need, the way they are transmitted and the persons entitled to access. We do not copy the entire harvest “just in case”. If the analysis requires personal data, commercial information or administrative access, we set the basis, safeguards and deadline for removal of working materials.

In the report we use descriptions needed for decisions, without passwords and secrets. Examples can be anonymised. Those participating in interviews know what the purpose of the interview is and the owner of the process approves a map of the current state before preparing a recommendation. This confirmation reduces the risk of designing a solution based on a incomplete image.

If the audit reveals an urgent risk, we will inform about it immediately instead of waiting for the final report. However, the corrective action needs to be agreed separately unless it has previously been included in the scope. This preserves the separation between independent diagnosis and the implementation of the proposed solution in writing.

Questions about the audit.

What is the difference between an audit and a free IT review?

The review is one hour online with an engineer that highlights the three biggest IT risks: backups, network, access and security. The operational audit takes several days and is about processes: where time is lost, what to automate and what it will save.

Does the audit cover IT security?

The operational audit focuses on processes and automation. We cover the security basics in the free IT review, and a full security audit is quoted separately once we have discussed the scope.

Do we then have to order the implementation from you?

No. The report, diagrams and priority matrix are yours. You can implement the recommendations yourself, with us or with another company.

How much of our employees' time will it take?

Mostly during interviews and work observation, usually an hour or two per person. We do the rest ourselves.

Free · 60 minutes online · no obligation

An IT review, not a sales call.

  1. You talk to an engineerOnline, by video call. Not with a salesperson. We don't install or change anything.
  2. We check 8 areasBackups, access, network, email, server, licences, protection and KSeF readiness.
  3. You get a scorecardThree priorities on one page, emailed after the meeting. Yours to use however you like.

We don't use a contact form. We answer the phone and reply to emails.