Delivery architecture decides how organisations work together. Pricing architecture decides how financial uncertainty is shared.
Projects often use the words procurement model and contract type as if they describe the same choice. They do not.
A procurement model describes the delivery relationship: who designs, who constructs, who integrates, who manages interfaces and how the buyer and supplier collaborate. A contract type, in the Week 8 material, describes the commercial pricing mechanism used inside that relationship: fixed price, time and materials, cost reimbursement or a related variant.
Confusing the two can produce poor decisions. A project may select the right delivery model but pair it with a pricing mechanism that does not fit the uncertainty. It may also choose a familiar contract type and then force the delivery relationship to operate around it.
The Strategic Context
The Week 8 study notes distinguish delivery models such as traditional construction, design and construct, managing contractor, alliance and PPP from pricing families such as firm fixed price, cost reimbursement and time and materials.
That distinction matters because the two decisions solve different problems.
The procurement model determines organisational responsibility.
The contract type determines how cost and price risk are distributed.
For example, a design-and-construct delivery model can still contain different pricing structures depending on requirement maturity and market conditions. A managing-contractor arrangement can contain separately priced work packages. A long-term PPP can contain performance-payment mechanisms that go far beyond a simple fixed-price construction contract.
The correct architecture therefore has at least two layers.
What Leaders Commonly Misread
The first mistake is choosing the pricing mechanism before deciding who should own the major delivery responsibilities.
The second is assuming a fixed-price contract automatically produces a fully transferred delivery outcome.
The third is believing a collaborative procurement model requires weak commercial discipline.
The fourth is assuming the same pricing mechanism should apply across every package inside a complex program.
The fifth is using the word “contract strategy” without distinguishing legal form, delivery model and price basis.
These are different design decisions and should be governed separately.
Reframing the Issue
A useful sequence is:
Sourcing boundary → Procurement model → Pricing mechanism → Contract governance
First decide what capability will remain inside the organisation and what will be sourced externally.
Then decide how the parties will work together.
Then decide how price and cost uncertainty should be handled.
Finally, design the contract controls required to manage performance, change and exit.
This sequence prevents the project from treating price structure as a substitute for delivery strategy.
Strategic Analysis
Consider a hypothetical manufacturing expansion.
The organisation wants a supplier to design, build and commission a new automated production cell. That is a delivery-model choice: the supplier carries significant design and integration responsibility.
However, the technology contains several uncertain interfaces with existing equipment.
The buyer could still use a firm fixed price if the requirement is sufficiently defined and suppliers can price the remaining uncertainty credibly.
Alternatively, it could use a target-cost or cost-reimbursable mechanism during an early phase, then move to a fixed-price package once the design is mature.
The delivery relationship remains broadly the same while the pricing mechanism changes with uncertainty.
That is the strategic value of separating the two decisions.
Executive Trade-offs
There is a trade-off between simplicity and fit.
Executives understandably prefer one clear commercial model. But complex programs often contain different types of uncertainty. Engineering design may be evolving while commodity equipment is well defined. Civil work may be fixed price while specialist integration remains time and materials.
Using one pricing mechanism everywhere can look administratively neat while misallocating risk.
The stronger approach is to design a coherent overall model and then allow different price mechanisms where the work genuinely differs.
Consistency should exist in governance and objectives, not necessarily in every commercial term.
Decision Framework
Use four questions.
Delivery responsibility
Who should own design, integration, construction, commissioning and operational interfaces?
Requirement maturity
How well can the outcome and scope be defined before commitment?
Cost uncertainty
Which cost drivers can suppliers realistically control?
Governance capability
Can the buyer administer open-book, T&M or incentive mechanisms if they are selected?
The answer to these questions should determine the architecture rather than organisational habit.
From Strategy to Execution
Immediate action: separate procurement-model approval from pricing-mechanism approval in major sourcing decisions.
Medium-term capability building: create decision templates that distinguish delivery responsibility, risk ownership and price basis.
Long-term strategic positioning: allow programs to use multiple commercial mechanisms under one coherent governance model where the work requires it.
This makes procurement more adaptive without making it inconsistent.
Signals to Monitor
Watch for teams describing “fixed price” as though it explains the entire delivery model, suppliers carrying design responsibility without corresponding control, projects using cost-reimbursement mechanisms without cost-governance capability and complex programs forcing every package into the same commercial form.
Another signal is disagreement between procurement, engineering and finance because each is using “contract strategy” to mean something different.
Questions for the Leadership Team
- Have we separated the delivery-model decision from the pricing decision?
- Who actually owns design and integration risk?
- Which uncertainties can suppliers price credibly?
- Which uncertainties should remain with the buyer?
- Can our governance systems administer the proposed price mechanism?
- Do different work packages genuinely require different commercial approaches?
Closing Perspective
Procurement architecture becomes clearer when leaders stop searching for one universal “contract type”.
Choose the relationship first.
Then choose the pricing mechanism that can operate credibly inside that relationship.
Related article: Contract Type Should Follow the Work: Choosing the Right Agreement for the Delivery Model
Related article: How Leaders Should Select a Contract Type Under Uncertainty
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.