Engagement models compared: fixed scope, T&M, team, managed

There are four common ways to contract technology work, and each one puts risk in a different place. Here are the engagement models compared in one sentence: fixed scope sets a price for a defined deliverable, time and materials bills the effort used at agreed rates, a dedicated team reserves people for a monthly fee, and a managed service charges for a result kept at an agreed level. Choose by how well you can define the work and how much direction you want to give.

The four engagement models compared

No model is cheaper by nature. Each one prices the same uncertainty in a different way, so the useful question is who is better placed to carry it.

Fixed scope: certainty in exchange for flexibility

Public procurement rules describe this trade clearly. The US Federal Acquisition Regulation says a firm-fixed-price contract places maximum risk and full responsibility for costs on the contractor, which gives the contractor the strongest incentive to control cost. Commercial fixed-scope work follows the same logic.

Three consequences follow. The provider adds a margin for the risk it is taking. The provider needs a specification firm enough to price. And anything outside that specification becomes a change request with its own price and delay.

Fixed scope works well for discovery phases, audits, migrations with a known inventory and a first release whose features are settled. It works badly when you expect to learn as you go. To get the benefit without the rigidity, fix the scope in small pieces and write acceptance criteria for each one.

Time and materials: flexibility in exchange for oversight

The same regulation defines a time-and-materials contract as labor hours at fixed hourly rates that already include wages, overhead and profit, plus materials at cost. It allows this type only when the extent or duration of the work cannot be estimated with reasonable confidence at the start. It also notes that the arrangement gives the contractor no positive profit incentive to control cost, so the buyer has to supervise, and it requires a ceiling price that the contractor exceeds at its own risk.

That is a good template for commercial buyers too. If you choose time and materials:

• Set a not-to-exceed amount for each phase.
• Ask for a demo of working software every week or two.
• Get a regular report that compares budget spent with progress made.
• Keep the right to pause or stop at short notice.

With those controls in place, this model suits early product work, research-heavy AI projects and anything where the first month will change the plan.

Dedicated team: reserved capacity that you direct

In a dedicated team model, the provider assembles a standing group, typically engineers plus design, quality and delivery roles as needed, and you set its priorities. You pay a monthly fee per person or for the team as a whole. The provider is responsible for hiring, retention, replacement and engineering standards. You are responsible for the backlog.

The model pays off when the work is continuous. The team builds up knowledge of your systems and you avoid a new statement of work for every feature. It wastes money when you cannot supply a steady flow of decisions and priorities, because the team is paid whether or not it is busy.

A dedicated team is not the same as adding individual contractors to your own team. The differences in management effort and accountability are covered in the comparison of staff augmentation, dedicated teams and managed services. For a view of how providers structure the offer, see dedicated teams and team extension.

Managed service: paying for a result that is kept up

A managed service starts once something is live. You stop buying effort and buy a level of service: the platform stays available, incidents get a response within a set time, costs stay inside a budget, models are retrained when accuracy drifts.

The contract centers on a service level agreement. One definition in the NIST glossary describes it as a commitment between a provider and its customers that covers responsibilities, the expected performance level, such as reliability and response times, and the requirements for reporting, resolution and termination.

Before you sign, pin down what is in scope, how each service level is measured, what the monthly report contains, how much change work is included and what the provider must hand back at exit. Managed cloud services are a common example.

How to choose, and when to combine models

Work through these questions in order and stop at the first yes.

1. Is a system already live and in need of someone to run it? Use a managed service.
2. Can you write acceptance criteria for the whole deliverable today? Use fixed scope.
3. Is the work continuous, with a backlog you can keep full? Use a dedicated team.
4. Otherwise, use time and materials with a cap, and revisit the choice once the scope settles.

Many programs use more than one model in sequence. A fixed-scope discovery produces a plan and an estimate. The build runs under capped time and materials or a dedicated team. After launch, a managed service takes over. A product engineering engagement often follows this path.

In every model, the same clauses decide how well a disagreement ends: ownership of the work, acceptance, key people, termination and handover. Ask your legal adviser to review them. This article is general information, not legal advice.

How YLinkTech helps

We offer project delivery with a defined scope, dedicated teams, managed services and talent placement, and we will tell you which one we think fits before you commit to anything. Our four delivery steps and engagement models are set out on the site. If you are unsure how to structure a piece of work, describe it to us and we will suggest a model, explain where the risk sits and outline what a first phase could look like.

Frequently asked questions

Sources

• Acquisition.gov: FAR 16.202-1, Firm-fixed-price contracts, description
• Acquisition.gov: FAR 16.601, Time-and-materials contracts
• NIST Computer Security Resource Center: Glossary, service level agreement (SLA)

This article is general information, not professional advice. See our Disclaimer.