It is the central contractual question of any outsourced project, and it always comes up sooner than expected: should you buy a result — fixed price — or managed working time — time and materials? Behind this choice lie the allocation of risk between client and provider, the project's governance model, flexibility in the face of change and, ultimately, a good part of the total cost. Fixed price reassures finance departments with its firm price, but it freezes a scope at the very moment when the least is known; time and materials embraces the shifting reality of a product, but it demands real steering capacity on the client side. Between the two, the dedicated team and hybrid structures have become established in lasting nearshore relationships. This article details how each model really works, their respective traps — change-order drift on one side, trajectory drift on the other — and a selection grid according to the nature of your project. CRYSTAL IT, a software company in Rabat that works under all three regimes with its French clients (our IT offshoring services), also shares the structure we most often recommend to get started: it is neither all-fixed-price nor all-time-and-materials.
Fixed Price: Buying a Result, at the Cost of a Frozen Scope
Under a fixed-price contract, the provider commits to a defined deliverable, a firm price and a deadline. The legal and economic logic is that of an obligation of result: it is up to the provider to absorb the hazards of execution — underestimated complexity, a sick developer, a recalcitrant technology. This shift of risk has a price: the provider builds into its quotation a safety margin proportional to the uncertainties of the scope. A vague specification is therefore paid for twice: in risk margin in the initial price, then in change orders at every gap between what was written and what you actually needed.
For that is the structural trap of fixed price: it freezes the scope at contract time, that is, at the moment when everyone knows the least about the final product. Anything not written down is out of scope; any evolution becomes a negotiation. Fixed-price projects that go well share three characteristics: a genuinely stable and specifiable need (a like-for-like redesign, a well-bounded technical work package, a deliberately minimal MVP), written and testable acceptance criteria, and closely spaced delivery milestones that allow progress to be observed on working software rather than in status reports. Used under these conditions, fixed price remains an excellent tool — notably for a first project with a provider you are discovering (How to Choose a Software Development Provider in Morocco).
- Fixed price transfers execution risk to the provider — who bills it as a safety margin proportional to the vagueness of the scope.
- Scope frozen at the moment when the least is known: every evolution becomes a negotiated change order.
- Success conditions: stable need, testable acceptance criteria, closely spaced demonstrable milestones.
- Ideal use cases: bounded technical work package, minimal MVP, like-for-like redesign, first project with a new provider.
Time and Materials: Buying Managed Time, at the Cost of Real Governance
Under time and materials — the "technical assistance" of IT services companies —, you buy the time of identified profiles, billed at a daily rate (The Real Cost of an Offshore Developer in 2026), and you direct their work: you are the one who prioritises, arbitrates and decides the trajectory. The logic is that of an obligation of means: the provider must supply competent and diligent profiles, but the result depends on the steering — yours. In return, time and materials offers what fixed price cannot: flexibility. The scope evolves freely, priorities change from one sprint to the next, and the start is fast since it does not require specifying everything in advance.
The trap of time and materials is the exact mirror of the fixed-price one: without firm governance, it becomes trajectory drift — months of honest invoicing for a product that is not moving in the right direction, because no one on the client side held the course. The safeguards are well known: a genuinely available product owner on the client side, a prioritised backlog that is authoritative, precise activity reports, regular demonstrations, and progress indicators oriented towards deliverables rather than occupation. Add two contractual clauses: the replacement of a profile that does not fit, without penalty and within a short time, and intellectual property rights arising for the client's benefit as work progresses — under time and materials, this does not go without saying (Intellectual Property and Rights Assignment in a Development Contract).
- Time and materials buys the time of identified profiles that you steer: maximum flexibility, trajectory responsibility with you.
- Structural trap: trajectory drift — regular invoicing, a product that does not advance, for lack of a course held on the client side.
- Safeguards: available product owner, authoritative backlog, regular demonstrations, deliverable-oriented indicators.
- Clauses to demand: fast replacement of an unsuitable profile, intellectual property arising for the client's benefit as work progresses.
The Dedicated Team: The Cruising Regime of Products That Live On
Between the one-off fixed-price contract and profile-by-profile time and materials, the dedicated team has established itself as the model of lasting nearshore relationships: a stable team — developers, technical lead, often a project manager — works exclusively for you, month after month, with a reciprocal commitment of duration and a smoothed monthly cost. Economically it is the best cost per worked day, because the provider can commit over time; above all, operationally it is the model where knowledge accumulates: the team that has been developing your product for eighteen months knows your business, your users and your code — that knowledge is an asset that appears in no quotation.
The dedicated team suits products that evolve continuously: a business ERP enriched with each cycle (our ERP development service), a living mobile application (our mobile app development service), a SaaS platform. It assumes a sufficient flow of work to keep the team busy — that is its entry condition — and the same governance requirements as time and materials, with one advantage: the stability of the people makes the rituals more effective as the relationship settles in (Managing a Remote Development Team). Contractually, take care of three points: the named composition of the team and the replacement rules, reversibility with notice and organised knowledge transfer (Reversibility of an Outsourced IT Project), and a framed flexibility clause to adjust the team size to the activity.
- A stable team working exclusively for you: best cost per worked day and accumulation of product knowledge.
- Suited to continuously evolving products; assumes a sufficient flow of work to keep the team busy.
- Key contractual points: named composition, replacement rules, organised reversibility, framed size flexibility.
- The knowledge accumulated by a stable team is an invisible asset — and the first argument against provider-hopping.
The Selection Grid: Four Questions That Settle It
First question: is your need specifiable today? If you can write testable acceptance criteria covering the essentials of the scope, fixed price is conceivable; otherwise, fixed price will make you pay for the vagueness in margin and then in change orders, and time and materials is more honest. Second question: do you have the capacity to steer? A product owner available several hours a week, able to arbitrate quickly — without one, time and materials drifts, and you need either a milestone-based fixed price, or a provider that includes project management in its service. Third question: what is the horizon? A one-off need leans towards fixed price; a product that will live for years calls for a dedicated team. Fourth question: what is your tolerance for scope change? If your market or your users will impose pivots, do not sign a contract that prices them as anomalies.
Note that the contractual model and the place of execution are chosen separately but interact: remote time and materials requires more instrumented steering rituals than local work, which argues for a nearshore provider working on your hours rather than a distant time zone (Nearshore, Offshore, Onshore). Finally, beware of false fixed-price contracts: a "fixed price" whose specification fits in two pages is a disguised time-and-materials arrangement that dares not say its name — the firm price protects no one there, it prepares the litigation. An honest provider will tell you when your scope cannot be priced as a fixed package; that is even a good selection test.
- Need specifiable with testable criteria → fixed price possible; emerging need → time and materials or dedicated team.
- No available product owner → milestone-based fixed price or project management provided by the provider.
- One-off need → fixed price; lasting product → dedicated team.
- A "fixed price" with a two-page specification is disguised time and materials: refuse it, or specify first.
The Hybrid Structure: Frame at Fixed Price, Build in Time and Materials, Last as a Dedicated Team
In the practice of successful outsourcing relationships, the choice is not final: the models succeed one another over the course of the relationship. The structure we most often recommend to French companies starting with a new provider comes in three stages. First, a short framing work package, at fixed price: specification of the first version, mock-ups, architecture, prioritised and costed backlog — a few weeks that produce a shared reference and make it possible to evaluate the quality of the collaboration on a limited commitment. Then, the construction of the first version, at milestone-based fixed price if the framing produced a clear scope, or in instrumented time and materials if the product needs to find itself — in both cases with closely spaced demonstrable deliveries.
Finally, once the product is alive, the move to a dedicated team or cruising time and materials for maintenance and evolutions: that is where the real economics of outsourcing plays out, that of a team that knows the product and moves it forward without rediscovery costs. This sequencing has an additional virtue: each stage is a clean exit door. If the framing disappoints, you leave with a reusable specification file; if the first version disappoints, you leave with documented code that you own — provided the rights assignment and reversibility were addressed from the first contract, as we detail elsewhere (Intellectual Property and Rights Assignment in a Development Contract). That is how we start most French collaborations at CRYSTAL IT (our IT offshoring services): small, demonstrable, reversible — and lasting precisely because each stage earns the next.
- Stage 1 — framing at fixed price: specifications, mock-ups, architecture, costed backlog; short commitment, shared reference.
- Stage 2 — construction: milestone-based fixed price if the scope is clear, instrumented time and materials otherwise; closely spaced demonstrable deliveries.
- Stage 3 — product life: dedicated team or cruising time and materials, where accumulated knowledge pays off.
- Each stage is a clean exit door: reusable specifications, assigned and documented code, reversibility provided for in the contract.
Time and materials or fixed price is not an ideological debate: it is a risk-allocation choice that must follow the nature of your need — specifiable or emerging —, your steering capacity and your horizon. Fixed price protects a clear, milestone-based scope; time and materials serves a product under construction, provided governance holds; the dedicated team is the cruising regime of products that live on. And the hybrid structure — frame at fixed price, build in demonstrable milestones, last as a dedicated team — remains the safest path to start with a provider you are discovering, each stage validating the next. CRYSTAL IT, a software company based in Rabat for more than 20 years, practises all three regimes with its French clients, on Paris hours and in French (our IT offshoring services). Tell us about your project: we will tell you frankly which of these structures suits it — including if it is the smallest one.
Have a project or a question? Let's talk with a CRYSTAL IT expert.
Request a demo
