+32 473 52 49 31Mon–Fri · 08:30–18:00
Prefer to talk it through first? Just give us a call.
Make IT So
Make IT So · DIGITAL AUDIT

An honest picture: where you stand and what to do next.

You feel something isn't right with your digital landscape, but you can't get a straight answer. Or you know a big decision is coming and first want to know, independently, whether the current foundations can take it. Within two to four weeks at most, we get a clear picture together.

Duration
2 to 4 weeks max
Deliverable
One page + appendix
First conversation
30 min, no obligation
01 · Sound familiar?

You know something is or isn't right. But not what.

Three of the moments when companies call us for an audit. If one of them sounds familiar, you're in the right place.

A

Your in-house IT says 'it's running', but you have your doubts.

Nobody complains openly, but you notice small things always take too long. Getting a new employee started takes a week. Running a report is a ritual involving three systems. You want to know whether that's structural, and what it would cost to do things differently.

B

You're facing a big investment and first want to know whether the foundations hold.

A supplier proposes a new platform, or the accountant is pushing to replace the ERPEén systeem dat je kernprocessen zoals voorraad, boekhouding en orders samenbrengt.. Before you sign, you want to know whether your current architecture, processes and team can handle it. Not what the supplier thinks. An independent view.

C

Someone is leaving and you don't know what knowledge they're taking with them.

Your IT lead is retiring, or your regular freelancer is calling it a day. What's in their head that isn't documented anywhere? An audit brings that silent knowledge to light before it's too late.

What we examine

Four places where it usually goes wrong.

We first understand how your company works, then look specifically for where risk is building up.

Data

What's where, who has access, and is it still correct? Duplicate sources and islands of Excel make it unclear.

QualityOwnershipBackup

Processes

Do your systems still fit how your business really works? We look at where work gets stuck: manual steps, double entry, and tasks left lying because nobody owns them.

Lead timeManual workOwnership

Integrations

Integrations are often the weakest link: more fragile than people think, and sometimes built by someone who has since left.

IntegrationsDependencies

Architecture

Does the structure still fit where you want to go, or are you building on foundations that can no longer take the load?

ScalabilityMaintenance

Take our free quickscan first. 10 minutes.

Walter Swaenepoel
Walter Swaenepoel
Does the audit in person
02 · How an audit runs

Three weeks. One clear report.

First look. Then test. Then deliver. No talk of formal methodologies, but a structured diagnosis you can keep using yourself afterwards.

Week 1

What's connected to what?

We map what you have: systems, suppliers, integrations, people with access, running contracts. Not an inventory of tools for its own sake. We look specifically at where problems typically arise: at the handovers between systems, people or parties.

Week 2

What do we see when we look?

We talk to your people, read logs and config files where that makes sense, and look at concrete figures (uptime, response times, ticket volumes where available). No penetration test, no security audit at that level (others do that better). But an honest look at architecture, processes and organisational risk.

Week 3

What would you do next?

We distil it into 3 to 5 findings and 2 to 3 scenarios for what you could do now. Not a list of 47 'recommendations' nobody can act on. Instead: what has priority, what costs order-of-magnitude X, and what can wait without breaking anything.

End of week 3

Working session + one page

Finally we schedule two hours with you and whoever you want to bring. We go through the findings, answer questions and adjust where needed. The document is yours. You can reuse it in board meetings or in conversations with partners.

03 · During the audit

What we do. What you do.

An audit only works if both sides deliver. Being clear up front about who carries what avoids frustration halfway through.

What we do

The diagnostic work you don't have the time or distance for.

  • Interviews + observationWe plan and hold the conversations with your people and partners. Where it helps, we sit next to someone from your team to see how the work actually gets done.
  • Reading documentation + logsExisting contracts, configs, integration documentation, ticket history where available. In all of these sources we look for patterns that nobody inside notices any more, out of habit.
  • Findings + scenarios on one pageWe write one version of the truth, understandable for management and for IT alike.

What you do

Work only you or your team can do.

  • Arranging access + making introductionsWe need read access to systems and introductions to key people. Not full admin, but enough to look concretely.
  • Time for 2 conversations + the closing sessionOne intake conversation up front, one interim check-in (~week 2), one working session at the end. Count on 5 to 8 hours of your own time over 3 weeks.
Sample from the report

Each finding with its severity, and what it means.

No technical dictionary. For each finding you read how serious it is, what it means in plain language, and which area it affects.

Hoog risico
One person keeps the integrations running Custom work without documentation: if that person drops out, the integration stops.
Integrations
Hoog risico
Backups are made, but never tested A backup you've never restored is an assumption, not a certainty.
Data, Security
Middel
Old accounts are still open From people who have left and former partners, with access nobody follows up any more.
Security
Middel
Customer data lives in three places ERP, accounting and Excel, with differences between the three.
Data
Laag
The architecture is healthier than expected Good news belongs in the report too, so you know what you don't need to touch.
Architecture
Walter Swaenepoel
Walter · on where the problem really lies

I read the logs nobody else reads. That's usually where the real story is, not in the slides you're shown.

04 · What an audit delivers

Three weeks later: finally a grip on the IT situation.

A service SME wondered whether its current IT architecture could handle its customer base doubling. We delivered our findings and 3 scenarios in 3 weeks. On that basis, management could decide to postpone or go ahead with the planned investment. No more supplier pressure.

ServicesBefore the investment3 weeks
“We thought the system was our problem. After the audit, it turned out the processes around it were the real risk. No supplier would have told us that, because it doesn't cost them a customer. Walter and Jan did.”
Service SME
Managing director
05 · Frequently asked questions

What clients ask before they sign.

Missing one? Call or email. We answer without a sales pitch.

Another question? Call us for half an hour

What's the difference between your audit and a security audit?

A security audit digs deep into one layer (network, application vulnerabilities, penetration tests). Our audit looks wider and less deep: architecture, processes, team composition, organisational risk. For security depth, others do it better. For 'is the picture in my head right?', we do it better.

Do we get a list of technical recommendations?

No. You get 3 to 5 findings (what we saw) plus 2 to 3 scenarios (what you can do about it). Not a 47-point list you then have to prioritise. We don't have that context; you do. We make the decision work lighter, not heavier.

What if the audit shows everything is in order?

Then that goes in the report in black and white too. No culture of 'we found something after all to justify the invoice'. Sometimes the most important result is that you now know, with data, that your current setup is good enough for the next 12 to 24 months.

Do you come and fix the problems yourselves?

That depends on the scenario. If the outcome calls for project management or turning it into an implementation, we can possibly take that on (see programme management). If the outcome is that your current partner can solve it themselves, we hand over the report and leave the rest of the delivery to them. No vendor lock-in.

Do you work at a fixed price or by the hour?

Fixed price per scope. In the first conversation we decide together whether it's a light audit (2 weeks) or a broader one (4 weeks max) and give you a fixed price. No surprises afterwards.

What do you do with sensitive information we share?

We sign an NDA before we start if your situation calls for it. Documents and interview notes stay with us until the end of the engagement and are then destroyed, except what ends up in your page and appendix. No 'we keep everything in our database for future insight'.

We guide the delivery, or not. Your choice.

Walter Swaenepoel
Walter Swaenepoel
Calls you back in person