IT Consulting & Audit

Your IT problem is not the budget. It is the order of priorities.

IT audit and consulting for Algerian companies

You spend on IT without knowing whether the money goes to the right place. We lay out your information system as it stands, say what needs to change and in what order, then cost the next steps with you.

  • A factual review of what exists today
  • Priorities ranked by risk and by gain
  • A budget and a schedule before any commitment

Interactive demo

An audit does not deliver a list of problems. It delivers an order of work.

Here are eight findings we often come across. Keep the ones that look like your situation: each one takes its place on the matrix according to its risk and the effort it requires, and the roadmap builds itself alongside.

Findings

Click a finding to add it or remove it.

Examples

Priority matrix

Why this ranking

Backups never tested

High riskLimited effortDo first

The backup runs every night, but nobody has ever attempted a restore. The risk is high and checking takes little: one restore test is enough to know.

Roadmap

  1. 1

    First

    2 / 3

    High risk, limited effort. We fix it without waiting.

    • 1Backups never tested
    • 2Guest Wi-Fi not isolated
  2. 2

    Next

    1 / 4

    The projects to budget, and the simple fixes that slot in between.

    • 3End-of-life server
  3. 3

    Later

    1 / 1

    Useful, but nothing is pressing. To pick up once the rest is done.

    • 4Licences nobody tracks

Order of work

2First1Next1Later

Findings kept: 4 of 8

This is what you receive at the end of an audit: not the list of what is wrong, but what to deal with, and in what order. The costing comes next, step by step.

Simplified example, for illustration only. The risk and effort levels are set in advance for this demonstration. In a real audit, each finding is rated in the context of your company: its business, its constraints, its means. Your selections stay in your browser.

What we see

What we find in most companies

  1. Projects launched without an overall view

    One piece of software per need, one provider per piece of software. After a few years, nobody can say what is running, or why.

  2. A provider chosen on price

    The cheapest bid wins, the scope is vague, and the project ends up costing far more than the bid that was turned down.

  3. Invisible technical debt

    End-of-life servers, backups never tested, licences nobody tracks. Nothing shows, until the day something fails.

  4. An IT manager alone with everything

    Support, network, security, projects: one person carries it all, with no time to step back.

Our method

How an audit and consulting engagement works

The engagement is short, clearly scoped, and ends with a document you can use without us.

  1. 1Listening to management and business teamsWe start with your objectives: growth, opening a site, a regulatory constraint. IT is judged against them, not in the abstract.
  2. 2Technical reviewAn inventory of equipment, applications, licences, backups and contracts. We look at what is really in place, not at what is supposed to be.
  3. 3Risk and cost analysisEvery finding is ranked: what threatens the business, what costs too much, what can wait.
  4. 4Costed roadmapYou receive a step-by-step plan with an order of priority, an estimated budget and a realistic schedule. You can entrust it to whoever you choose.

Deliverables

What you receive at the end of the engagement

  • A map of your information system: hardware, applications, data flows, contracts
  • An audit report that non-technical management can read
  • The list of risks ranked by severity, with the measure to take for each
  • An IT master plan broken into stages, from the immediate measure to long-term work
  • A budget framework to prepare your supplier consultations and your decisions

Who it is for

This engagement is for you if

  • You run a company of 50 to 500 employees without a structured IT department
  • You are preparing a major investment: ERP, cloud migration, new site
  • You have just been through an incident or a failed project and want to understand why
  • You are an IT manager and need an outside view to convince your management
Discuss your project

Take stock

Where does your information system stand?

Six questions, two minutes. Your answers stay in your browser and are not sent anywhere.

Question 1 of 6

Do you have an up-to-date inventory of your equipment, software and licences?

Why Gnosis

What you get by working with us

Advice independent of vendors

We are not tied to any software vendor or hardware manufacturer. The recommendation starts from your need, not from a catalogue.

A written scope before any commitment

Scope, priorities, budget and schedule are set down in writing before the first day of implementation.

Local delivery, by a team in Algiers

A team based in Algiers that knows the country's regulatory, human and infrastructure constraints.

Straight talk on what is feasible

If a project does not have the means to succeed, we say so before it starts.

Frequently asked questions

What we are asked before we start

How long does an IT audit take?

It depends on the number of sites, the number of applications and the availability of your teams. The duration is set in writing at the scoping stage, with the report delivery date, before work starts.

Does the business have to stop during the audit?

No. The audit relies on interviews, data collection and read-only access. We do not make changes to your production systems during this phase.

Are you tied to a software vendor or a manufacturer?

No. We are not the exclusive reseller of any brand. If an open-source solution or a tool you already own is enough, that is what we recommend.

What happens after the roadmap is delivered?

You decide. You can run the projects in-house, entrust them to other providers or ask us to take them on. The roadmap is written to be usable without us.

Further reading

Our articles on the subject

Know where your IT budget is going

Describe your situation in a few lines. We will reply with the questions to settle first.

Discuss your project