IT audit
What you were actually sold
An independent check of what the business runs on: the code and the platform, the server and the backups, the CRM and the registers — and who really holds the domain, the hosting and the access. The result is a written report: what is sound, what is at risk, and what to fix first.
- 88
- projects delivered
- 19
- years in development
- 25
- systems implemented
The reasons
When to check
The vendor is leaving — or gone
The developer has stopped answering, or you are parting on good terms. The audit shows what you are getting into your hands and what the handover is missing.
Nobody knows what was delivered
The site works, the invoices are paid, and what is inside is known only to whoever built it. The report moves that knowledge to you.
After an incident
A break-in, lost data, a site down on the wrong day. The review answers how it became possible and what to close so it does not repeat.
Before a purchase
You are buying a ready-made site, or a business together with one. A check before the deal is cheaper than surprises after it.
The estate has grown
A site, a CRM, registers, mail — and nobody sees the whole picture. The audit gathers it into one document.
The scope
Four layers of the check
Code and platform
The state of the CMS or the framework, the discipline of updates, the quality of custom work, the speed. Not the aesthetics of the code but the risks: what breaks on the next update and what already holds on a promise.
Security and backups
Vulnerabilities, passwords and staff access, whether copies exist — and whether they have ever been restored. A backup that has never been restored does not count as a tested one.
Server and ownership
Where the site lives and what state the server is in; who the domain, the hosting and the admin access are registered to. If everything is in the vendor's name, the business runs on somebody else's property — and the report says so in plain words.
Systems and services
The CRM, the registers and fiscal devices, the mail, the integrations between them. What is connected, what is typed in by hand, and where data lives in a single copy with no backup.
The order
Three steps to the report
The access
The list of required access arrives before the start. What exists, you hand over; what cannot be found is already the first finding of the check.
The check
Each layer is walked through a method: code, server, copies, access, systems. Nothing is changed or fixed along the way — only recorded.
The report
A written document: what is sound, what is at risk, what to fix first. Ordered by priority, in human language, with each finding weighed.
Plans
Two depths of checking
For the site and the access
Express
$500
The core risks in a short run: the site, its server, and who all of it belongs to.
- The site and its platform
- Domain, hosting and admin access
- Backups and their restorability
- A written report with priorities
For the whole estate
Full
$1,000
The whole picture at once — from the code to the registers, with a work plan for every layer.
- Everything in Express
- The server and the infrastructure in full
- CRM, registers, mail and their integrations
- Data flows and manual entry
- A report with a prioritised work plan
The date is named before the start, after the scope is weighed, and does not drift along the way. This is a one-off piece of work, not a retainer — IT consulting in the shape of a check with a document at the end. Talking the task over costs nothing; the paid work is the check with the written report.
Questions
Before you write in
Start
Fill in the brief
Naming the site and saying what worries you is enough. The conversation costs nothing; after it — which plan fits and what date is realistic.