01Why most procurement digitalization projects fail
Studies on organizational digital transformation converge on one finding: the majority of projects that fail to meet their objectives are not technology failures. They are change management failures.
In the procurement cycle, resistance is particularly strong. Operational teams, buyers and accountants have developed habits around Excel and email. Changing those habits requires an impulse that can come from neither IT nor the procurement team alone.
CIPS, in its publications on procurement organization maturity, identifies explicit CEO involvement as one of the factors most correlated with P2P transformation project success, on par with the quality of the chosen solution.
02The role only the CEO can play
The CEO holds three levers that nobody else in the organization has. First lever: authority over behavior. When the CEO announces that purchases without an approved purchase request will no longer be reimbursed, behaviors change. When IT or the procurement team says it, the message lands less.
Second lever: cross-functional vision. Procurement digitalization touches every function: operations (who create purchase requests), finance (who approves and accounts), the executive team (who arbitrates budgets), suppliers (who receive purchase orders). Only the CEO has the natural authority to align these stakeholders.
Third lever: budget legitimacy. Even if the cost of a P2P platform suited to African SMEs is low (Procura starts at 75,000 XOF per month), the project must be sponsored by the executive to prevent it being undermined by operational resistance.
03The three decisions only the CEO can make upfront
First decision: define non-negotiable rules. Which purchases must go through the platform? From what amount? Which procurement categories are covered at launch? These rules must be communicated directly by the CEO, not documented in a procedure manual nobody reads.
Second decision: appoint an internal champion. One person, not a committee, leads the operational rollout: supplier database configuration, approval tier setup, user training. This person must have the CEO's visible backing to enforce the process.
Third decision: set a hard cutover date. Coexistence of the new system and Excel for months is the primary cause of adoption failure. The CEO sets a date after which Excel is no longer accepted for procurement. This decision is hard to hold, but it is the only one that guarantees full adoption.
04How to bring teams and suppliers on board
Internal teams are onboarded in three stages. First, a short demonstration of the new cycle focused on what changes for each profile: the requester creates their PR in two minutes and tracks its status in real time; the approver validates from their phone; the accountant receives the invoice already matched against the PO.
Next, a test period on a limited procurement category with real data. This allows everyone to get familiar with the tool before the full cutover. Finally, the CEO's message at cutover: a clear communication to all relevant staff, with the date and rules.
Suppliers onboard naturally, because the supplier portal simplifies their daily life: they see the status of their invoices in real time, receive their purchase orders directly on the platform, and no longer need to call the accountant to find out when they will be paid.
05What a 1-week deployment changes in the equation
Implementation duration is one of the main barriers to the procurement digitalization decision in an SME. A six-month project with an external consultant mobilizes internal resources, creates prolonged uncertainty, and demotivates teams before the launch.
Procura is usually deployed within a week. Day 1: discovery call and initial configuration. Days 2 and 3: personalized demo with the company's data in a sandbox environment. Days 4 to 7: first complete cycle in production, from purchase request to supplier payment. From week 2: deployment to all users.
This speed changes the risk calculation for the CEO. A one-week project is a low-risk experiment. If it does not produce the expected results, it can be stopped without major cost. In practice, organizations that cross this threshold never go back.