Every engagement starts with the same question: who carries the cost when the work turns out to be different from the plan? We contract three ways, and the models differ in when scope is fixed, how you are billed, and where the risk of change sits. Choosing the right one at the start usually saves more than negotiating the price does.

Scope Projects Model

We agree the scope of work, the deliverables and the acceptance criteria in writing before the contract is signed, then deliver against them for a fixed price. The specification does the work here: the more precisely the boundaries are drawn up front, the less room there is for disagreement later about what was included. Changes are not refused — they go through a change request, are priced, and are approved before we act on them, so the budget never moves without your say-so.

Best fit when

  • The requirements are understood well enough to write down before work begins
  • You need a committed price to get the budget approved
  • There is a clear test for whether the deliverable is finished

Worth weighing: If the requirements are still being discovered, a fixed scope turns every new insight into a change request, and the administration starts to cost more than the work. Time and materials is usually cheaper in that situation, not more expensive.

How it is billed: A fixed price agreed before signing. Scope changes are quoted and approved separately.

Contact Us

Time & Materials Model

You are billed for the hours actually worked and the materials actually used, at rates agreed before we start. There is no fixed total, which is the point: the scope can move as you learn, and priorities can be reordered between one week and the next without renegotiating a contract. In exchange you get visibility — you see where the time went, and you decide what the team works on next.

Best fit when

  • The scope will be discovered during delivery rather than before it
  • Priorities change and you want to redirect the team without a new contract
  • You are extending your own team rather than buying a finished deliverable

Worth weighing: This model needs someone on your side who can set priorities week to week. Without that involvement the work drifts, and cost drifts with it. If nobody on your team has that time, a fixed scope protects you better.

How it is billed: Agreed hourly or daily rates for the people on the engagement, plus materials at cost.

Contact Us

Managed Services Model

We take on the day-to-day running of your infrastructure, systems or processes as an ongoing service rather than a project. The approach is proactive rather than reactive: continuous monitoring, routine maintenance and tuning, so that faults are found and cleared before they become outages you hear about from your users. The commitments are written into a Service Level Agreement, which is what makes the arrangement measurable rather than a matter of goodwill.

Best fit when

  • The system is already live and the priority is keeping it that way
  • You would rather buy the outcome than hire and retain scarce specialists
  • You need operating cost to be predictable across the year

Worth weighing: This is an operating relationship, not a project with an end date. It works when responsibilities, escalation paths and the boundary between your team and ours are agreed in writing before handover — and it goes wrong when they are assumed.

How it is billed: A recurring fee covering an agreed set of systems and the service levels attached to them.

Contact Us

The three side by side

How the models differ on the four things that decide which one fits.

Scope ProjectsTime & MaterialsManaged Services
Scope is fixedBefore the contractEvolves during deliveryDefined as an ongoing service
You are billedA fixed priceActual time and materialsA recurring fee
Change is handled byA priced change requestReprioritising the workThe service level agreement
Risk of change sits withINVENTOYouShared, and written into the SLA
The shape of itA defined deliverableAn extension of your teamContinuous operation

Not sure which one fits?

Most programmes are not purely one model. A discovery phase on time and materials, a fixed-scope build once the requirements settle, and managed services after go-live is a common shape, and the three can run under one agreement. Tell us what you are trying to deliver and, more usefully, what is still uncertain about it — we will recommend a model and explain the trade-off you are accepting by choosing it.

Contact Us