Define the business outcome before deciding on the buying process.
What strategic sourcing actually decides
Strategic sourcing is the structured work of aligning business needs with supply-market options, comparing the full consequences of those options, and securing a workable commercial arrangement. A purchase order records a transaction. A sourcing strategy explains why that transaction should happen, with whom, under what conditions, and with what alternative if it fails.
Procurement is the broader function that can include policy, purchasing, sourcing, contracting and supplier management. Category management sets a longer-term direction across related spend. A sourcing event makes a particular decision within that direction. These responsibilities overlap; labels matter less than clear ownership.
Use a formal process when the decision is material, options differ substantially, switching is difficult, or a failure would disrupt the business. A repeat purchase against an appropriate existing agreement may need a simpler route. A high-value event with no realistic alternative needs a different strategy from a contest with several credible suppliers.
Follow the decision, not just the stages
Define the need
Clarify the business outcome, the actual demand and the constraints before choosing a buying route.
Understand the market
Map credible suppliers, substitutes, capacity and switching barriers. Separate facts from assumptions.
Create competition
Use a process that resolves real uncertainty and gives qualified suppliers a fair chance to compete.
Evaluate options
Compare evidence, normalize the economics and identify risks that a weighted score cannot resolve.
Negotiate
Connect executable alternatives with evidence, timing and a clear internal mandate.
Contract
Carry the winning offer into clear obligations, acceptance, change controls and exit provisions.
Implement
Align delivery, buyer dependencies and acceptance around useful business outcomes.
Govern
Track performance, obligations, invoices and changes with owners who can act.
Renew / exit
Work backward from notice requirements, transition lead time and the internal approval path.
The route is iterative. A market review may reveal that the requirement excludes every viable alternative. Evaluation may expose an implementation dependency that changes the budget. Go back to the relevant gate, document the change, and give affected suppliers consistent information. Progress is not the number of documents produced; it is the reduction of consequential uncertainty.
What a sourcing event should produce
| Output | What it must establish |
|---|---|
| Decision brief | The need, alternatives considered, recommendation, unresolved risks and accountable decision owner. |
| Comparable economics | A common demand scenario, scope boundary, time horizon and treatment of transition costs. |
| Evidence record | What was demonstrated, what is only a claim, and where the supporting material lives. |
| Commercial agreement | The commitments that made the winning proposal acceptable, reflected in executable terms. |
| Operating handoff | Who owns acceptance, service measurement, invoices, change requests, notice dates and exit readiness. |
Treat estimated savings carefully. Distinguish lower spend, avoided future increases, demand reduction and productivity assumptions. State the baseline and period. Do not add overlapping benefits or describe an unapproved business case as realized value.
A purchase request is not the whole problem
Gather actual usage, employee roles, integration needs and the operating owner’s rollout plan. Compare viable options against the same adoption scenario. An inexpensive license can become an expensive decision if the business cannot implement it or the contract prevents reducing unused capacity.
The operational stage gates
Use these gates as a working review sequence. A gate is a decision that the available evidence is sufficient to proceed, not a demand for a large document. Scale the effort to the consequence and retain the reasoning when a step is simplified.
01 Define the need
- Inputs
- An approved business problem, current process and demand information.
- Activities
- Challenge inherited scope, agree the outcome and identify decision owners.
- Output
- A scoped requirement, budget assumptions and stakeholder responsibilities.
- Common failure
- A preferred product is treated as the requirement.
- Next gate
- The sponsor accepts the need and the boundaries.
02 Understand the market
- Inputs
- The requirement, constraints and known incumbent dependencies.
- Activities
- Map viable suppliers and substitutes; validate capacity and switching effort.
- Output
- An evidence-backed options map with consequential unknowns.
- Common failure
- A list of brand names is mistaken for viable alternatives.
- Next gate
- The team can explain which routes are feasible and what must be verified.
03 Create competition
- Inputs
- The viable field, decision criteria and internal procurement rules.
- Activities
- Select the route, define the response and issue consistent information.
- Output
- Comparable offers or a justified alternative sourcing approach.
- Common failure
- A formal event is launched without capacity to evaluate it.
- Next gate
- Responses contain enough evidence for a meaningful comparison.
04 Evaluate options
- Inputs
- Proposals, demonstration evidence, references and normalized costs.
- Activities
- Apply gates, score independently, reconcile differences and assess risk.
- Output
- A decision record explaining the preferred option and accepted tradeoffs.
- Common failure
- A high average hides a disqualifying operational gap.
- Next gate
- The authorized decision maker accepts the recommendation and open issues.
05 Negotiate
- Inputs
- The evaluation, executable alternatives and approved mandate.
- Activities
- Prepare conditional packages, resolve gaps and maintain an issue log.
- Output
- A complete economic and risk package within delegated authority.
- Common failure
- A concession is offered without a corresponding return.
- Next gate
- The package is acceptable as a whole, not only on unit price.
06 Contract
- Inputs
- The negotiated package, scope and specialist review requirements.
- Activities
- Reconcile documents, define acceptance and record operating obligations.
- Output
- An approved agreement and accessible obligations register.
- Common failure
- A proposal promise is not carried into the contract.
- Next gate
- Required approvals and executable documents are complete.
07 Implement
- Inputs
- The agreement, delivery plan and committed buyer resources.
- Activities
- Manage dependencies, test deliverables and resolve acceptance defects.
- Output
- A working service or capability with a documented handover.
- Common failure
- The project reaches a date but the business is not ready to operate.
- Next gate
- The designated owner accepts useful delivery against agreed evidence.
08 Govern
- Inputs
- Accepted delivery, service measures and obligations.
- Activities
- Monitor performance and invoices, resolve issues and control changes.
- Output
- A current record of outcomes, demand, risk and open actions.
- Common failure
- Reviews report activity but never close recurring problems.
- Next gate
- Material changes and renewal decisions have current evidence and owners.
09 Renew / exit
- Inputs
- Usage, performance, notice terms, alternatives and transition lead time.
- Activities
- Choose stay, reshape or move; complete approvals and authorized actions.
- Output
- A deliberate next arrangement or completed transition.
- Common failure
- The team waits for the renewal quote while notice options close.
- Next gate
- Continuity and obligations are managed, and the next review is owned.
Sources & context
- CIPS · Strategic sourcing ↗Professional foundation: sourcing connects organizational objectives, market understanding and ongoing review.
- CIPS · Procurement and supply cycle ↗Reference lifecycle. Our nine-stage route is an original editorial synthesis, not the CIPS 13-step model.
The decision frameworks and illustrative examples are original editorial guidance. Sources support the stated context; they do not endorse this guide.