PwC's 2024 Digital Procurement Survey found that 94% of organizations have deployed source-to-pay tools. Yet the same survey found that only 43% of procurement processes are actually digitized. The remaining 57% run on spreadsheets, email, and manual workarounds — often layered on top of the very tools the organization paid for. The gap between software ownership and software adoption is the most expensive procurement problem nobody measures.
Spend Matters documented a 70% failure rate for procurement digital transformations. Broader research from McKinsey, BCG, and Bain converges on a 70-84% failure range for enterprise digital transformation programs. The root cause across all of these studies is consistent: organizations deploy technology before redesigning the processes the technology is supposed to support. They automate the spreadsheet instead of replacing it. The technology works. The adoption fails.
The framework: five phases for adoption that sticks
The framework below is built on the principle that adoption failures are people and process failures, not technology failures. Every phase addresses a specific adoption risk. Every step within a phase includes what skipping it breaks. The framework works for teams moving from spreadsheets to a first procurement platform and for organizations replacing an under-adopted legacy system.
Phase 1: Diagnose before you prescribe
What it is: Before evaluating any software, map your current procurement workflows as they actually operate — not as the process documentation says they operate. Document where spreadsheets are the system of record, where data is re-entered between systems, where approvals happen over email, and where supplier information lives in personal drives rather than shared repositories.
What it produces: A current-state process map that identifies every manual handoff, every data re-entry point, and every spreadsheet that functions as a de facto system of record. Include cycle times for key workflows: PR-to-PO, supplier onboarding, contract approval, invoice processing.
What skipping this step breaks: Without a current-state map, you cannot distinguish between a process problem and a technology problem. Teams that skip diagnosis buy software to solve symptoms they have not properly identified. The most common outcome: the new tool replicates the old spreadsheet workflow in digital form, preserving every inefficiency.
Phase 2: Redesign the process, not the tool stack
What it is: Using the current-state map from Phase 1, redesign each workflow for efficiency before selecting any technology. Eliminate steps that exist only because the spreadsheet required them. Standardize approval paths. Define what "one source of truth" means for supplier data, contract data, and spend data. Design the intake-to-pay flow that the technology will support.
What it produces: A future-state process design that is technology-agnostic. The design describes what the workflow should look like regardless of which software platform you select. It includes standardized data fields for suppliers, contracts, and purchase requests. It defines approval rules, role-based access, and escalation paths.
What skipping this step breaks: This is the step that separates the 30% of successful transformations from the 70% that fail. Organizations that select software before redesigning processes end up configuring the tool to match broken workflows. The software becomes a more expensive version of the spreadsheet it was supposed to replace. Adoption stalls because users see no improvement in their daily experience.
Phase 3: Select software against process requirements, not feature checklists
What it is: Evaluate technology platforms against the future-state process design from Phase 2. The selection criteria are: can this platform support the redesigned workflow without requiring workarounds? Does it integrate with the ERP system you cannot replace? Can users complete the most common tasks — raising a purchase request, approving an invoice, finding a supplier — in fewer steps than they take today?
What it produces: A shortlist of 2-3 platforms evaluated against process fit, not feature count. A selection decision based on demonstrated workflow support in your specific operational context — tested with real procurement scenarios, not vendor demos.
What skipping this step breaks: Feature-driven selection produces shelfware. Organizations buy platforms with capabilities they never configure because the features solve problems the organization does not have, while the workflows the organization actually runs require workarounds the vendor did not demonstrate. Users default to spreadsheets because the platform does not support how they actually work.
Phase 4: Pilot with one business unit, one module, measurable outcomes
What it is: Deploy the selected platform for a single procurement workflow — purchase requisitions, supplier onboarding, or contract management — in a single business unit. Define success metrics before going live: cycle time reduction, user adoption rate, data quality improvement. Run the pilot for 90 days. Collect feedback weekly. Fix configuration issues before they compound.
What it produces: A working implementation with demonstrated results in a contained environment. Measurable before-and-after data on the workflow the pilot addressed. A list of configuration adjustments needed before broader rollout. A group of internal advocates who have used the system and can speak to its value.
What skipping this step breaks: Enterprise-wide rollouts without a pilot produce enterprise-wide failure. Issues that could have been caught in a contained pilot — integration failures, configuration gaps, training deficiencies — affect every user simultaneously. The support burden overwhelms the implementation team. User trust in the system collapses before it has a chance to build.
Phase 5: Force adoption — disable spreadsheets, measure compliance, and scale
What it is: After the pilot demonstrates results, disable the spreadsheet-based workflow for the pilot group. Require all transactions in that workflow to flow through the new system. Measure compliance weekly. Address resistance case by case — most resistance is a configuration or training issue, not a technology rejection. Scale the system to additional business units and additional workflows, one at a time, applying the same pilot-and-disable pattern.
What it produces: A procurement technology adoption program that expands through demonstrated results rather than executive mandates. Each expansion has a reference group of users who can speak to the system's value. Compliance metrics show adoption rates, not just deployment status.
What skipping this step breaks: Organizations that deploy software but allow spreadsheets to continue operating in parallel never achieve adoption. Users follow the path of least resistance, and the path of least resistance is always the spreadsheet they already know. Parallel operation also creates data fragmentation: half the spend flows through the system, half continues in spreadsheets, and procurement never has a complete picture. The 94%/43% gap between tool ownership and process digitization is a direct consequence of skipping this step.
The failure mode that kills most adoption programs
The single most common failure is skipping Phase 2 — redesigning processes before selecting software. Organizations feel urgency to deploy technology, so they collapse Phases 1-3 into a single vendor evaluation process. They select a platform based on feature checklists, configure it to match their existing workflows, and wonder why adoption stalls.
The second most common failure is skipping Phase 5 — allowing spreadsheets to coexist with the new system indefinitely. Every organization that measures the 94%/43% gap between tool ownership and process digitization has made this mistake. The new system is deployed. The old spreadsheets continue operating. Users have no incentive to change. Procurement leadership reports that the transformation is "complete" because the software is installed, while the actual work continues exactly as it did before.
Hackett Group's 2025 Key Issues research quantifies what correct execution produces: "Digital Masters" — organizations that execute the full adoption framework — deliver 2.03 times higher savings as a share of spend and 2.6 times higher ROI than average organizations. Deloitte's Global CPO Survey 2025 adds that leaders meet or exceed their savings plans 96% of the time, compared with 80% for followers. The gap is not the technology. It is the adoption discipline.
Operational checklist: gate checks for each phase
- Phase 1 gate: Current-state process map exists and has been validated by the people who actually execute the workflows — not just process documentation owners. All spreadsheet-based workflows are documented.
- Phase 2 gate: Future-state process design is complete, technology-agnostic, and signed off by process owners. Approval paths, data standards, and role definitions are specified before any software is evaluated.
- Phase 3 gate: Platform evaluation is scored against process fit, not feature count. At least one real procurement scenario has been tested on the shortlisted platforms using your organization's actual data and workflows.
- Phase 4 gate: Pilot has completed 90 days. Before-and-after metrics exist for the pilot workflow. User feedback has been collected and configuration adjustments made. Internal advocates have been identified.
- Phase 5 gate: Spreadsheet version of pilot workflow is disabled. Compliance rate exceeds 90%. Expansion to next business unit or next workflow has a defined timeline with success metrics.
What this means in practice
- Audit your current technology adoption. Count how many procurement workflows still run on spreadsheets despite having a tool deployed. The 94%/43% gap is your adoption deficit. If you do not measure it, you cannot close it.
- Map one end-to-end workflow — PR-to-PO is the most common starting point. Document every step, every system, every spreadsheet. Show the map to the people who execute the workflow. Ask them where they work around the tool. Their answers will surface the process problems your technology deployment missed.
- Redesign that single workflow before touching any software. Eliminate steps that exist only because of the spreadsheet. Define what "done" looks like in the new process. Only then evaluate whether your current tool can support the redesigned workflow.
- Run a pilot for the redesigned workflow with one business unit. Set a hard deadline — 90 days — after which the spreadsheet version is disabled. Do not extend the deadline. Parallel operation is the mechanism by which most adoption programs fail.
- Scale one workflow at a time. Organizations that attempt to deploy procurement technology across all categories and all workflows simultaneously produce the 70% failure rate. Organizations that expand through demonstrated results produce the 2.6x ROI.
Frequently asked questions
How long does a full procurement technology adoption program take?
A complete program across multiple categories takes 12-24 months. The first phase — pilot on a single workflow with one business unit — should produce measurable results within 90 days. Organizations that try to compress the timeline by running multiple pilots simultaneously risk the coordination failures that produce the 70% failure rate.
What if my organization already has a procurement platform that nobody uses?
Start with Phase 1 — map the workflows that bypass the platform. Identify why users default to spreadsheets. The answer is usually one of three things: the platform does not support the actual workflow (process misfit), users were never trained (adoption gap), or the platform requires more steps than the spreadsheet (usability deficit). Each has a different fix. Buying a new platform before diagnosing why the current one failed guarantees the same outcome.
What measurable results should I expect from correct adoption?
Hackett Group data shows Digital Masters achieve 2.03x higher savings as a share of spend. Operational benchmarks from mature procurement technology deployments include: PR-to-PO cycle time under 24 hours (from 5-7 days manual), contract compliance above 90% (from 60-70%), supplier data accuracy above 95%, and procurement operating cost below 1% of managed spend. These outcomes require the full five-phase framework. Skipping phases reduces the outcome proportionally.
Data sources
- PwC — "Digital Trends in Operations Survey 2024". Accessed July 2, 2026.
- Spend Matters — Procurement technology research and analysis. 70% digital transformation failure rate. Accessed July 2, 2026.
- The Hackett Group — "2025 Key Issues Study". Digital Masters deliver 2.03x savings, 2.6x ROI. Accessed July 2, 2026.
- Deloitte — "Global CPO Survey 2025". Leaders meet savings plans 96% of the time vs. 80% for followers. Accessed July 2, 2026.
- Procurement Tactics — "12 Procurement Trends Set to Reshape 2026". Hackett Group data on digital procurement ROI. Accessed July 2, 2026.
- Suplari — "Procurement Trends 2026: Key Data, Priorities, and Pitfalls". Procurement workloads rising 10% vs. 1% budget growth. Accessed July 2, 2026.