It is tempting to start a procurement transformation meeting by opening software screens. A more useful starting point is one purchase completed last month. Where did the requirement originate? Which information was entered twice? Why was the quotation delayed? Where is the final decision stored? These questions reveal what digitisation actually needs to improve.
The OECD's digital procurement study considers technology alongside process transformation. Its scope is public procurement; the approach below is a practical way for private companies to examine their own operations, rather than a set of public-sector requirements transferred to their business.
Define the boundary of the work
Requisitioning, RFQs, e-auctions and ordering are connected but distinct stages. Write down the information produced at each stage and who owns it. If a buyer has to re-enter the quantity already supplied by the requester, there is a concrete improvement opportunity.
A narrow first phase is easier to evaluate. Improving the handover from requisition to auction gives the team a clearer test than changing every department's processes at once. Agree responsibilities across procurement, finance and IT before selecting the first workflow. Also identify information that must remain in another system rather than assuming the new platform will replace everything.
Choose the pilot category deliberately
Start with a recurring requirement, a clear specification and several suitable suppliers. A unique piece of critical production equipment introduces unnecessary uncertainty into the first trial. The pilot's purpose is to demonstrate a workable end-to-end process, not to manufacture the largest possible savings number.
For example, a pilot might collect requirements from two business units, transfer approved items into one sourcing event and compare quotations against common questions. Record missing fields, repeated data entry and points where suppliers need help. Those observations become the improvement list for the next event.
Establish a baseline before changing the process
Measure the same things before and after implementation. Time from requisition creation to event publication, the proportion of usable quotations and the effort required to prepare the comparison report are useful starting measures. Separate elapsed time from working time: an approval waiting over a weekend does not consume the equivalent number of staff hours.
Keep scope visible in the price comparison as well. A lower quantity or a more flexible delivery date can change the quoted price. Comparing that price directly with a previous purchase may attribute savings to the project that it did not create. Agree the reference-price method with finance before reporting the result.
Make adoption part of the design
Training should include real work, not just a presentation of features. Ask a requester to create a requirement, correct missing information and find the result. Test the supplier journey from invitation through login to submitting a quotation. Put a short guide at the point where help is actually needed.
Tenflex offers a concrete pilot flow through individual or Excel-based requisition items and the transfer of approved items to an auction. If ERP integration is required, define its data scope separately. Establish who develops the connection and who handles failed transfers before going live. Once the pilot works, expand the process using the evidence collected rather than assuming that every category will behave the same way.
