Articles / Strategy
A 90-day roadmap for adopting procurement technology
You do not need a multi-year transformation to benefit from modern tools. A practical plan for the first three months, for public and private teams.
Most procurement technology projects fail for the same reason: they begin with a tool and end with a disappointed team. A better path is to start with a problem, prove value quickly, and build from there. This plan fits into ninety days and works for a small municipal team as well as a corporate department.
Days 1 to 30: see clearly
Goal: know where time and money go.
- Map the process. From need to payment, who does what, and where do requests wait? Sketch it on a whiteboard.
- Collect a year of spend data. Do not wait for it to be perfect. See spend analytics for how to clean and classify it.
- Interview users. Ask buyers, budget holders and suppliers what frustrates them. The same three complaints usually come up repeatedly.
- Choose the baseline numbers. Cycle time from request to order, share of spend under contract, invoices processed manually, cost per tender.
Output: a one-page picture of the current state and a ranked list of problems.
Days 31 to 60: fix one thing
Goal: a visible, measurable win.
Pick one problem from the list. Good candidates:
| Problem | Candidate fix |
|---|---|
| Notices full of errors | Checklists, validation, e-tendering standards support |
| Slow payment, many manual invoices | E-invoicing and PO matching |
| Contracts renew unnoticed | A renewal calendar, then contract management |
| Hours lost reading long bids | Generative AI assistance with human review |
| Surprises from suppliers | Risk monitoring for the top twenty |
Run it as a small pilot with one team. Set the success measure in advance.
Output: a pilot with before-and-after numbers.
Days 61 to 90: lock in and plan
Goal: make it stick and decide what is next.
- Write the process down. A one-page standard is better than a long policy that nobody reads.
- Train the team. A short session and a named contact for questions.
- Share the results. Show leadership the numbers. Savings, time or errors avoided.
- Plan the next step. Use what you learned to choose the second pilot.
- Review risks. Data protection, security, supplier lock-in and, for public bodies, procurement law applied to the purchase of the tool itself.
Output: a standard process, a trained team, and a plan for the next quarter.
Principles that keep it on track
- Data before dashboards. Clean inputs matter more than clever tools.
- Small and visible. A modest win in ninety days builds more support than a grand plan.
- People first. Technology that makes life harder for buyers or suppliers will be bypassed.
- Standards over custom. Use open standards, such as open contracting data and Peppol, to avoid lock-in.
- Human accountability. Automation should speed work up, not hide who decided.
Buying the tool itself
If you are a public body, remember that choosing software is also a procurement. Define requirements around outcomes and open standards, allow for data export, and test with real data in the evaluation. For corporate buyers, ask for references from customers of a similar size and a pilot period before committing to a multi-year contract.
Measuring success
Revisit your baseline numbers after ninety days and again after six months. If a change did not move a number, find out why before expanding it.
The bottom line
The technology to improve procurement is available today. What separates teams that benefit from those that do not is rarely budget. It is focus: one problem, a clear measure, and the discipline to finish before starting the next.