Pricing Isn't About Cost, It's About Risk
When an organization weighs Fixed Price versus Time & Materials, they typically ask which model is cheaper. That's the wrong question. Both models account for the same work; the difference is who absorbs the deviation when reality strays from assumptions.
With Fixed Price, the vendor absorbs the risk—so they build in a risk margin from the outset and protect themselves by precisely defining what's included. With T&M, the organization absorbs the risk—so they need control mechanisms. With Retainer, both sides gain stability in exchange for reduced flexibility.
The simple rule: the more mature the Scope definition, the more advantageous a Fixed Price model. The more genuine unknowns there are, the better a capped T&M model.
Quick Comparison of the Three Models
| Aspect | Fixed Price | Time & Materials | Retainer |
|---|---|---|---|
| Who Bears Scope Risk | Vendor | Organization | Shared within agreed scope |
| Success Conditions | Well-defined Scope | Transparency and close management | Stable, predictable demand |
| Flexibility for Change | Low, via change requests | High | Moderate |
| Administrative Burden on Org | Medium, focused on definition | High, ongoing | Low |
| Typical Pitfall | Scope creep battles | Hours creep | Unused or absorbed hours |
| Good Fit For | Defined implementation waves | Integration, migration, discovery | Maintenance and continuous improvement |
Fixed Price — When to Use and What to Watch Out For
Suitable when there's a detailed specification with clear acceptance criteria, known and documented integrations, and verified data quality. In this scenario, the vendor can price with reasonable confidence, and the organization gains genuine budget certainty.
Protective mechanisms to demand:
- Defining "completed" for each deliverable, not just the deliverable's name.
- An explicit list of assumptions underpinning the price.
- A pre-agreed rate for change requests, preventing disputes under pressure.
- A payment schedule linked to acceptance, not arbitrary dates.
Warning sign: A Fixed Price quote given without any questions about data volume, user count, or source systems. Such a price will change; the only question is when.
Time & Materials — When to Use and How to Control
Suitable when there are unknowns that are not cheap to resolve: an old core system without documentation, historical data of unknown quality, or a business process that's still evolving.
Control mechanisms that make it safe:
- A cap for each milestone with an alert when a set percentage of it is reached.
- Task-level reporting—task name, hours spent, status.
- Exit points at the end of each milestone, with no penalty.
- An agreed team mix—how many senior vs. junior hours—to prevent quiet changes.
The last point is often overlooked, yet it impacts cost more than the hourly rate itself.
Retainer — When it Becomes a Waste
A Retainer works well after go-live, when there's a steady stream of requests. It falters in two opposite scenarios: when demand is low and the organization pays for unused hours, or when significant development work is pushed in, draining support capacity.
Two simple fixes: explicit separation between support and development, and a clause allowing partial rollover of unused hours to the next month, with a cap. Combining both stabilizes the model.
Hybrid Models That Work in Practice
| Project Phase | Recommended Model | Reasoning |
|---|---|---|
| Consulting & Discovery | Short Fixed Price | Scope is known, deliverable defined |
| Data Migration | Capped T&M | Data quality reveals itself during process |
| Integrations to Legacy Systems | Capped T&M | Dependent on the other system |
| Defined Implementation Wave | Fixed Price | Acceptance criteria exist |
| Stabilization Period | Included in wave price | Prevents disputes over what's a bug vs. change |
| Ongoing Maintenance | Retainer | Consistent demand |
Such a breakdown might seem more complex than a single agreement, but it precisely reduces the arguments that derail projects.
Illustrative Example: Medical Equipment Importer
This hypothetical scenario is for illustration. An importer requested a Fixed Price quote for a project that included integrating with a fifteen-year-old inventory management system lacking API documentation. The three proposals received had a very wide cost range, and the cheapest included a small print clause: "Assuming a REST API is available."
Before signing, the organization conducted a short, one-week feasibility study. It turned out there was no such interface, and an intermediary layer was required. This study changed the picture: the integration shifted to a capped T&M model, while the rest of the project remained Fixed Price.
What the brief study prevented was not additional cost—that would have come anyway—but a contractual dispute in the middle of the project over who was responsible for an unchecked assumption.
What Impacts Pricing More Than the Pricing Model
- Maturity of definition—incomplete specifications make any model more expensive.
- Number of source systems and their documentation level.
- Quality of existing data.
- Availability of process owners within the organization—decision delays are a direct cost.
- Number of business units that need to agree.
Four out of these five are within the organization's control, not the vendor's. This is why investing in preparation reduces project costs more than any negotiation over rates.
From Model to Agreement
After selecting the model, the wording matters: what constitutes a completed deliverable, who approves it, and what happens when the other party causes delays. The clauses that should be included in the agreement are detailed in the Salesforce SOW and Contract Guide, and how to draft an RFP to ensure comparable proposals is outlined in the Salesforce RFP Guide.
The initial selection of the type of service to be priced is detailed in the Salesforce Services Guide, and evaluating the vendor itself in the Salesforce Implementation Partner Selection Guide.
Next Step
Before requesting pricing, rank the three biggest sources of uncertainty in your project. If you can name them, you're ready for a Fixed Price model for part of the work. If you can't, the first thing to procure is a short discovery phase to remove those uncertainties, not a quote for the entire project.