The report that eats nine days a month
Payments, lending and trading platforms in the Gulf carry a reporting burden nobody budgeted for. The work is real, it is monthly, and it is done by the people you hired to build the product.
The month closes and the work starts
Nothing about the reporting is difficult. It is a set of rules applied to the same tables every month, by somebody senior, from a spreadsheet that lives on one laptop. It takes days you cannot buy back, it cannot be checked by anybody else, and the auditor's question is always about a figure nobody can reproduce.
Five signs this page is for you
Tick the ones you recognise. Nothing is sent anywhere and there is no score: the count is for you, not for us.
Read them again. If none of them land, this page is not for you, and the services page is the shorter route.
Our services, written for your work
The same ones we sell to everybody. What changes is which part of your job each one takes off your desk.
AI transformation
Snapshot the source rows, write the reconciliation rules as code, and produce the submission from the data rather than from a spreadsheet. Every figure resolves back to the rows that made it.
Read the serviceWeb development
Customer facing products that hold up under a compliance review: performance budget, accessibility audit trail, and no third party script nobody can account for.
Read the serviceBlockchain development
Only where two institutions must agree on the same history and neither will accept the other's database. We answer that in writing before quoting the build, and the answer is usually a shared API.
Read the serviceGrowth transformation
SOC 2 readiness and a fractional CTO for the quarter where an enterprise deal needs both and the timeline does not allow a hire.
Read the serviceThe terms that matter before the price does
A baseline before a plan
We measure the current close: how many days, how many hands, how many manual steps. Nothing is proposed until that number exists.
The rules become code
Reconciliation logic moves out of a spreadsheet and into a repository, reviewed like any other code, with the prior period reproducible.
Audit first, not last
Whatever the auditor will ask for is designed in from the first sprint, because retrofitting an audit trail is the expensive version.
A named owner inside your team
We hand over to a person, not to a document. If your team cannot run the close without us, the engagement failed.
What it looked like on a real engagement
Regulatory reporting that stopped eating nine days
Monthly regulator submissions assembled by hand across four systems, with no audit trail back to source.
- Cycle time
- 8.5 days6 hours
- Restatements
- 90
- Traceable rows
- 12%100%
Compared against the 12 monthly cycles preceding the engagement. Source: internal close log, June 2025
When we are the wrong call
- The requirement is a licence, not a system
- Nobody internally can approve changing how a figure is produced
- The close is painful but no one has ever measured how painful
Asked on the first call
Do you know Gulf regulation?
We know how to build a system that produces what a regulator asks for and proves where it came from. The rules themselves come from your compliance team, and they are written down as code so the next change is an edit rather than a project.
Where does our data sit?
Wherever the contract requires. Residency clauses that rule out every hosted product are a normal starting condition for us, not an obstacle to work around.
Can you finish our SOC 2?
We can get you ready for the audit: the controls, the evidence and the roadmap. The audit itself belongs to an auditor, and we will say so rather than imply otherwise.
How long is the first useful result?
Six weeks to the first automated submission on the last engagement of this shape. The measurement window and the source are published on the case.
One email a month, on what actually shipped
What we built that month, what it cost, and what we would do differently. No campaign, no offer, and one click to leave.
Bring the brief you are not sure you can deliver
Forty five minutes with the engineer who would run it. We will tell you on that call if the date is not reachable.