Support or project? How IT work gets scoped and quoted

The basic distinction

Support is maintenance of what already exists. Fixing a laptop that will not start, resetting a password, adjusting a mailbox permission, clearing a stuck print queue or applying security updates all keep your current systems working as they should. These tasks are what a monthly plan is designed to cover, and most take minutes or hours rather than days.

A project changes your environment in a planned way. Moving email from one system to another, installing a new firewall, replacing a server, setting up a new office network, deploying a new phone system or rolling out laptops to the whole team are all projects. They need planning, often involve downtime that must be scheduled, and carry more risk than everyday requests.

The grey areas

Some work sits in between. A single new laptop for a new starter might be routine support with one provider and a small billable task with another. Updating firewall rules for a new software system could be either, depending on how much is involved. Adding a few Wi-Fi access points might be treated as a minor change or a small project.

Good providers set out their approach clearly, often with a threshold such as work expected to take more than a few hours, or work that introduces new equipment or systems. Ask for examples during onboarding so that both sides agree in advance. Surprises usually come from these grey areas, not from the obvious projects that everyone expects to see quoted.

What a good project quote contains

A project quote should describe the goal, the work to be done, what is included and excluded, the equipment and licences required, the expected timeline, any downtime and who needs to do what on your side. It should state the price, whether it is fixed or an estimate, and what assumptions it relies on, such as existing cabling being usable or a vendor providing access on time.

Assumptions matter more than people expect. If a quote assumes your current network cabling is in good condition and it turns out not to be, the price will change. Reading the assumptions carefully, and asking how likely each is to hold, gives you a realistic sense of where the final cost might land and where risk sits.

Fixed price or time and materials

Fixed-price projects give you certainty: the provider agrees a price for a defined scope and absorbs the risk of the work taking longer. They suit projects with a clear, stable scope, such as installing a new firewall or setting up a standard office network. Expect the price to include some margin for that risk, which is a fair trade for knowing the total before you commit.

Time and materials pricing charges for the actual hours and equipment used, often against an estimate. It suits projects where the scope is uncertain, such as untangling an undocumented old system. Ask for a cap or regular updates against the estimate so costs do not drift without you knowing. Some projects combine both, with a fixed price for the known work and hourly rates for anything discovered along the way.

Managing changes once work starts

Most projects change somewhat once work starts. You might decide to add a meeting room to the network upgrade, or discover that an old application needs special handling during a migration. Agree a simple change process at the start: the provider describes the change, its cost and its effect on timing, and you approve it in writing before the extra work begins.

This protects both sides. You avoid an unexpected bill at the end, and the provider avoids disputes about work they did in good faith. A short email exchange is usually enough. The key is that nothing outside the original scope is billed without your agreement first, and that every approved change is added to the project record so the final invoice is easy to check.

Keeping projects on track

Nominate one person in your business as the contact for each project, with authority to make decisions. Ask for brief regular updates, even a weekly email, covering progress, issues and next steps. Plan downtime for quiet periods, and give staff notice of anything that will affect their work, such as a weekend migration or a new sign-in process on Monday morning.

When the project finishes, ask for a short handover: what was done, what changed, updated documentation and any follow-up tasks. A brief review afterwards, covering what went well and what could improve, makes the next project smoother and helps your provider understand how your business prefers to work. Keep the documentation with the rest of your IT records.