FBFreight Base System
Guides › Implementation

Fixed-Price or Time-and-Materials? How to Contract an ERP Implementation

A fixed price doesn't remove ERP overrun risk. It reprices that risk and buries it in assumptions. Here's how each contract model shifts risk, where change orders hide, and when a capped hybrid is the safer choice.

Freight Base System editorial team · November 2026 · 8 min read

The Real Question Is Who Pays When the Estimate Is Wrong

Every ERP estimate is wrong. The partner sizes the work from a few discovery workshops, a requirements list and experience with similar clients. Then the project meets your actual data, your actual approval chains and the integrations your team forgot to mention. What you're negotiating is who absorbs the gap between estimate and actual hours, and how that gets decided.

A fixed price ERP implementation appears to put that gap on the partner. A time-and-materials contract leaves it with you. Both descriptions are only partly true. Fixed price moves the risk on paper, then hands much of it back through assumptions and change orders. Time-and-materials keeps the risk with you but shows exactly where the hours go. Below: how each model behaves once a project is underway, and why a capped hybrid with milestone payments often protects buyers better than either.

Advertisement

What a Fixed Price Actually Buys You

Partners don't take on overrun risk for free. A fixed fee typically carries a contingency on top of the partner's internal time-and-materials estimate. It's often in the range of 15% to 30% or more, depending on how well the partner understands your scope. You pay that premium even when the project runs smoothly.

The partner protects its margin a second way: tight scope definition. The fee covers a specific list of deliverables under a specific set of assumptions, and anything outside that list is billable. The price is fixed only while reality matches the statement of work.

Fixed price works when scope is knowable. A single-entity rollout of NetSuite, Microsoft Dynamics 365 Business Central or SAP Business One, with mostly standard processes, two or three standard integrations and clean data, is a fair candidate. It works badly for multi-country rollouts, heavy warehouse or manufacturing customization, and any project where you're still redesigning processes during the build.

Time-and-Materials: Full Transparency, Full Exposure

Under a time and materials ERP contract, you pay for hours worked at agreed rates, plus expenses. There's no contingency premium, and you can change priorities without negotiating a change order each time. If requirements are still moving, that flexibility is worth real money.

The downside: nothing limits the bill, and the partner has no financial reason to finish sooner. Your safeguards are governance and discipline: weekly burn reports, approved staffing plans and the right to remove consultants who aren't performing.

Blended rates vary widely by delivery location. As typical 2026 market ranges, which vary by contract and seniority mix, expect roughly:

  • North America, UK and Western Europe: $140 to $260 per hour
  • Middle East (Gulf-based partners): $90 to $180 per hour
  • Eastern Europe and Latin America: $55 to $110 per hour
  • India and Southeast Asia offshore delivery: $30 to $80 per hour

Many partners mix onshore and offshore staff, so ask for the rate card by role and location, not just a blended figure. Confirm current rates with each shortlisted partner.

Where Change Orders Hide in a Fixed-Price Statement of Work

On a fixed-price deal, an ERP change order rarely comes from a dramatic scope change. Most trace back to sentences in the assumptions section that nobody challenged during procurement. Read your ERP statement of work for these patterns:

  • Data migration limits. "Client will provide cleansed data in partner templates" and "up to two mock loads." A third load, or any data cleansing, is billable.
  • Counted objects. "Up to 15 reports, 8 workflows, 3 integrations." Real projects usually need more, and each extra is priced separately.
  • Integration boundaries. The partner builds its side of the connection to your WMS, TMS or e-commerce platform. Middleware, third-party API changes and the other vendor's work are excluded.
  • Client-responsibility clauses. "Client SMEs available within 48 hours" and "decisions within five business days." Miss these and the partner can claim delay costs.
  • Testing caps. One UAT cycle, with defect fixes limited to items classed as in scope. A second cycle becomes a change order.
  • Localization gaps. E-invoicing for India's GST, Saudi Arabia's ZATCA or Mexico's CFDI is often listed as "standard functionality only," while your actual requirements, including any newer e-invoicing mandates in your markets, may go well beyond that.
  • Hypercare length. A couple of weeks of post-go-live support is common. Month-end close usually exposes issues after that window ends.

None of these clauses is unreasonable alone. The problem is that you rarely see their combined cost until you're too far in to walk away.

Fixed, T&M and Capped Hybrid Side by Side

