Buyer-side resource
A strategic sourcing process connects the business need to supplier selection, negotiation, implementation, and measured results. These seven steps give buyers a repeatable route while keeping evidence and approval responsibilities visible.
Strategic sourcing is a structured way to choose how an organization will meet a business need through suppliers. It combines demand, market alternatives, total cost, risk, and execution planning. Purchasing carries out an approved transaction; sourcing establishes whether the requirement, supplier approach, and commercial arrangement make sense.
| Question | Purchasing focus | Strategic sourcing focus |
|---|---|---|
| What are we buying? | Order the specified item or service. | Test demand, specifications, and viable alternatives. |
| What is a good price? | Check the quoted or contracted price. | Compare equivalent scope, whole-life cost, and leverage. |
| When is the work complete? | Receive and pay for the order. | Confirm outcomes and revisit assumptions over the lifecycle. |
A low-risk repeat purchase may need only established purchasing controls. A critical software replacement with migration, renewal, and continuity exposure needs a broader sourcing decision. Scale the work to the decision rather than running a large event for every request.
This is Sourcing Playbooks’ practical buyer-side sequence, not a claim that one universal seven-step standard applies to every organization. Some activities run in parallel, and new evidence can send a team back to requirements or market analysis.
Describe the business outcome before naming a product. Identify the decision owner, contract deadlines, current service problems, and the cost of doing nothing. Agree what is outside scope; an unresolved scope boundary will become a pricing dispute later.
Reconcile invoices, entitlements, usage, and forecast demand. Separate essential requirements from preferences and specify how suppliers will demonstrate them. For software, named users, active users, environments, and API volumes may produce very different commercial models.
Compare supplier segments and alternatives, not just familiar names. Test availability, implementation capacity, concentration, switching barriers, and evidence quality. Record what is observed, what a supplier claims, and what needs validation.
Choose the route: competitive event, targeted negotiation, phased transition, extension, or a justified single-source approach. Set evaluation criteria, pricing scenarios, negotiation objectives, and fallback options before supplier proposals influence them.
Use an RFI when material market questions remain; use an RFP when suppliers can respond to a sufficiently clear requirement. Issue consistent clarifications. Evaluate mandatory gates before weighted scoring, normalize proposals, and test claimed capabilities with evidence.
Negotiate the complete economic and delivery position: price basis, scope, implementation, service levels, renewal, termination, and transition. Convert material promises into the appropriate contract documents and resolve conflicting schedules before signature.
Assign an implementation owner, acceptance criteria, invoice controls, service measures, and renewal calendar. Compare actual consumption and performance with the approved baseline. Feed missed assumptions and new demand into the next sourcing decision.
The existing playbook library uses seven preparation stages: intake, category profile, market scan, supplier discovery, cost drivers, shortlist strategy, and event readiness. Those stages deepen the early work in this full lifecycle; they are not a second name for the same seven steps.
Use the preparation worksheets mainly during steps 1–4 and to establish readiness for step 5. RFx execution, negotiation, contracting, implementation, and performance governance then carry the decision forward. The Full Sourcing Playbook System remains focused on connected sourcing preparation artifacts.
| Role | Owns | Must not be assumed |
|---|---|---|
| Business sponsor | Business outcome, resources, and authorized commercial decision | Sourcing cannot silently accept a changed business requirement. |
| Sourcing lead | Market approach, event integrity, comparison, negotiation coordination | Leading an event does not confer contract-signature authority. |
| Finance | Baseline, affordability, TCO assumptions, benefits measurement | A supplier discount is not automatically realized savings. |
| Technical and service owners | Fit, integration, acceptance, ongoing service | A successful demo is not proof of production readiness. |
| Legal, security and privacy reviewers | Review within their assigned authority and escalation of exceptions | An aggregate score cannot override an unresolved mandatory gate. |
Record each approval, its scope, conditions, and date. If the evaluation reveals a major requirement change, return it to the requirement owner rather than rewriting criteria to favor the preferred supplier.
A fictional multi-site business needs a common service-management platform. Its existing applications create duplicate work, but consolidating immediately would exceed the integration team’s capacity. The sponsor therefore defines a phased rollout as a requirement rather than treating it as a post-award problem.
The team reconciles users and current costs, investigates three viable providers, and runs a common workflow demonstration. Security and export capability are mandatory gates. Weighted evaluation compares functionality, three-year TCO, implementation feasibility, and support. Negotiation focuses on migration acceptance, subscription start dates, renewal pricing, and usable data export.
The award is conditional on an approved integration plan and contract closure. Quarterly governance checks adoption, duplicate-license retirement, and support outcomes. A delayed legacy shutdown changes the cost forecast and becomes an input to the next review. See the completed scenarios and worked evaluation for the assumptions and award logic.
Use the Sourcing Intake Playbook to start the decision, Supply Market Analysis to test alternatives, and Should-Cost / TCO to expose economic assumptions. The workbook examples show preparation artifacts, not completed customer engagements.
For the decision structure behind the steps, read the strategic sourcing framework. For supporting capabilities and selection questions, use the tools comparison guide.
No. Organizations group the work differently. This seven-step model is a practical editorial structure; retain the decisions and evidence even when local stage names differ.
No. Use the market evidence, scope, risk, and buying constraints to choose the route. Document why a targeted negotiation, extension, or other approach is appropriate.
Build the schedule backward from the required service date, allowing for evidence gathering, supplier response, approvals, negotiation, and transition. Complexity and readiness matter more than a universal timetable.
Templates organize inputs, assumptions, and approvals. They support the process but cannot replace the buyer’s market assessment or accountable decisions.
