Initial Infra · Networks & systems

What keeps yourbusiness moving.What keepsyour businessmoving.

Networks, systems and virtualisation for SMBs.

Explore our expertiseStart the diagnostic

Find the service that fits your needs. View the result without sharing contact details.

Group references

Trusted by

  • Secours populaire français
  • Peugeot Motocycles
  • Entremont
  • SDE76
  • We Fly Trampoline Park
  • DIR Ouest
  • ADM76

02 · Initial Infra in detail

Complete infrastructure for SMBs.

From the first audit to the target architecture, Initial Infra builds a clear, secure and scalable network, systems and open-source foundation.

Where to begin?

One need. A clear scope.

Review your current setup, upgrade your infrastructure or prepare for recovery: choose your starting point.

01

Audit & roadmap

You are unsure what to tackle first.

Work to scope

  • Review of your current setup
  • Risks and dependencies
  • Improvement priorities

What you receive

A summary to help you decide your next steps.

Explore the service
02

Infrastructure project

Your setup needs to evolve with your business.

Work to scope

  • Target architecture and technical choices
  • Migration preparation
  • Checks and documentation

What you receive

Documented infrastructure and an organised handover.

Explore the service
03

Backup & recovery

You cannot afford to lose your tools or data.

Work to scope

  • Data and services to protect
  • Backup policy
  • Restoration and recovery order

What you receive

Procedures to recover your data and restart your tools.

Explore the service

Scope, equipment and recurring costs are detailed in the quote before work begins.

Your business, your constraints

The same IT expertise. Different priorities.

With or without an IT team, your daily operations are the starting point. A few situations to review together.

Find your situation

Professional services

Shared files, staff permissions and remote work: keep documents available to the right people.

Construction & field teams

From the office to the site: organise access to plans and files as your teams move around.

Industry & workshops

Business software, servers and workshop networks: identify dependencies and plan changes around production.

Retail & multiple sites

Connect locations, separate guest Wi-Fi from internal tools and prepare to restore essential services.

The Initial Infra method

01

The assessment

Understand before transforming.

We map the network, systems, access, dependencies and actual risks across the business.

02

The target architecture

Every choice answers a concrete constraint.

Segmentation, identities, hypervisors, backup and open source are designed as one coherent system.

03

Implementation

Deploy without disrupting operations.

Migrations are prepared, sequenced and documented to reduce downtime and preserve a safe rollback path.

04

Handover

Infrastructure the business understands.

Diagrams, access, procedures and decisions remain clear so the system can be maintained and evolve over time.

The Initial Infra method
01
04

The assessment

Understand before transforming.

We map the network, systems, access, dependencies and actual risks across the business.

The target architecture

Every choice answers a concrete constraint.

Segmentation, identities, hypervisors, backup and open source are designed as one coherent system.

Implementation

Deploy without disrupting operations.

Migrations are prepared, sequenced and documented to reduce downtime and preserve a safe rollback path.

Handover

Infrastructure the business understands.

Diagrams, access, procedures and decisions remain clear so the system can be maintained and evolve over time.

Why Initial Infra

Your IT should remain understandable.

You should know what was installed, why, and how to take over. That is part of the project.

Choices explained

Keep, replace or upgrade: options are discussed along with their constraints and costs.

Useful documentation

Diagrams, access rules and procedures guide your team and whoever takes over next.

Recovery prepared

Dependencies, checks and rollback are defined before a migration.

Working with your team

Based in Rouen, we scope the work with your contacts and existing provider, if you have one.

Inside your handover documents

Documents for what comes next.

Understand what is connected.

Firewall
Devices & teams
Servers & applications
Guest Wi-Fi
BackupsSeparate access
Simplified diagram: internal and guest networks are separated. Backups have their own access and retention policy.

Illustrative example · content depends on project scope

Supported environments

Choices depend on your existing setup, your needs and your team.

Identity & collaboration

  • Microsoft 365
  • Active Directory
  • Entra ID

Systems & virtualisation

  • Linux · Debian / Ubuntu
  • Proxmox

Open source tools

  • Nextcloud
  • OnlyOffice

Still unsure where to begin?

The diagnostic suggests a service based on your needs and team size. You can view the result without sharing your contact details, then request a conversation if you wish.

Find my starting point

Customer reviews

Hear it in their own words.

Common questions

Before we begin.

Let’s discuss your situation
Where do I start if I do not know the state of my IT?

Start by reviewing equipment, administrator accounts, business applications, backups and current problems. This helps separate urgent work from improvements that can wait.

Does everything need replacing?

Not necessarily. An audit also identifies what can be kept. Adjusting permissions, network configuration or backups may meet your needs without replacing all the equipment.

Does a migration require downtime?

Some operations require an interruption. Affected applications, the migration window, checks and rollback should be defined in advance. Duration depends on your environment.

Can you work with our IT team or current provider?

A project can focus on a specific scope. Access, responsibilities, change approval and maintenance after handover need to be agreed together.

What should the budget cover?

Costs depend on the number of sites, equipment, licences and migration work. The quote should distinguish project work, any hardware and recurring costs. Scope and exclusions need to be defined before approval.

What documentation should we receive?

Diagrams, an inventory, access rules and operating procedures. For migrations and backups, also plan for verification results and the agreed recovery procedure.

The right starting point

Less noise. More direction.

Come with an idea, a problem or a system already in place. Together, we find where to begin.