SAP contract pricing models come in three working shapes, time and materials, fixed fee, and milestone-based, and each one is a decision about who pays when the plan turns out to be wrong. That decision gets made at signing, months before anyone configures a single ledger. Most buyers treat it as a budgeting preference. It is a risk assignment.
Two lawsuits show what happens when nobody reads the assignment closely. National Grid sued Wipro over a fixed-scope rollout and settled for a reported $75 million. Zimmer Biomet is suing Deloitte for $172 million over a milestone-paid S/4HANA program, and Deloitte’s first move was to point at the contract.
Neither case turned on how many hours the consultants billed. Both turned on what the paper said.
So this is a comparison with one question running underneath it: under each model, which risks stay with you, which move to the partner, and what does the partner charge to carry them? The answer is the table in section two. Everything else is context for reading it.
The Three SAP Contract Pricing Models, in Plain English
Every SAP services contract (implementation, migration, or the AMS support deal that follows, AMS meaning application management services) is priced one of these ways or as a blend of them. The definitions are short. What they do to your budget under stress is the whole story, and it is why the model matters as much as the headline number in any SAP implementation cost estimate.
Time and Materials (T&M)
You pay for hours actually worked, at agreed rates, plus expenses. The statement of work (SOW) describes the effort and an estimate; the invoice describes reality. The final price is known when the work ends and not a day earlier.
Two variants matter. Capped T&M adds a not-to-exceed (NTE) ceiling: you pay actuals up to the cap, and crossing it requires a contract amendment. Cost-plus is a cousin, not a twin (the vendor bills its actual costs plus a margin set as a percentage or fixed fee, where T&M bakes the margin into the hourly rate).
Fixed Fee (Fixed Price)
You pay a pre-agreed amount for a defined scope, regardless of the hours the partner burns delivering it. If the work runs light, the partner keeps the difference. If it runs heavy, the partner eats it.
That second sentence is the one on the sales slide. The load-bearing wall is actually the SOW. The fixed price is fixed only for the scope as written, and everything outside that document is priced separately, later, at a moment when you have far less bargaining power.
Milestone-Based
A fixed fee cut into phases, with payment released when each phase clears defined acceptance criteria. Think blueprint signed off, build complete, user acceptance testing passed, go-live stable. Some contracts run T&M inside each phase with a milestone cap; most run a fixed amount per gate.
This is the structure most large SAP programs actually use, and it is the one page one of Google barely mentions. It gets its own section below.
- T&M prices effort. You own the estimate.
- Fixed fee prices a document. The partner owns the estimate; you own the document.
- Milestone prices a sequence of documents, each one closed by your signature.
Who Carries the Risk: The Transfer Table for SAP Contract Pricing Models
The generic comparison guides handle risk in a single line: under T&M the client carries the risk, under fixed price the vendor does. Both halves are wrong in the way that costs money, because “risk” in an SAP program is at least five different things, and each model moves them differently.
| Risk | T&M | Capped T&M (NTE) | Fixed Fee | Milestone |
|---|---|---|---|---|
| Scope risk (the requirements were wrong or incomplete) | You. Absorbed as extra hours. | You. The cap just forces the conversation sooner. | You. Anything outside the SOW becomes a change order. | You. Acceptance criteria define what “done” means, and you wrote them. |
| Estimate risk (right scope, wrong hours) | You, fully. | Shared. You up to the cap, then a negotiation. | Partner, who prices it in up front. | Partner, phase by phase, repriced at each gate. |
| Change risk (the business changes mid-project) | You, with low friction. | You, and it eats the cap. | You, at change-order rates. | You, and later phases get rebaselined. |
| Delivery risk (it’s built but doesn’t work for the business) | You. You bought hours, not outcomes. | You. | Shared on paper. The partner must meet the spec, which is not the same as the business working. | Shared until you sign acceptance. After that, mostly you. |
| Talent risk (who actually shows up) | You pay for every ramp-up hour after a swap. | You, same. | Partner’s cost, your outcome. The incentive runs toward cheaper staffing. | Same as fixed fee, inside each phase. |
| Payment control (who holds the money when things go wrong) | Partner. Invoices are monthly and earned by the hour. | Partner, until the cap. | Depends entirely on the payment schedule. | You, until you sign. Then it’s gone. |
Read down the scope row. It says “you” in every column. No pricing model on earth moves scope risk to the partner, because the partner didn’t write your requirements and won’t pretend to own them. Fixed fee doesn’t remove that risk. It reprices it.
The US government is unusually candid about what a true fixed price means. Its procurement rulebook, FAR 16.202-1 (the Federal Acquisition Regulation), says a firm-fixed-price contract “places upon the contractor maximum risk and full responsibility for all costs and resulting profit or loss.” That describes estimate risk, the one row where the partner genuinely takes the hit. It says nothing about scope, because scope was defined before the price existed.
And the partner charges for carrying that row. Software-services guides commonly put the fixed-price risk premium at 15-30% or more over the equivalent T&M estimate. That range comes from generic IT outsourcing, not a published SAP-specific study (none that we could find), so treat it as an order of magnitude, not a quote.
The incentives follow the money. Fixed price rewards the partner for finishing with fewer or cheaper hours, which is fine when it means efficiency and less fine when it means corner-cutting on testing. T&M rewards hours, which is fine when it means iteration and less fine when a workstream never quite converges. Oversight flips too: T&M needs you in the room every week, while fixed fee lets you step back after requirements, which is exactly when the expensive surprises start.
Bottom line: You never eliminate risk in an SAP contract. You only choose which risks to hand over and pay the partner’s price for carrying them.
What the Math Looks Like at SAP Rates
The generic guides illustrate this with a $75,000 app build. SAP numbers are larger, and the differences between the models scale with them.
Take one worked example: a six-month FI/CO workstream (finance and controlling, the accounting core of S/4HANA, SAP’s current ERP platform), staffed with the six-person team from our SAP consultant hourly rates analysis. One onshore architect at $200/hr, three onshore senior functional consultants at $150/hr, two offshore consultants at $60/hr, which blends to $128 an hour. Assume full-time staffing at about 160 billable hours a month. That’s 5,760 hours and an estimate of $737,280.
Here is the same estimate under each model, and what happens when reality misses it by 20% in either direction.
| Model | Price at Signing | If Work Runs 20% Heavy | If Work Runs 20% Light |
|---|---|---|---|
| T&M | ~$737K estimate, not a price | You pay ~$885K | You pay ~$590K |
| Capped T&M, NTE at $800K | Up to $800K | You pay $800K, then the work stops for an amendment | You pay ~$590K |
| Fixed fee (15-30% premium) | ~$848K to ~$958K | You pay the fixed fee; the partner eats the overrun | You pay the fixed fee; the partner keeps the savings |
| Milestone (same fee, four gates) | ~$848K to ~$958K, released per gate | Same as fixed fee, unless the overrun is traced to scope | Same as fixed fee |
The illustration assumes the 20% miss is pure estimate error. In a real SAP program it rarely is. Most overruns get argued as scope, and scope sits in your column of the transfer table.
So look at the fixed-fee row honestly. You are paying $110,000 to $220,000 up front for insurance against estimate error on a well-defined workstream. If the partner estimated well, you bought insurance you didn’t need and they keep the premium. If the work runs light, they keep that too. Sometimes that insurance is worth every dollar. It should be a choice, made with the number in front of you.
One more thing the blended rate hides. The $128 figure assumes two of six chairs are offshore. A partner can hit a lower blend by moving more of the team offshore, and under a fixed fee they have every reason to, because the saving is theirs. Offshore sellers pitch their rates as 40-60% below onshore “for the same quality.” That last phrase is the pitch, not a finding, so write the staffing mix into the contract whichever model you choose.
Milestone Contracts: The SAP Pricing Model Page One Ignores
Search for contract pricing comparisons and you get a binary: T&M or fixed price. Real SAP programs mostly run on a third thing. The fee is fixed, cut into phases, and paid when each phase clears acceptance.
Public-sector buyers make this visible, because their tenders are public. The CTBTO’s 2024 request for proposal for an SAP SuccessFactors implementation (SuccessFactors is SAP’s cloud HR suite) splits the scope of work into four phases with a numbered milestone under each, from “Assessment and Detailed Blueprint Design” through integration with a new ERP. The first milestone is a deliverable, not a date: an agreed “To-Be” business process supported by an approved implementation plan. The tender has its own section titled “Acceptance and Invoicing.” That pairing is the whole model.
Milestone contracts have real strengths. Payment tracks progress. You get a formal checkpoint at every phase boundary. And the partner carries estimate risk one phase at a time, so the premium is smaller than on a single fixed fee covering everything.
The weakness lives in the word “acceptance.”
Zimmer Biomet’s case against Deloitte is the live example. According to UpperEdge’s reading of the public filings, Zimmer Biomet’s S/4HANA program ran under a Master Services Agreement (MSA) signed in 2011 and a Work Order signed in 2021. It aimed to consolidate nine legacy ERP systems across North and Latin America, in two releases: North America from late 2022 through mid-2023, Latin America in early 2024. Milestone payments were tied to those staged go-lives. Zimmer Biomet filed its $172 million suit in September 2025 in New York Supreme Court. Deloitte filed a motion to dismiss on November 7, 2025.
This is active litigation, and nothing here says who is right. What matters for a buyer is the shape of the defense. UpperEdge summarizes it this way: the filing argues that every major activity, milestone, and payment was governed by agreements Zimmer Biomet signed, that each phase was approved, and that no objections were raised within the time frames the contract required.
“That positioning reframes the conversation from performance to paperwork, and that’s the terrain Deloitte prefers to fight on.” (UpperEdge)
Here is the sentence your partner cannot say to you in a sales meeting. A paid milestone is an accepted milestone, and every acceptance you sign is evidence for the partner’s side if the program later goes wrong. Your signature on the blueprint is their exhibit.
That doesn’t make milestone contracts bad. It makes acceptance criteria the most important pages in the contract. Write them as testable business outcomes (invoices post, the close runs, the interface to the warehouse system reconciles), give yourself a real review window, and never sign a gate to keep the schedule green.
Change Orders: Where Fixed Price Sends the Bill
A fixed bid doesn’t end the price negotiation. It moves it. Before signing, the fight is over the estimate. After signing, it’s over the boundary of the SOW, and every request that lands outside that boundary comes back as a change order, priced by the partner, at a moment when switching partners is no longer a realistic threat.
(The partner will call it scope clarification. Your invoice will call it a change order.)
Partners know this terrain well. One SAP proposal-writing guide, written for consultants, tells them to validate the business blueprint against the signed SOW “including all approved change request[s].” It also calls getting client sign-off that a requirement has been met “one of the tougher challenges of an ERP project.” They count change requests carefully. You should count them with the same care.
The buyer-side discipline is not complicated. It is just rarely enforced.
- Lock scope by the end of Explore. Explore is the fit-to-standard phase in SAP Activate, SAP’s delivery methodology. Practitioner Noel D’Costa’s timeline guide pairs “unclear scope or late scope changes” with the fix: lock scope by Explore and run a strict change control board (CCB).
- Document what’s out, not just what’s in. In D’Costa’s words, listing both “gives you something to point to when new requests arise.”
- Price change orders before you need them. Put the rate card for change work in the original contract, so the first change order isn’t also a rate negotiation.
- Put every decision in writing. The consultants’ own rulebook agrees.
As Günter Dusch writes in SAP Basics, Tips and Tricks for Prospective SAP Consultants (translated from the German), in his golden rules for consultants: “Verbal or telephone decisions are always confirmed in writing (e.g. by e-mail). In this way, misunderstandings can be avoided, and you can be protected.” That rule is taught to the people billing you. Follow it from the buyer’s side too.
National Grid shows what a fixed-scope wreck looks like at full size. The utility went live on SAP in 2012 with its integrator, Wipro, and the litigation record describes what followed: payroll errors, roughly 15,000 unpaid supplier invoices, and a period-end close that stretched from 4 days to 43. The recovery burned near $30 million a month. National Grid’s suit alleged design documents below industry standard, problems not disclosed, and legacy data not converted. Wipro paid $75 million to settle, against a total program reported near $1 billion, with more than $100 million of it paid to Wipro.
Read those numbers against the contract. The settlement came to well under a tenth of the program cost. The contract capped the partner’s exposure, not the buyer’s. Consultant Eric Kimberling’s lesson from the case is blunt: “You are in charge of your project, not your system integrator.” We walk through the full failure pattern in why ERP implementations fail.
The aggregate numbers are quieter but no kinder. Panorama Consulting’s published ERP research found 58% of projects exceeded their budgets and 65% overran their schedules, and 53% of organizations realized less than half the benefits they expected. Every one of those overruns landed in some contract’s change-order column. The mechanics of pricing and disputing change orders deserve their own guide; the short version is that the change-order clause is where a fixed-price contract’s real price is written.
How to Pick an SAP Contract Pricing Model: Match It to What You Actually Know
The usual question is which model is cheapest. The better one is what you can honestly specify today, because every model rewards certainty and punishes its absence differently.
Three questions decide it:
- How well defined is the scope, really? Not “we have a requirements document.” Could a stranger price it without asking you twenty questions?
- How likely is it to change? An acquisition pending, a new CFO, a regulatory deadline in motion: any of these means change risk, and change risk is always yours.
- How much oversight can you staff? T&M without a buyer-side lead reviewing timesheets weekly is a blank check with a nice rate card.
Answer those, and the models sort themselves.
T&M fits discovery work, AMS and ongoing support, agile build cycles, and any phase where the requirements are genuinely still forming. It’s also the fastest to start. It is not automatically runaway spending; it runs away when nobody on your side reads the invoices.
Fixed fee fits small, fully specified, repeatable work: a defined rollout of a template to one more country, a technical upgrade with a known object list, a data migration with the data already profiled. It is not automatically cheaper. You pay the premium whether or not the risk shows up, and it doesn’t guarantee the date, only the price of the scope as written.
Milestone fits most multi-phase S/4HANA programs, provided you invest in the acceptance criteria. It’s the best structure for keeping control of payments, and the worst one to sign carelessly.
The hybrids that work in SAP delivery tend to look like this:
- Discovery on T&M, then fixed fee per phase. Pay for the partner to learn your business, then ask for a fixed price once there’s something real to price. The discovery output becomes the SOW.
- Capped T&M with a working CCB. The cap only protects you if hitting it triggers a real decision, not an automatic amendment.
- Guaranteed maximum price (GMP). An import from construction: a cap, with savings below it split between the parties (often 50-50). Rare in SAP services, and worth asking about when a partner refuses a plain cap.
The counterargument deserves a sentence. A large partner quoting fixed fee on a big program is taking real balance-sheet risk, and for a buyer with thin internal capacity, that transfer is worth the premium. I’d still rather see that premium spent on a sharper SOW, because a better document shrinks every row of the transfer table at once.
The remaining problem is finding a partner willing to sign the structure you picked. Some shops only quote T&M; some will do milestones only with loose acceptance language. That matching step is what our engine handles: describe the project and the contract structure you want, and watch it rank partners that fit, free, no signup.
Not the Same Thing: SAP’s Own Software Pricing Models
Search “SAP contract pricing” and half the results are about something else entirely. For the record, three different things share the phrase.
- Services contracts (this post): how you pay the partner who implements or supports SAP.
- SAP’s software commercials: how you pay SAP itself. On BTP (Business Technology Platform, SAP’s cloud development and integration platform) that means a subscription with fixed entitlements, consumption-based credits under CPEA (Cloud Platform Enterprise Agreement, pre-purchased credits with an entry point around EUR 10,000), or pay-as-you-go (no upfront commitment, but list price and no discounts). Across the portfolio, the license shapes run from subscription contracts priced as annual contract value (RISE with SAP, the bundled S/4HANA cloud offer), to perpetual licenses plus annual maintenance for on-premise, to per-seat and per-transaction pricing on the cloud apps.
- “Contract pricing” inside SAP: the configuration sense. Pricing conditions on purchasing and sales contracts in SAP ERP (transaction ME33K displays a purchase contract, for example). That’s a consultant’s configuration question, not a buying one.
If you came for the software side, the license and subscription costs sit alongside services in our full cost breakdown. The services contract is where the risk transfer happens, though, and it’s where buyers most often sign without reading the transfer table.
Frequently Asked Questions
Is time and materials a fixed-price contract?
No. Time and materials bills actual hours at agreed rates plus expenses, so the final price is known only at the end. A fixed-price contract sets the price for a defined scope before work starts. A capped T&M contract with a not-to-exceed ceiling sits between them: the cap limits your exposure, but you still pay actuals below it.
Which is better, fixed price or T&M?
Neither, in the abstract. Fixed price is better when scope is small, stable, and fully specified, because the partner carries estimate risk. T&M is better when requirements are still forming or the work is ongoing support. For multi-phase SAP programs, a milestone structure with testable acceptance criteria usually beats both.
When should a time and materials contract be used?
Use T&M for discovery and blueprint work, AMS and ongoing support, agile build cycles, and any phase where requirements will change as you learn. It starts fastest and handles change with the least friction. It only works with a buyer-side lead reviewing hours weekly; without that oversight, you carry every risk with no visibility.
What are the three types of fixed price contracts?
The three most commonly cited, from US federal procurement rules (FAR subpart 16.2), are firm-fixed-price (one price, no adjustment), fixed-price with economic price adjustment (the price moves with defined indices like labor rates), and fixed-price incentive (the final price adjusts by a formula tied to cost performance). Commercial SAP contracts mostly use the first, sometimes with milestone payments.
Sources
- Federal Acquisition Regulation, subpart 16.2: fixed-price contract types and the firm-fixed-price risk language.
- UpperEdge, “Deloitte’s Defense Unfolds: The Contract That Could Decide the Zimmer Biomet Case” (November 10, 2025): program structure, milestone payments, and the motion to dismiss.
- Third Stage Consulting, lessons from the National Grid v. Wipro SAP lawsuit: case figures and the buyer-side lesson.
- Spinnaker Support, ERP implementation failure roundup: National Grid program cost and settlement figures.
- Panorama Consulting ERP Report archives: budget, schedule, and benefits-realization figures.
- CTBTO RFP 2024-0169, SAP SuccessFactors Implementation Service, terms of reference: the phase-and-milestone structure.
- SAP BW Consulting, “14 Ways to Write Better SAP Proposals”: the partner-side view of change requests and sign-off.
- Noel D’Costa, SAP timeline planning guide: scope lock by Explore and the change control board.
- Günter Dusch, SAP Basics, Tips and Tricks for Prospective SAP Consultants (translated from the German): quoted in the section on change orders.
Pick the model that matches what you can actually specify today, then police the boundary it creates. A fixed fee caps your risk, but only the risk you remembered to write into the scope. When you’re ready to find partners who will sign the structure you chose, browse the vendor directory by module and industry.
