How are IT projects charged within an outsourced arrangement?

Within an outsourced IT arrangement, project work is normally charged according to how clearly the work can be defined and how much uncertainty it contains. A well-defined upgrade may be billed at an agreed fixed price, whereas investigative, evolving or user-led work is more commonly billed by time spent. Some projects are also funded from an existing project allowance or service package, provided the contract specifically includes that work.

Fixed-fee projects use an agreed price for a defined outcome. This approach is suitable where the provider can establish the required tasks, technical requirements, dependencies and acceptance criteria before work begins. The quotation should explain what the fee covers, such as planning, configuration, testing, documentation and implementation, rather than describing the project only by its end result.

A fixed fee does not usually mean that every conceivable task is included. The agreement should identify client responsibilities, required access, compatible equipment, third-party charges, implementation conditions and any work that would be treated as a variation. If the agreed requirements change, the provider may issue a revised quotation or variation for approval before carrying out the additional work.

Time-and-materials charging bills for the resources used on the project. Charges may be calculated from recorded engineering time, project management, travel where applicable, equipment, licences or other approved materials. This method is useful when the technical environment needs investigation, the scope is likely to develop, or the project depends on information that cannot be confirmed at the outset.

Time-based work should still be controlled. A sensible arrangement sets out the applicable rates or rate structure, the unit used for billing, how time is recorded, whether work is billed in minimum increments, and how the client is informed if the estimated effort is likely to be exceeded. An estimate is not the same as a fixed price unless the contract expressly says that it is.

Included project work may be covered by the recurring managed service charge where the agreement defines it as part of the service. For example, routine administration or a stated allowance for minor changes may be included, while a major migration, infrastructure redesign or office deployment may remain separately chargeable. The distinction should be documented so that included service activity is not confused with a separately priced project.

Projects are often invoiced in stages rather than as one amount at completion. Common arrangements include:

• an initial invoice when the project is authorised or scheduled;
• progress billing at agreed milestones;
• separate billing for equipment or software when those items are ordered;
• a final invoice after implementation, handover or acceptance; or
• regular invoices for time-based work during the project.

The appropriate schedule depends on the project length, procurement requirements and the amount of work completed at each stage. The quotation should state when invoices will be raised and whether payment is linked to delivery, approval, installation or another measurable event.

Where a project involves hardware, cloud services, software subscriptions or specialist suppliers, these costs should be separated from professional services where possible. This makes it clearer which charges relate to labour and which relate to products or third-party services. It also helps the client identify recurring costs that will continue after the project has finished.

Change control is particularly important in an outsourced arrangement because the provider may be managing several parts of the client’s IT environment under one contract. A change request should describe the requested alteration, its effect on cost and timescale, any technical consequences, and the person authorised to approve it. Work outside the approved scope should not be assumed to be included simply because the provider already manages the environment.

Before agreeing to a project charge, a business should check whether the proposal states:

• the project outcome and measurable acceptance criteria;
• the work included and excluded;
• the pricing method and applicable rates;
• the treatment of equipment, licences, travel and third-party services;
• the assumptions and information on which the estimate relies;
• the invoicing schedule and payment terms;
• the approval process for changes; and
• what happens if the project is delayed, paused or cancelled.

It is also worth confirming how project records will be provided. For time-based work, this may include a summary of activities and time used. For fixed-fee work, it may include milestone reports, test results, configuration records and handover documentation. These records help the client compare the invoice with the agreed work without turning the managed service relationship into an informal arrangement.

For businesses around Stourbridge and neighbouring areas, the most appropriate model will depend on the maturity of the existing IT environment and the certainty of the proposed change. The key issue is not simply choosing between a fixed fee and hourly charging; it is ensuring that the contract makes the boundary between recurring support, project work and approved additional work unambiguous.