Do you need a regular pair of eyes or a defined change?

01 / In practice

Begin with what keeps recurring.

If the same kinds of questions keep arriving, nobody owns maintenance and you regularly coordinate several suppliers, an ongoing support arrangement may be worth discussing. It gives repeated tasks and supported systems an agreed home.

If you need a particular result, such as replacing equipment, moving email or reviewing a network, a project may be the clearer starting point. It has a defined scope and a finish line, even if it later reveals a need for ongoing care.

02 / In practice

Ask four useful questions.

The answers matter more than the name of the service.

• Is the need recurring, or is there a specific change to complete?
• Which people and systems are affected?
• Who currently owns routine care and supplier coordination?
• What result would make the work feel complete?

03 / In practice

What an ongoing agreement should explain.

Look for a clear description of supported users, devices, services and contact routes. Availability and response arrangements should be explicit. Monitoring, routine administration, maintenance and human support are different activities; understand which are included.

Look for a clear explanation of how larger changes are handled. A migration, new installation or specialist application project may need its own plan and quotation alongside routine support.

04 / In practice

What a project should explain.

A project proposal should describe the current position, intended outcome and included work. It should identify access requirements, supplier dependencies, likely interruption and the checks needed afterwards. Hardware, licences and third-party charges should be visible.

When the starting point is unclear, discovery can be a useful first project. It should produce findings, options and priorities that let you decide what to do next.

05 / In practice

Sometimes the right answer is both.

An untidy environment may need a remedial project before routine support can begin on a sound basis. Equally, an ongoing customer may need a separate project when the business moves office or changes its core application.

You can explain the problem before choosing a model. The conversation should help establish the shape of work, not force you to diagnose the environment or select a technical bundle unaided.