Background: A 30-Person Fintech in Dubai
This case study is a composite based on patterns observed in the field. We do not fake named customers. The details below reflect a real engagement profile, with identifying information generalized to protect client confidentiality.
The client was a 30-person fintech company in Dubai, focused on cross-border payments for e-commerce. They used a standard ERP for order management and Slack for internal communication. Their operations team of 12 handled supplier documents in English, Arabic, and occasionally French. The manual process involved copying data from PDFs into the ERP, which took 3-5 hours per batch. The company was in the growth stage, with revenue around AED 15 million annually. They had no prior AI deployment but had a clear need to reduce manual data entry and speed up order status updates.
Challenge: Slow Turnaround, Multilingual Data, and a PCI DSS Audit
The operations team faced three pressures simultaneously. First, document turnaround was slow: a supplier shipment status update took 4.2 hours on average to move from PDF receipt to ERP entry. Second, the team needed to post status updates to a Slack channel for the logistics team, but the manual process was error-prone. Third, a PCI DSS audit was scheduled for Q3, which required documented controls over how cardholder data was handled. The team could not afford to hire more staff, and the multilingual nature of the documents (English, Arabic, French) made manual processing even slower. The deadline was hard: the audit had to pass, and the team needed to demonstrate that data handling was under control.
Approach: A Fixed-Scope Pilot with LangChain and LangGraph
The team ran a fixed-scope pilot over six weeks. The scope was narrow: extract shipment data from supplier PDFs and post status updates to Slack. The architecture used LangChain to define extraction prompts and data schemas. LangGraph handled the state machine: if the model was uncertain about a field, it routed the document to a human reviewer in Slack. If the confidence score was above 0.95, it auto-posted the update. The LLM ran on the client’s own GPU server in Dubai, so no cardholder data left the building. For the multilingual layer, a smaller open-weight model handled Arabic and English translation locally. The team built a small evaluation set of 200 historical documents to measure extraction accuracy per field.
Outcome: 18-Minute Turnaround and a 9% Error Reduction
The pilot measured cycle time from document receipt to ERP entry. Before automation, it took 4.2 hours on average. After, it dropped to 18 minutes for auto-approved documents. Error rate on field extraction fell from 12% to 3%. The team documented these baselines in a one-page report before the rollout decision. The human-in-the-loop step caught 8% of documents that the model was uncertain about, and the reviewers corrected them in under 2 minutes each. The Slack integration meant the logistics team saw status updates in real time, rather than waiting for a batch report. The PCI DSS auditor noted the documented controls and the local data processing as positive findings.
Lessons for Similar Teams
- Start with one process, not a platform. The pilot succeeded because the scope was narrow. Trying to automate all document types at once would have diluted the measurement and delayed the rollout.
- Run the model on client hardware when data is regulated. The PCI DSS requirement was not a blocker; it was a design constraint. The local GPU server made the solution compliant without sacrificing model quality.
- Make the human-in-the-loop step explicit. The LangGraph state machine made the approval step visible and auditable. This was critical for the PCI DSS audit and for building trust with the operations team.
- Measure before and after, in writing. The one-page baseline report gave the client a concrete artifact to show the board and the auditor. It also set the stage for the next phase of automation.
Leave a Reply