FactorFixed priceTime-and-materialsCapped hybrid with milestones
Who absorbs overrunsPartner, within the assumptionsBuyerShared up to the cap, then partner
Risk premium in priceSubstantialNoneLow to moderate
Flexibility to change scopeLow; each change needs an orderHighModerate; changes draw on a change budget
Visibility into effortLowHighHigh
Partner incentiveMinimize hours, defend scopeHours billedHit milestones, stay under cap
Best fitStandard, well-defined scopeDiscovery, phase-two optimizationMost mid-market rollouts

How a Capped Hybrid With Milestone Payments Works

A capped hybrid bills time-and-materials up to a not-to-exceed ceiling. Part of each payment is tied to accepted milestones rather than hours. You still see every hour in the burn reports, and the partner absorbs costs above the cap unless an approved change order raises it.

Hypothetical example: say a 150-person distributor running two warehouses is implementing a cloud ERP. The partner estimates 2,400 hours at a $165 blended rate, about $396,000. Its fixed-price quote for the same scope is $490,000. The buyer negotiates a hybrid instead:

  1. T&M billing with a $440,000 cap, roughly 11% above the estimate versus the fixed quote's 24% premium.
  2. A separate $40,000 change budget, approved line by line by the steering committee.
  3. Payments released on four accepted milestones: design sign-off, build complete, UAT exit and go-live.
  4. 15% of each invoice held back until 30 days after the first clean month-end close.

If the project finishes at 2,300 hours, the buyer pays about $380,000 instead of $490,000. If it runs to 2,900 hours, the buyer's cost stops at $440,000 plus whatever approved changes it has drawn from the change budget. The holdback gives the partner a direct financial reason to get through hypercare well.

Most partners will accept a cap if discovery came first and was paid for separately. A partner that refuses any cap on a well-scoped project is telling you it doesn't trust its own estimate.

Contract Clauses That Matter More Than the Pricing Model

A sloppy ERP implementation contract can turn any pricing model into an expensive one. Before you sign, push for these terms:

  • Objective acceptance criteria for each milestone, defined in test scripts so "accepted" doesn't mean "the partner says so."
  • A change-order process with written impact estimates, a price per change and a response deadline. Confirm the partner can't stop work while a change order is in dispute.
  • Named key personnel and limits on swapping them out, especially the solution architect.
  • Rate locks for the project term and any phase two.
  • Data-protection terms that match where migrated data sits and who can access it. GDPR in Europe, India's DPDP Act, Brazil's LGPD and Gulf data-residency rules can all affect offshore access.
  • Tax treatment of cross-border services. VAT, GST and withholding tax can add materially to invoices in some jurisdictions if you don't plan for them.

Rules on enforceability, liability caps and tax differ by country. Have a commercial lawyer and a tax adviser licensed in your jurisdiction review the final agreement.

A Decision Rule for Picking Your Model

Choose fixed price only if all three are true: discovery is complete, processes are close to standard, and you can meet every client-responsibility assumption in the SOW. Use time-and-materials for discovery, proofs of concept and post-go-live optimization, where scope is supposed to change. For everything else, which covers most mid-market and multi-site rollouts, negotiate a capped hybrid with milestone payments and a holdback.

Your next step: before comparing headline prices, ask each shortlisted partner for its time-and-materials estimate alongside its fixed quote, plus the full list of SOW assumptions. The gap between the two numbers shows the risk premium. The assumptions list shows where the change orders will come from.

Quick answers

Is a fixed price ERP implementation always more expensive than time-and-materials?

The quote is usually higher because the partner prices in contingency, often by a double-digit percentage. On a well-defined project that runs smoothly, you pay that premium for nothing. On a poorly defined one, change orders can push the total past what time-and-materials would have cost. Fixed price saves money only when scope truly holds.

What is a reasonable cap above the estimate in a hybrid contract?

Caps roughly 10% to 20% above the partner's T&M estimate are a common starting point on mid-market projects with a paid discovery phase first. Keep a separate change budget for approved scope additions so real new requirements don't eat into the cap. Ranges vary by partner and region, so settle this in negotiation.

How much should we hold back from milestone payments?

Holdbacks of roughly 10% to 20% per invoice are typical. They're usually released after a stable post-go-live period, such as 30 to 60 days or the first clean month-end close. That's long enough to catch problems in close, inventory valuation and integrations without straining the partner's cash flow unreasonably.

Should discovery be part of the fixed-price contract?

Usually not. Contract discovery as a separate, smaller engagement, either fixed-fee or T&M, and require a detailed statement of work as its deliverable. That gives you a better basis for pricing the build, and you can take the design to a different partner if the first one's build quote isn't competitive.

Written by the Freight Base System editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.