Somewhere between about fifty and two hundred people, an estate stops being a collection of computers and starts being infrastructure, and the contract that suited the first shape starts to fail at the second. The change is not technical. It is that things now depend on each other, so a change made without thought breaks something in another department, and nobody notices capacity running out until it has.
Change control is the first thing that has to arrive
At twenty people, somebody makes a change and if it breaks something they fix it. At a hundred and fifty, the same change stops a department that had no idea it was coming. What replaces improvisation is modest: a record of what changed and when, a nominated person who approves anything touching a shared system, a way back, and a window that is not the middle of the working day. Ask a provider what its change process is and to show you last month's change records.
Capacity and lifecycle stop being events
Storage filling, licences running out, warranties expiring and equipment reaching end of support are all predictable a year ahead and all arrive as emergencies when nobody is watching them. Infrastructure management means somebody maintains a forward view: a replacement schedule with dates and costs, renewal dates for every licence and contract, and capacity trends reported before they matter. Ask for that as a named quarterly deliverable, because it is the part that most distinguishes the two contract shapes.
What corporate and enterprise mean in a quote
Usually nothing precise. In this market they are size adjectives rather than product categories, and a provider using them is generally signalling that it serves larger accounts. That is worth knowing in both directions: bench depth and process maturity on one side, and being a small client in a book built for bigger ones on the other. Ask how many clients of your size the provider has and who your account would be handled by, rather than inferring anything from the label.
Documentation becomes an asset
At this size the estate is beyond what any one person holds in their head, so documentation stops being nice and starts being the thing that makes the estate survivable: diagrams, dependencies, who owns each application, what breaks if a given system stops. Insist that it is maintained rather than produced once at onboarding, that it is reviewed at a stated interval, and that it is yours. A provider that keeps your own estate documentation to itself has made leaving expensive by design.
Questions people ask about it infrastructure management services
When does a business need infrastructure management?
When systems depend on each other enough that an unannounced change breaks another department, usually somewhere between fifty and two hundred people.
What should change control look like at this size?
A record of changes, a named approver for anything shared, a rollback plan and a window outside working hours. Ask to see last month's change records.
Do corporate and enterprise mean anything specific?
Not in this market. They signal that a provider serves larger accounts, which is worth asking about directly rather than inferring.
Who should own the estate documentation?
You should, and it should be maintained rather than written once. Ask what the review interval is and what you receive if the contract ends.