IT documentation

IT documentation and infrastructure map

We inventory your IT infrastructure, document critical systems, map risks and deliver a clear report that shows what exists, what is risky and what should be fixed first.

Problem

Without documentation, every incident starts by searching for basic answers.

The goal is an operational view of the system that decision makers and responsible people can use when action is required.

The company does not know who has admin access.
Domains, DNS, hosting and email are undocumented.
Backups exist, but restore has not been verified.
Former employees may still have access.
There is no network map.
Everything depends on one person.
There is no procedure for outages.
Risks are not ranked by business impact.

Deliverables

You receive a system map, risk register and order of priorities.

The scope follows the real infrastructure: users, locations, servers, cloud services and critical applications.

01

Server, device and service inventory

See which systems are in use, where they are located and who is responsible for them.

02

Infrastructure map

Connect locations, networks, servers, cloud services and critical dependencies.

03

Domains, DNS, hosting and email review

Identify ownership and the points where one mistake could interrupt communication.

04

Google Workspace / Microsoft 365 review

Review account organization, administrative access and baseline security settings.

05

Backup and restore review

Check what is copied, where it is stored and whether a realistic recovery plan exists.

06

Baseline security review

Map MFA, access, firewall, devices and obvious sources of unnecessary risk.

07

Risk register

Separate risks by likelihood, business impact and remediation priority.

08

PDF report

Deliver an overview that can support decisions, planning and internal records.

09

Recommendations and priorities

Define the order of work: urgent, important and planned, without random spending.

Process

The review is structured. The output is useful to both technical teams and management.

We introduce visibility first. Only then do we propose interventions, migrations or a maintenance model.

01

Initial call

02

Information gathering

03

Technical review

04

Infrastructure map

05

Risk register

06

PDF report

07

Maintenance proposal

Not included

The assessment is clearly separated from ongoing support and larger interventions.

  • Support during agreed business hours is not included in this service.
  • 24/7 availability is provided only through a separate SLA agreement.
  • Urgent interventions and work outside business hours are agreed separately.
  • Migrations are not included.
  • Deep penetration testing is not included.
  • Ongoing maintenance is agreed separately.

Important

The report does not become shelfware.

Recommendations are separated into urgent, important and planned actions, so the next investment starts with actual risk.

Starting price

The final offer depends on scope, but the starting point should be clear.

We confirm the scope after a short discussion about users, locations, servers and critical services.

IT documentation and infrastructure map

from €250 one-time

Starting scope for the infrastructure, access, backup and business service review.

Complex infrastructure

custom offer

Multiple locations, servers, network segments or critical applications require a precisely defined scope.

Documentation + maintenance

custom offer

Connect the documentation with a realistic monthly maintenance and responsibility plan.

EUR pricing for international inquiries. For Serbian resident companies, invoicing and payment are performed in RSD in accordance with the issued offer and invoice.

FAQ

Common questions before the review starts.

Do you store our passwords?

We document where access is managed, who is responsible and how access can be recovered. Passwords are not placed in the PDF report. If centralized storage is needed, we recommend a suitable password manager and access policy.

Do you fix issues during the documentation process?

Small corrections can be identified and handled by agreement. Larger interventions, migrations and urgent work are scoped separately so the assessment and the implementation remain clear.

How long does the documentation take?

For a small company, typically a few business days after the required information is collected. For multiple locations, servers or more complex services, we confirm the timeline after the initial call.

Can this be the start of monthly maintenance?

Yes. Documentation is a good starting point because it defines what exists, what is risky and which maintenance level makes sense for the company.

Do we receive a PDF report?

Yes. You receive a clear PDF report with an infrastructure overview, risk register, priorities and recommended next steps.

First step

Send the basic information about the company and the systems you use.

We reply with a realistic review scope, delivery model and next step.

Request an IT review