In April 2026 Saudi Arabia published its Vision 2030 annual report for 2025 and, with it, marked the start of the programme’s third and final phase, running from 2026 to 2030. The framing of that phase is the signal worth reading. The first phase was about laying foundations and the second about building at scale. The third is described, in the Kingdom’s own words, as the peak of implementation: sustaining delivery, maximising returns, and proving that a decade of announcements produced measurable outcomes. Vision 2030 has moved from launch framing into delivery assessment, and that shift does not stop at the programme owners. It runs all the way down to the suppliers who build the work.
For a contractor, manufacturer or service company serving a national programme, in Saudi Arabia or from across the Gulf, this changes what a client is actually buying. When the emphasis was on getting things started, a capable supplier who could mobilise was enough. When the emphasis is on delivery and measurable return, the client needs more: proof, continuously, that the work is on track, that risks are managed, and that quality is being met. The bar is no longer can you do the work. It is can you show, at any moment, that you are doing it well.
Delivery assessment cascades downward
A programme judged on measurable delivery has to measure its suppliers, because its own numbers are only as good as theirs. Phase three explicitly expands the private sector’s role and increases local content, pulling more suppliers into the delivery net, and it maintains the heavy monitoring of initiatives that the annual reports reflect. The reporting culture at the top becomes an evidence expectation at every tier below it. A supplier that cannot feed clean delivery data upward becomes the weak link in someone else’s scorecard.
There is a commercial edge to this that suppliers underrate. A programme owner being measured on delivery will, over time, prefer the suppliers who make that measurement easy: the ones whose data is clean, whose reports arrive on time, and whose risks are visible early. That preference is quiet but durable. It shows up in who gets shortlisted, who gets the benefit of the doubt when a schedule slips, and who is invited back for the next package. Evidence is not just defensive; it is how a supplier becomes the easy choice. It helps to see what a programme owner in a delivery-focused phase actually asks of a supplier, because it is more than good work. The view below takes the areas where delivery now has to be evidenced. For each, what the programme owner asks, the record a supplier needs, and where suppliers without a system fall short. Tap any area.
What a delivery-phase programme asks of a supplier
Tap an area for what the owner asks, the record a supplier needs, and where suppliers fall short
Read down the third row of each area and the same lesson repeats. In a delivery phase, the gap that hurts a supplier is rarely the work itself. It is the inability to prove the work: readiness asserted but not evidenced, progress reported but not backed, problems handled but not shown, numbers compiled by hand and easily challenged. A supplier that does good work and cannot demonstrate it competes on equal terms with one that does poor work and hides it, until the day both are tested, and neither can show the difference cleanly.
What a supplier delivery layer holds
To be clear about scope: this is not the enterprise programme-management system a giga-project owner runs to steer the whole endeavour. That belongs to the programme, and building it is not what any supplier needs. What a supplier needs is the layer on its own side of the contract, the one that produces clean delivery evidence as work happens, so the client’s questions are answered from a record rather than a scramble. It sits alongside a firm’s existing tools and complements a project visibility platform, and where local content is in play it connects to the same discipline as ICV reporting. In practice it is four things.
Readiness and mobilisation record
Evidence per work package that the team, plant, permits and approvals are in place before work starts, so readiness is shown rather than asserted in a meeting.
Live progress tracking
Progress tied to milestones and the underlying work, so a percentage complete reconciles to evidence and a status is backed by something real.
Exception and risk register
Each issue logged with its impact, action and outcome as it happens, so problems are seen to be caught and handled rather than surfacing late.
KPI and document packs
Reporting and handover documents drawn from operational data, so the programme’s measures and each gate’s paperwork are ready on time and reconcile to the work.
| What the client buys | Launch phase | Delivery phase |
|---|---|---|
| Readiness | A capable supplier | Evidenced readiness per package |
| Progress | A status update | Progress backed by the work |
| Problems | Raised when unavoidable | Caught, escalated and shown |
| Reporting | Compiled for the meeting | Drawn from operational data |
In a delivery phase, the bar is no longer whether a supplier can do the work. It is whether they can show, at any moment, that they are doing it well. The firms that can prove delivery win the next contract; the ones that cannot compete on price alone.
A clear word on what we build. We build software. We are not a programme-management office, a government reporting platform, a management consultancy, or a legal, tax or labour-law adviser, and we do not run national programmes, set their KPIs, or advise on Saudi regulatory requirements. Those belong to the programme owners, their advisers and the relevant authorities. We build the supplier-side delivery-evidence layer, and it is not a safety-critical control system for construction or engineering. Responsibility for the work, its safety and its compliance stays with the firm doing it.
Questions suppliers are asking
The third phase, from 2026 to 2030, is described by the Kingdom as the peak of implementation, focused on sustaining delivery, maximising returns and reinforcing resilience, with the 2025 annual report reflecting a strong emphasis on measurement and delivery assessment. For suppliers, the practical change is that programmes increasingly judge and are judged on measurable delivery, which raises the expectation that a supplier can evidence its own progress, quality and risk management, not just perform the work.
Yes, where you serve Saudi programmes, which many Gulf contractors, manufacturers and service firms do. The delivery-evidence expectation follows the programme, not the supplier’s home market, so a UAE firm working on a Saudi national programme meets the same bar as a local one. The same capability also helps on large programmes elsewhere in the Gulf, where the direction toward measured delivery is shared. The evidence layer is portable; the specific KPIs and contract terms differ by client.
No. We are an independent software engineering company. We are not a programme-management office, a government or programme reporting platform, a management consultancy, or a legal, tax or labour adviser, and we are not affiliated with or endorsed by Vision 2030, the PIF, or any authority. We do not run programmes, set KPIs, or advise on Saudi requirements. We build the supplier-side software that produces clean delivery evidence. The programme, the rules and the advice stay with the owners and qualified advisers.
Both, indirectly. It does not write bids or make promises for you. What it does is let you show a track record of evidenced delivery, and answer a client’s questions from a clean record during a project. On a national programme where the client is measured on delivery, being the supplier who makes their reporting easy and their risk visible is a real competitive advantage that compounds from one contract to the next. The work still has to be good; this proves that it is.
No, and that boundary matters. We do not build safety-critical control systems for construction or engineering, and this layer does not manage or assure the physical safety of the work. It records delivery: readiness, progress, exceptions, KPIs and documents. The engineering, the safety and the compliance of the work itself stay with the firm doing it and its qualified professionals. The software evidences delivery; it does not perform or certify the build.
Vision 2030 spent a decade proving that the Kingdom could launch at scale. Its final phase is about proving it can deliver, and that shift is quietly rewriting what a good supplier looks like. The winners over the next five years will not only build well; they will be able to show, at every stage and on demand, that they built well: ready, on track, risks handled, quality met, documents in order. That evidence is buildable, and it is ordinary software work done against a market that has decided, at every tier, to measure what it delivers.
References to Saudi Vision 2030, its third phase, the 2025 annual report, and the figures described are descriptive of publicly available announcements as reported at the time of writing. Figures, including the phase dates, the initiative count and the progress reported, are drawn from public reporting and official publications and are point-in-time. BY BANKS is an independent software engineering company; we design and build software and hand it over. We are not a programme-management office, a government or programme reporting platform, a management consultancy, a legal, tax or labour adviser, or a provider of safety-critical construction systems, and we are not affiliated with or endorsed by Vision 2030, the PIF, or any authority. On any engagement, the firm owns its delivery, safety, and compliance decisions and responsibility for their implications. This article is not legal, regulatory, or professional advice; readers should obtain qualified advice and rely on official sources for current requirements. Public sources used in this piece are listed on our Sources and Data page.
Ready to Build Something?
If this resonated, let's talk about how we can apply these ideas to your business.
Start a Conversation