From 139 days to 57: how a Kuwait bank transformed procurement with AI process engineering
139 days. That was the average procurement cycle at a mid-sized Kuwaiti bank before the project began. Seven stakeholder sign-offs, manual vendor forms passed between departments, and approval queues that aged out before anyone acted on them. The bank had tried to fix it before. Consultants had documented the pain. Nothing changed.
The transformation that followed cost $200 per month and launched the same day the redesigned process was approved. No six-month implementation. No change-management workshops that stretched into the following quarter. One structured conversation, one E-S-S-A-M analysis, and a redesigned SOP deployed via WhatsApp to the people who actually ran procurement.
This is the case study a banking COO should share with their team — not because the numbers are impressive (though 59% cycle-time reduction and 106.9% process efficiency improvement are hard to argue with), but because the approach challenges a premise the consulting industry has spent decades reinforcing: that fixing a broken banking process requires a large budget, an extended engagement, and an external team.
It does not.
What the old procurement process actually looked like
Before the project, the bank's procurement cycle was built on habits, not design. A vendor request entered the system and then moved — slowly — through a chain of approvals that had accumulated over years. No single person had ever sat down and asked whether each step was necessary. They were simply inherited.
The process had 7 sign-offs before a purchase order could be issued. Two of those sign-offs were, on close inspection, redundant: they existed because a department head had been added to the chain after an audit three years earlier and no one had removed the original approval node. The vendor intake form had 23 fields. Fewer than half were used in any downstream decision.
Mohammed Razouki, the bank's IT Process Improvement Head, described the operating reality plainly: "We knew the process was slow, but every time we tried to map it, we ended up arguing about who owned which step. The map kept changing before we could act on it."
Dhuha Al-Kouz, Operations Manager, put the cost in human terms: "By the time a purchase order reached final sign-off, the team that requested it had often found a workaround or gone without. We were approving things that no longer mattered."
The process had no single point of failure. It had dozens of small ones, distributed across departments, embedded in software no one wanted to reconfigure, and defended by stakeholders who had built their authority around it.
How E-S-S-A-M applied to a banking procurement cycle
ESSAM uses a five-phase framework: Eliminate waste, Simplify & Standardize, Automate, Migrate low-value work. Each phase is applied in sequence, with the output of one feeding the input of the next. The framework is grounded in DMAIC principles (Define, Measure, Analyze, Improve, Control) but operates at conversation speed rather than consulting-engagement speed.
Here is how each phase applied to the Kuwait bank procurement case:
Phase 1: Eliminate
The baseline analysis surfaced 2 sign-offs that contributed no decision information. Neither the department head added post-audit nor the secondary finance reviewer had ever blocked or modified a procurement request. Their approvals were cosmetic, present because no one had formally questioned them.
Both were removed. The approval chain moved from 7 sign-offs to 5. That single change cut an average of 18 days from the cycle — not because the approvals were slow individually, but because each approval node introduced a queue wait of 5 to 12 days depending on the approver's availability.
The 23-field vendor form was also reviewed. 11 fields were collecting data that was never read downstream. Those fields were removed. The remaining 12 were reorganized into a logical intake sequence that reduced completion time for procurement staff from an average of 47 minutes to under 15.
Phase 2: Simplify & standardize
The bank had three vendor intake templates in active use across departments. Each had evolved independently. A vendor responding to requests from two departments might receive different forms with different terminology for the same information.
ESSAM produced a single standardized vendor template. The language was aligned to the bank's existing procurement policy documentation. Compliance review was built into the template structure rather than applied as a separate downstream step.
This standardization also resolved a downstream data problem: the procurement team had been spending time reconciling information from different form versions before passing requests to finance. That reconciliation step no longer existed.
Phase 3: Automate
The most time-consuming manual task in the old process was PO creation. A procurement officer was taking an approved vendor request, manually entering the data into the bank's ERP system, and generating the purchase order. This took between 40 minutes and 2 hours per PO depending on vendor complexity.
ESSAM automated PO creation directly from the approved vendor intake form. When a request cleared its final digital sign-off, the PO was generated without human re-entry. The procurement officer's role shifted from data transcription to exception handling.
This automation did not require new infrastructure. It connected to the bank's existing ERP via a configured integration rather than a custom build.
Phase 4: Migrate
The final phase addressed where approval decisions were being made. Under the old process, approvals were managed through a combination of email chains, a shared drive, and occasional in-person sign-offs. The location of each approval depended on approver preference rather than process design.
The redesigned process migrated all approval steps to a single digital procurement workflow. Each of the 5 remaining sign-offs happened within the same system, with a documented audit trail, automated reminders, and escalation triggers if an approval sat idle for more than 48 hours.
The migration also resolved a compliance exposure the bank had not fully quantified: under the old system, there was no reliable record of which specific individual had approved which request at which time.
The deployment method that made same-day go-live possible
WhatsApp penetration in Kuwait runs above 90%. Most of the bank's procurement staff already used it daily, both personally and for work coordination. ESSAM deployed the redesigned SOP through WhatsApp — not as a message, but as a structured, accessible process guide that staff could reference in the same interface they were already working in.
Zero training sessions were scheduled. Zero onboarding workshops. The redesigned process went live the same day the SOP was finalized. Staff accessed it on the devices they already carried.
Abdulla Al-Awadi, ESSAM's founder and a former Chief Security Officer at a bank in the region, has made this point repeatedly in conversations with operations leaders: "The biggest implementation risk isn't the technology. It's the gap between the process being approved and the process being used. If that gap is six months, you will spend most of that time managing resistance. If it's one day, the new way becomes the normal way before the old habits can reassert themselves."
The WhatsApp deployment method — documented separately in how WhatsApp deployment made the new process go live in a day — is not a workaround. It is a deliberate architectural choice that trades enterprise-software deployment risk for adoption speed.
The numbers, plainly stated
| Metric | Before | After | Change |
|---|---|---|---|
| Procurement cycle | 139 days | 57 days | -59% |
| Sign-off steps | 7 | 5 (all digital) | -29% |
| Process efficiency | Baseline | +106.9% | 106.9% improvement |
| Vendor form fields | 23 | 12 | -48% |
| PO creation | Manual, 40–120 min | Automated | Time eliminated |
| Deployment timeline | N/A | Same day | — |
The 106.9% process efficiency improvement is calculated against the baseline waste map, incorporating both the cycle-time reduction and the elimination of rework, reconciliation, and redundant handling steps. The 59% cycle-time reduction is the most visible metric, but the efficiency figure captures what actually changed in the daily work of the procurement team.
The cost of the ESSAM Pro plan at the time of engagement: $200 per month. A traditional consulting engagement scoped to deliver comparable process redesign in a banking procurement context typically runs between $50,000 and $200,000, with a delivery timeline of 3 to 6 months before any change reaches the operational floor.
The math is not subtle. See ESSAM pricing to apply the same framework to your banking process from $40 per month.
What the consulting industry gets wrong about banking process transformation
The standard consulting model for banking process improvement has three built-in assumptions, and all three work against fast outcomes.
First, it assumes that the problem requires external expertise to define. The procurement team at the Kuwait bank knew exactly what was wrong. They had known for years. What they lacked was a structured method to act on that knowledge without triggering a territorial dispute over process ownership.
Second, it assumes that a long diagnostic phase produces better recommendations. In practice, a longer diagnostic phase produces more documentation and more stakeholder meetings, neither of which changes how a purchase order gets approved on a Tuesday afternoon.
Third, it assumes that implementation is a separate project from design. Under this model, you pay for the map, and then you pay again to follow it. The gap between design and deployment is where transformation initiatives die — not because the analysis was wrong, but because the organizational conditions that made the process slow in the first place also make change slow.
ESSAM's architecture inverts all three assumptions. The analysis is conducted in conversation with the people who run the process. The redesign is produced within the same session. The deployment happens before the old process has time to defend itself.
Mohammed Razouki's observation after the project went live: "We spent three years talking about fixing this. It took one structured session to agree on what to cut and one day to put the new process in front of the team. I keep waiting for the catch."
There is no catch. The methodology is the catch — it simply does not require the infrastructure the consulting model was built around.
Where this approach has limits
This case study involves a procurement process that was slow primarily because of structural waste: redundant approvals, inconsistent templates, manual data re-entry. E-S-S-A-M addresses structural waste well.
It does not address processes where the slowness is caused by regulatory constraints that cannot be eliminated, contractual obligations with external parties, or decisions that genuinely require the judgment of a senior stakeholder and cannot be delegated or automated without compliance risk.
If your procurement cycle is 139 days because of a regulatory requirement for dual-authority approval on transactions above a certain value, ESSAM can help you optimize everything around that constraint, but the constraint itself is not a waste item to eliminate.
The Kuwait bank case succeeded in part because the two sign-offs that were removed had no regulatory or contractual basis. They existed because of organizational habit. That distinction matters, and any honest process redesign has to make it.
ESSAM accelerates expert judgment. It does not replace it.
The question every banking COO should ask
The Kuwait bank ran a 139-day procurement cycle for years. Not because no one noticed. Not because the team lacked the competence to fix it. Because the organizational conditions that make process change possible — clarity on what to cut, agreement on a single standard, authority to automate, a fast path to deployment — were never assembled at the same time.
ESSAM assembles them in a single structured conversation.
The question is not whether your procurement process has waste in it. Every procurement process that evolved organically over more than three years has waste in it. The question is whether you want to spend the next six months documenting it for a consulting report or the next session redesigning it for deployment.
For a complete view of what ESSAM has produced across different process types and industries, see all ESSAM case studies.
Map one procurement process to a redesigned SOP
Describe one procurement or approval process that is taking too long. Bring the step count, the sign-off chain, and your best estimate of cycle time. ESSAM returns a measured baseline against the E-S-S-A-M framework, a waste map showing exactly where the days are being lost, and a redesigned SOP you can put in front of your procurement team — in one session, with no retainer required.
Send your procurement process for a baseline and waste map
Frequently asked questions
What is a banking procurement process improvement case study?
A banking procurement process improvement case study documents the before and after of a specific procurement workflow at a financial institution, including the metrics, methods, and outcomes. The most useful case studies go beyond cycle-time numbers to describe the specific changes made — which steps were removed, which were standardized, which were automated — so that readers can evaluate whether the approach applies to their own process.
How did the Kuwait bank reduce its procurement cycle from 139 days to 57 days?
The reduction came from four sequential changes: eliminating 2 redundant sign-off steps (saving approximately 18 days in queue time), standardizing the vendor intake form from 23 fields to 12 (reducing completion and reconciliation time), automating purchase order creation from the approved intake form (eliminating 40 to 120 minutes of manual re-entry per PO), and migrating all approvals to a single digital workflow with automated reminders and escalation triggers. Each change addressed a different category of waste in the E-S-S-A-M framework.
What does 106.9% process efficiency improvement mean?
It means the redesigned process produces the same output with significantly fewer inputs — fewer steps, less manual handling, less rework, less waiting time. A 106.9% efficiency improvement against the baseline waste map means that more than twice the process value is being delivered per unit of operational effort compared to the original workflow. The figure incorporates cycle-time reduction, elimination of rework, and removal of reconciliation steps that were not visible in the headline cycle-time metric alone.
How much does ESSAM cost compared to a consulting engagement?
ESSAM's Basic plan starts at $40 per month. The Pro plan, which was used in the Kuwait bank engagement, is $200 per month. A traditional consulting engagement scoped to redesign a banking procurement process typically costs between $50,000 and $200,000 with a 3 to 6-month delivery timeline. The difference is not primarily about price; it is about architecture. ESSAM conducts the analysis and produces the redesigned SOP in the same session, with deployment via WhatsApp on the same day the SOP is approved.
Can ESSAM be applied to other banking processes beyond procurement?
Yes. The E-S-S-A-M framework applies to any process with identifiable steps, handoffs, and measurable cycle time. In banking, this includes credit approval workflows, customer onboarding, compliance review chains, vendor due diligence, and internal audit preparation. The methodology is the same regardless of process type: baseline the current state, identify waste against the five E-S-S-A-M phases, redesign, and deploy. The Kuwait bank procurement case is one of several documented transformations across ESSAM case studies.
Related reading: