IT infrastructure
What to gather before an infrastructure conversation
A short list of facts that make a network, server, or cloud discussion useful.
· 1 min read · Neturon
An infrastructure conversation goes faster when the current environment is described in plain terms: how many sites, whether servers are on premises or with a hosting provider, and which applications people cannot lose.
What to have to hand
You do not need a full inventory on the first call. A sketch of the network, the names of the main systems, and a note of what is failing or due for replacement is enough to decide whether the work is design, support, or a migration.
- Number of sites and roughly how many people work at each.
- Where servers and data live today: office, data centre or cloud.
- The applications that would stop the business if they failed.
- How backups are taken, and when a restore was last tested.
- Who currently supports the environment, and any contracts that are ending.
Be clear about the constraint
Neturon does not assume a particular cloud vendor or a certification. Say which platforms you already use, and the recommendation can stay inside that constraint.
Related service
IT Infrastructure & Technical Support
If this matches a piece of work you are planning, tell us about it and we will suggest a sensible first step.
General guidance only. It is not legal, financial or regulatory advice, and it does not describe the results of any client project.
More insights
Data protection
Building UK GDPR into a business system from the start
The data protection features to specify at the beginning, rather than add later.
AI solutions
Getting ready for AI: start with one task and your data
A practical way to choose a first AI use case, check your data and keep people in control.
Open-source software
Open source, off-the-shelf or custom: choosing with eyes open
How to compare licences, support, ownership and running costs before you choose.
