Procurement in Projects: Getting the Most from Your Vendors
Organisations that procure goods and services operationally -- repeating the same purchase on a regular schedule, from established suppliers, under long-term contracts -- have typically developed mature procurement practices for that environment. Category managers, preferred supplier lists, framework agreements, and annual price reviews are the tools of operational procurement, and most organisations with volume have invested in them.
Project procurement is a different animal. The scope is unique: each project calls for goods or services that may not have been purchased before in this combination or at this scale. The relationship is often one-time or short-term: the vendor engaged to build a new facility, deliver a technology implementation, or provide specialist consulting is not the same as the regular stationery supplier or the freight carrier on a standing contract. The timeline is often compressed relative to the complexity of what is being procured. And the integration risk is high: the vendor's performance directly affects the project's ability to deliver its objectives, and problems that might be manageable in an ongoing operational context can be project-ending in a compressed project schedule.
Managing project procurement well requires a different set of disciplines from operational procurement -- not a completely different toolkit, but different emphasis and different attention to the phases of the procurement lifecycle that matter most in a project context.
The Make-or-Buy Decision
The first procurement decision in any project is whether to do the work internally or bring in external capability. This decision is often made informally -- based on habit, existing relationships, or a rapid judgment about internal capacity -- when it deserves systematic analysis. The make-or-buy decision should consider: whether the internal capability and capacity actually exist in the timeframe required; the comparative cost of internal versus external delivery, including the full cost of managing an external engagement; the strategic sensitivity of the work and whether outsourcing it creates unacceptable intellectual property or knowledge dependency risks; and the speed with which external capability can be mobilised relative to the project schedule.
The answer is not always to buy. Organisations that default to external procurement for project work because their internal capability is underutilised, or because procurement is seen as faster than internal resource mobilisation, often discover mid-project that external vendors cannot match the contextual knowledge and organisational relationships that internal resources would have brought. The make-or-buy analysis is worth doing properly.
The Statement of Work
The Statement of Work (SOW) is the document that defines what the vendor is being asked to deliver. In project procurement, the SOW is the single most important document in the procurement process: its quality determines the quality of the proposals received, the precision of the contract, and the clarity of the basis for disputes if they arise. Poorly written SOWs produce proposals that are incomparable, contracts that are ambiguous, and change orders that proliferate.
A well-written SOW defines the scope of work with enough specificity that a competent vendor can price it accurately; it defines the deliverables in terms of what the vendor must produce, not what activities they must perform; it specifies acceptance criteria so both parties know when a deliverable is complete; it identifies the assumptions underpinning the scope definition and the exclusions that are explicitly out of scope; and it establishes the governance arrangements under which the work will be managed. The investment of time in writing a rigorous SOW is repaid many times over in a cleaner procurement process and a more manageable vendor relationship.
RFP Development and Vendor Selection
The Request for Proposal (RFP) packages the SOW with evaluation criteria, commercial terms, and submission requirements. The most important design decision in an RFP is the weighting of evaluation criteria: how much of the selection decision is based on technical capability, how much on methodology, how much on price, and how much on vendor qualifications and references. Criteria that are not weighted are not criteria -- they are aspirations that vendors can satisfy with impressive words and that selectors can interpret selectively to justify a predetermined preference.
Vendor selection in project procurement should include qualitative assessment that operational procurement often does not require. References from clients for whom the vendor has delivered comparable work are worth checking: not as a formality, but with specific questions about how the vendor managed issues, communicated problems, and handled scope changes. A vendor's track record on the difficult parts of delivery -- not just the happy path -- is the most predictive indicator of how they will perform.
Contract Types and Risk Allocation
The choice of contract type allocates risk between the project and the vendor. The three fundamental types cover the spectrum of risk allocation.
Fixed-price contracts: the vendor commits to delivering the defined scope for a fixed price. The vendor bears the risk of cost overrun; the project bears the risk of scope being inadequately defined. Fixed-price contracts work well when scope is genuinely well-defined and stable; they work poorly when scope is uncertain, because vendors price in contingency and change orders proliferate.
Time-and-materials contracts: the project pays for the vendor's time and materials at agreed rates. The project bears the cost risk; the vendor bears no financial incentive to be efficient. T&M contracts are appropriate when scope cannot be defined in advance -- investigative work, early-stage design, or work where requirements will emerge through the engagement.
Cost-plus contracts: the project pays the vendor's actual costs plus a fee (fixed, percentage, or performance-based). Similar risk profile to T&M but used in contexts where the cost structure is more complex -- major construction, defence procurement, large-scale outsourcing.
Vendor Management and Common Failure Modes
Procurement does not end at contract award. Vendor management -- the ongoing relationship with the vendor through the delivery period -- is where most project procurement value is won or lost. The most common failure modes are predictable and largely preventable.
Scope ambiguity, left unresolved at contract award, produces disputes. The test of scope definition is simple: if both parties were asked independently to describe what is and is not in scope, would their answers match? If the answer is uncertain, the scope is not yet clear enough to award a contract.
Poor communication -- specifically, the absence of agreed status reporting, issue escalation protocols, and decision-making authorities -- allows small problems to become large ones. Invoice disputes, which are a reliable early indicator of a strained vendor relationship, almost always have their roots in unclear acceptance criteria or billing procedures that were not resolved at the time of contract award.
Change order proliferation is the most expensive failure mode in fixed-price project procurement. It typically results from a combination of inadequate scope definition, a vendor that priced competitively to win and intends to recover margin through changes, and a project team that approves changes without fully accounting for their cumulative impact on budget and schedule. Controlling scope change requires discipline that must be established at project initiation and maintained throughout delivery.
XNM Consulting supports organisations in project procurement strategy, vendor selection, contract design, and vendor management across complex delivery programmes. Learn more about our program and project delivery services.