Services
We build the software that runs the business, and the AI that reasons over it.
Two practices, six lines of work. For each line: what it is, what is delivered, and how the engagement is priced and staged. Advice and engineering come from the same team, so the plan you receive is one we are prepared to build.
02How the lines connect
One firm, accountable for the whole chain.
Assessment establishes what is worth doing. Engineering builds it, whether that is an ERP integration, a mobile application or a model deployment. Integration and governance make the result fit the estate and stand up to review, deployment puts it on infrastructure inside the Kingdom, and enablement brings it into daily use. Most AI work fails at the plumbing, and most business software now has AI somewhere inside it, so one team doing both means the system that runs the business and the system that reasons over it are built to the same standard. A Saudi firm able to do that, on data that stays in the Kingdom, is one contribution to the capability Vision 2030 calls for.
Establishes what the organisation has, what it needs, and what is worth building.
Enterprise systems, applications, platforms, agents and models, delivered into your repositories.
Connects the result to the systems of record, and adds the controls and audit trail that make it defensible.
Puts it into production on infrastructure inside the Kingdom, or on your own.
Hands it over with runbooks, and trains your people to run it.
- 01AssessEstablishes what the organisation has, what it needs, and what is worth building.
- 02BuildEnterprise systems, applications, platforms, agents and models, delivered into your repositories.
- 03Integrate and governConnects the result to the systems of record, and adds the controls and audit trail that make it defensible.
- 04DeployPuts it into production on infrastructure inside the Kingdom, or on your own.
- 05EnableHands it over with runbooks, and trains your people to run it.
03Two practices
Software engineering
The systems that run the organisation, built to last.
Enterprise systems and ERP programmes, web and mobile applications, and platforms that carry regulatory weight. For organisations replacing something that no longer fits the way they work, or building what no product on the market covers.
Enterprise systems & ERP
Enterprise systems and ERP work covers choosing a product on the evidence, implementing the one you have chosen, extending or replacing what is already in place, and connecting finance, HR, procurement and inventory to the systems of record around them. Where no product on the market fits the way an organisation works, we build the internal platform instead. Migration and data cleanup are scoped into the programme at the start.
What you receive
- A current-state map of the processes, the systems holding the data, and the people who own each step
- A fit assessment against the product under consideration, with every gap named
- Configuration, extensions, and the integrations to your systems of record
- Data migration with the cleanup and reconciliation it needs
- A phased cutover plan, and support through the first close after go-live
How the engagement runs
Current-state mapping and fit assessment as a fixed-scope phase, implementation by phase against an agreed scope, and support after go-live as a retainer. Where customising a product far enough to fit would put its future upgrades out of reach, the assessment says so and sets out the alternative.
Web & mobile applications
Web and mobile applications covers customer-facing apps, staff and partner portals, dashboards and internal tools: mobile in Flutter for iOS and Android, the web applications and APIs behind them, and interfaces in Arabic and English where the right-to-left layout is designed rather than mirrored from the English. Work runs in slices, so there is something you can open and judge every few weeks. Deployment goes to cloud regions inside the Kingdom where residency requires it, or to infrastructure you already run.
What you receive
- Discovery: who uses the application, the task each of them needs to finish, and the constraints around it
- Interface design in Arabic and English together, with right-to-left layout designed for it
- The application, its APIs and its infrastructure definitions, in your repository from the first commit
- Accessibility and performance checks on the devices and networks your users have
- App store release under your own developer accounts, and runbooks for the team that takes it on
How the engagement runs
Fixed scope for discovery and design, then build in slices, each ending in something running that you can use. A retainer follows where the product keeps changing; where it does not, the hand-over ends the engagement and your team carries it from there.
Fintech & regulated platforms
Fintech and regulated platforms covers payment, lending, wallet, billing and back-office systems, and other software that carries regulatory weight. The engineering decides whether a platform survives review: integration with banking and payment rails, reconciliation that balances, an audit trail over every consequential action, and access control with segregation of duties. We do the engineering. Licensing and regulatory advice stay with your counsel and your compliance function.
What you receive
- Integration with the banking, payment and settlement rails the product depends on
- Ledger and reconciliation design, with breaks surfaced instead of absorbed
- Access control, segregation of duties, and an audit trail over every consequential action
- A codebase prepared for penetration testing, and the remediation that follows the report
- The evidence pack your auditors and your risk function ask for
How the engagement runs
Fixed scope per release, with the security, reconciliation and audit work inside that scope. Where a question belongs to your regulator or your licence rather than your engineers, the work stops at that boundary and says so.
04Two practices
Artificial intelligence
Models that stay inside the Kingdom, and inside the rules.
Adoption from assessment through to production, the governance that makes a deployed system defensible, and open-weight models on infrastructure the client controls. For organisations answering to a regulator, a data residency rule, or a board that wants evidence before it commits.
AI transformation
AI transformation runs from readiness assessment to systems in production, with the same team advising and building. Most transformation consulting stops at the roadmap. Ours continues into the pilot and the build, so the roadmap is written by people who will have to deliver it.
What you receive
- A readiness assessment covering data, systems, people and governance
- A use-case portfolio scored for value, feasibility and risk, including the cases we advise against
- A roadmap staged and priced so you can stop at any phase
- A working pilot built end to end on your data, inside the Kingdom
- An operating model your own people run
How the engagement runs
Assessment and roadmap as fixed-scope sprints, pilots fixed-scope, and the scale phase as a programme retainer. You can exit at any boundary and keep everything produced up to that point.
AI governance, safety & compliance
AI governance means the policies, controls and assurance that let an organisation defend its use of AI to its board or a regulator, aligned with SDAIA’s AI ethics and adoption guidance, the Personal Data Protection Law and NCA controls where they apply. Because the same firm builds systems, findings are implemented as controls with an audit trail rather than left in a report.
What you receive
- A governance framework written for the structure you have: policy, roles, approval gates, model inventory
- Risk and impact assessments for planned and deployed systems, including PDPL exposure
- Audits of existing AI systems, with findings and reasoning in a written report
- Implemented controls: input and output policy, audit logs, human checkpoints
- The documentation pack you show a regulator
How the engagement runs
Advisory sprints and audits are fixed-scope; ongoing assurance runs as a named retainer. Where a system cannot be made defensible, the report states that and explains why.
Sovereign & private AI deployment
Sovereign AI deployment puts open-weight models on infrastructure the client controls: on-premises, in an in-country cloud, or air-gapped. Models are evaluated on your own tasks, sized to the workload, monitored, and handed to your team. For much of the data held by Saudi government, healthcare and financial organisations, staying inside the Kingdom is a condition of any AI work.
What you receive
- Model evaluation on your own tasks, before any commitment to hardware
- A deployment architecture your security team can review before procurement
- Retrieval over your documents, indexed inside your network boundary
- Guardrails, monitoring and an audit log with the retention your compliance function requires
- Runbooks, an upgrade path, and a hand-over to your engineers
How the engagement runs
Fixed-scope, beginning with the evaluation. If a hosted API is the better choice for non-sensitive workloads, the evaluation will recommend it and the engagement can end there.
05Three more lines
One level down, on the same terms.
These are usually where a front-door engagement leads: the data platform an integration exposes the need for, the agents a roadmap calls for, or the training that follows a hand-over. Each can also be commissioned on its own, at a fixed scope.
How an engagement runs, phase by phase- 07
Agentic AI & automation
Multi-step agents that hold state, act in your systems under typed permissions, and stop for a person before any consequential action. Where a full agent is more than the job needs, lighter automation that runs on its own.
- What you receive
- Working agents or automations in your repository, the evaluation set that tests them, deployment on your infrastructure, and runbooks.
- How the engagement runs
- Fixed-scope. If the workflow is deterministic, the right tool is a script, and we will recommend one on the first call.
- 08
Data platforms & integration
The pipelines, the warehouse or lakehouse, and the integration layer between systems that were never designed to talk to each other. Reporting and AI fail for the same reason more often than for any other: the data underneath them was never put in order.
- What you receive
- Pipelines and integration code in your repository, a modelled warehouse or lakehouse, data quality checks that run on a schedule, and the documentation for both.
- How the engagement runs
- Fixed-scope for the first domain, then domain by domain as the rest of the estate comes in. Where a scheduled export would do the job, we will say so before a platform is proposed.
- 09
AI enablement & training
Executive briefings, hands-on programmes for teams, and role-specific training in using AI well and safely at work, in Arabic or English, with an internal usage policy alongside.
- What you receive
- The sessions, bilingual materials under your own branding, an internal usage policy, and an uplift plan measured with your own instruments.
- How the engagement runs
- Programmes and workshops, priced per cohort or per programme.
06Start here
Describe the situation, and we will tell you which line fits.
Tell us what you are trying to change and what you have to work with: the systems, the data, the people. If one of the six lines fits, the first reply will name it. If none does, the reply will say that instead.
Start a conversation