Fixed Fee, Time and Materials or Retainer: Who Carries the Risk
How cloud consulting is priced: fixed fee, time and materials, retainers, managed services and outcome-based deals, who carries the risk and what to ask for.
Techrupt Team8 min read

Cloud consulting is priced in three main ways. A fixed fee puts the cost-overrun risk on the partner, time and materials puts it on you, and a retainer has you pay for reserved capacity whether you use it or not. Managed services for ongoing operations are priced per user, per device or by consumption, and outcome-based deals tie part of the fee to a measured result, though they remain uncommon.
No model is safer in general. Each one is safe for a certain kind of work. A fixed fee suits a build with a known scope, time and materials suits work whose effort nobody can estimate yet, and a retainer suits steady advisory work. The protection comes from the terms around the price: a cap, a rate card, a change process, acceptance criteria and a way out. This post covers the models, when each fits and what to ask a partner for under each one.
The three models and who carries the risk
The clearest public definitions come from Public Services and Procurement Canada’s Practitioner’s Guide for Procurement Pricing (August 2023). BC public sector buyers will recognise its terms, and they apply equally to private-sector work.
Fixed fee. PSPC defines a fixed price as a definite sum for carrying out the work “regardless of the costs incurred”. The contractor bears the risk of cost fluctuations, and the guide notes that a higher profit rate is typically built into the price to pay for that risk. You are paying a premium for certainty, and it only holds if the scope is precise enough that both sides agree when the work is done.
Time and materials. PSPC calls this a fixed time or unit rate: you pay a set rate for the hours actually worked. The guide says to use it when the level of effort cannot be estimated in advance and there are adequate controls to make sure the hours are used efficiently. The rate is fixed, the total is not, and the overrun risk sits with you.
Retainer. A monthly fee buys a set amount of capacity or access to named people, usually for architecture advice, cost reviews or support after a project. You carry utilization risk: unused hours are your cost unless the contract says they roll over. It works when demand is steady but hard to scope as a project.
Caps that sit between fixed fee and time and materials
Most contracts are hybrids. The PSPC guide describes two controls that make rate-based billing something a budget owner can approve.
A ceiling price is used when the effort can be realistically estimated and both parties fully agree on what the work is. The contractor must finish that work without extra payment, even if its costs go past the ceiling. Above the cap, the risk moves to the partner.
A limitation of expenditure is the maximum you will pay, used when the effort cannot be estimated at the outset. It does not oblige the partner to finish the work within the cap. It obliges them to notify you before they reach it, so you can decide whether to raise the limit or stop once the funds are spent.
A ceiling buys a finished deliverable. A limitation of expenditure buys a spending limit and an early warning. “Capped” is used loosely for both, so ask which one a proposal contains.
PSPC also describes a provisional price: work starts on a cost basis while requirements are uncertain, then moves to a fixed price at a milestone. In consulting, this usually looks like paid discovery followed by a fixed quote for the build.
Managed services and outcome-based pricing
Once a project is live, pricing changes with the work. Managed services are usually priced per user, per device, as a flat subscription for a defined scope, or by consumption, where the fee follows the Azure resources or spend under management. In Kaseya’s 2023 MSP benchmark survey, a combination of per-user and per-device pricing was the most common billing model among respondents. The provider carries the effort risk inside the defined scope, and the line between “in scope” and “billable project” is where disputes start. Our post on managed IT services pricing in Vancouver covers those models and how to compare quotes.
Outcome-based pricing links part of the fee to an agreed result, such as a reduction in tickets or a completed number of cases. Gartner told CIO Dive in August 2026 that only 19% of services buyers use such arrangements, and projects that through 2031, fewer than 25% of the tech services contracts in its forecast will use outcome-based pricing. Gartner’s test for these deals is whether the vendor is actually taking on risk. If the partner fully controls the “outcome”, it is a fixed fee under another name.
Which model fits which kind of work
| Model | Who carries cost-overrun risk | Fits when | What to ask for |
|---|---|---|---|
| Fixed fee | Partner | Scope, inventory and acceptance criteria are known: a landing zone build, a defined tenant migration, a fixed-scope assessment | Written deliverables, acceptance criteria per milestone, a change process with a priced rate card, payment on accepted milestones |
| Time and materials | You | Effort cannot be estimated yet: troubleshooting, early discovery, advisory work | Rate card by role, weekly time reports against tasks, a limitation of expenditure with notice before it is reached |
| Time and materials with a ceiling | Partner above the ceiling | Effort can be estimated and both sides agree on the work | The ceiling in the contract, the work it covers, and confirmation that changes need written approval |
| Retainer | You (unused capacity) | Steady advisory or post-project support | Named people, what the hours cover, rollover or expiry rules, a monthly report of what was delivered |
| Managed service | Provider, for in-scope effort | Ongoing operations after a project | Unit definitions, inclusions and exclusions, service levels, onboarding fee, exit and handover terms |
| Outcome-based | Shared, if the outcome is real | A narrow result that can be measured from your own data | The metric, the baseline, who measures it, and what happens if it is missed |
The phase of work usually decides the model:
- Discovery. A short paid phase on time and materials with a limitation of expenditure, or a small fixed fee. You should own the outputs: the inventory, the design decisions and a quote for the next phase.
- Defined builds. A fixed fee, or time and materials with a ceiling, once discovery has produced a scope both sides can test against.
- Open-ended migrations. Phases, each priced once the previous one has reduced the unknowns. A fixed fee for a migration with no application inventory usually hides a large contingency or a long list of exclusions. Our post on why cloud migrations stall covers how unclear scope shows up later as delay.
- Ongoing operations. A managed service or a retainer, priced on units you can count.
Microsoft-funded work is usually fixed-scope
Microsoft funding for partner-delivered assessments, proofs of concept and deployment accelerators has its own structure. The funded portion is defined by a statement of work and paid against evidence that the work was delivered. Microsoft’s terms for the FY27 Copilot Agents voucher are an example: one SOW per voucher, Microsoft’s own SOW and proof-of-execution templates signed by the customer and the partner, and redemption within six months. For public sector customers, the partner is paid only once the work is complete and proof of execution is approved.
The funded slice behaves like a fixed fee with an end date, and anything beyond it is priced under one of the models above. Ask the partner to show the funded scope and the paid scope as separate lines, so work that was meant to be funded does not drift onto your invoice. Our post on Microsoft funding for cloud projects covers which programs exist and how to ask for them.
What to ask a partner for under each model
Whatever the model, five terms decide how much risk you carry.
Caps. For any rate-based work, ask whether the cap is a ceiling price or a limitation of expenditure, and at what point you get notice. A cap with no notice clause tells you the money is gone only after it is spent.
Rate cards. Ask for rates by role, not one blended figure, and the rate that applies to changes on a fixed-fee project. A rate card is only useful if the senior architect in the proposal is the one doing the work.
Change control. Ask how a change is raised, estimated, approved and signed off, and who on your side can approve it. PSPC’s guide calls for a clause in ceiling-price contracts so the contractor makes no changes and does no extra work without the contracting officer’s prior written approval. That is a sensible rule for any contract.
Acceptance criteria. Each milestone needs a test you can run: a deployed landing zone that passes a named policy set, a migrated workload running in production for an agreed period, a document reviewed and accepted. “Delivered” is not an acceptance criterion.
Exit terms. Ask what you receive if you end the engagement early: code, infrastructure-as-code templates, documentation, credentials and a handover session. For retainers and managed services, ask about notice and whether unused prepaid hours are refunded. Our guide to choosing a Microsoft Azure partner in Vancouver covers the wider evaluation.
Red flags in a proposal
- A fixed fee with no acceptance criteria. The price is fixed, but the definition of done is not, so the partner decides when the work is finished.
- Time and materials with no cap and no reporting. You learn the cost from the invoice.
- A retainer with no record of delivery. If nobody can say what last month’s hours produced, the retainer is paying for availability.
- “Capped” without saying which cap. A limitation of expenditure presented as a ceiling price leaves you holding the risk.
- No exit terms. Leaving should not depend on the partner’s goodwill.
Where to start
This week, take your current or next consulting proposal and mark each workstream with its pricing model, who carries the overrun risk and the clause that covers each of the five terms: cap, rate card, change control, acceptance criteria and exit. Any blank cell is a question for the partner before you sign.
If you are planning a project or the operations that follow it, our Microsoft managed cloud service provides ongoing support for your Microsoft cloud platform, and our Azure consulting team in Vancouver scopes project work. Book a consultation and we will go through your proposal and the pricing model that fits each phase.



